CRYPTSETUP-LUKSUUID(8)
π CRYPTSETUP-LUKSUUID β the girlies' guide to LUKS UUIDs π
okay so bestie, this is the cryptsetup-luksUUID page from the cryptsetup maintenance commands (section 8, we love a numbered section β¨). It's literally just: peep your LUKS device's UUID, or swap it for a new one. Short page, big energy. Let's go π«Ά
πΈ NAME πΈ
cryptsetup-luksUUID β print or set the UUID of a LUKS device
β¨ SYNOPSIS β¨
cryptsetup luksUUID [<options>] <device>
π¦ DESCRIPTION π¦
Prints the UUID of a LUKS device. That's the vibe. π
And if you hand it the --uuid option? It sets a brand new UUID instead. Glow-up for your metadata fr fr π
<options> can be [--header, --uuid, --type, --disable-locks].
π OPTIONS π
--batch-mode,-qβ Suppresses all the confirmation questions. Use with care, bestie, I'm serious π
If the --verify-passphrase option isn't specified, this option also switches off the passphrase verification. So yeah, it's giving "no takebacks."
--debugor--debug-jsonβ Runs in debug mode with full diagnostic logs. Debug output lines are always prefixed by#.
If --debug-json is used, additional LUKS2 JSON data structures get printed. Snack for the nerds π
--disable-locksβ Disables lock protection for metadata on disk. This option is valid only for LUKS2 and is ignored for other formats.
WARNING: do not use this option unless you run cryptsetup in a restricted environment where locking is impossible to perform (like when the /run directory cannot be used). No cap, just don't π
--header<device or file storing the LUKS header>β Uses a detached (separated) metadata device or file where the LUKS header is stored. This option lets you keep the ciphertext and the LUKS header on different devices. Separation era π§
For commands that change the LUKS header (e.g., luksAddKey), specify the device or file with the LUKS header directly as the LUKS device.
--help,-?β Shows the help text and default parameters. Your little map πΊοΈ--typetypeβ Specifies the required device type. For more info, read the BASIC ACTIONS section incryptsetup(8).--usageβ Shows short option help. The bite-sized version β¨--uuidUUIDβ Uses the provided UUID for theluksFormatcommand instead of generating a new one. When used with theluksUUIDcommand, it changes the existing UUID.
The UUID must be provided in the standard UUID format, e.g., 12345678-1234-1234-1234-123456789abc.
--version,-Vβ Shows the program version. Iconic behavior π
π REPORTING BUGS π
Report bugs at the cryptsetup mailing list <cryptsetup@lists.linux.dev> or in the Issues project section <https://gitlab.com/cryptsetup/cryptsetup/-/issues/new>.
Please attach the output of the failed command with the --debug option added. (Receipts, bestie. Always bring receipts π§Ύ)
π SEE ALSO π
Cryptsetup FAQ <https://gitlab.com/cryptsetup/cryptsetup/wikis/FrequentlyAskedQuestions>
cryptsetup(8), integritysetup(8) and veritysetup(8)
π CRYPTSETUP π
Part of the cryptsetup project <https://gitlab.com/cryptsetup/cryptsetup/>.
and that's the whole page, bestie, you ate that π
β¨ this lil manual is from cryptsetup 2.8.8, dated 2026-09-07 β go forth and luksUUID responsibly, mwah π«Άπ
π¦ where this page comes from
- arch rolling: cryptsetup 2.8.8-1 Β· GPL-2.0-or-later
- fedora 44: cryptsetup 2.8.8-1.fc44 Β· GPL-2.0-or-later WITH cryptsetup-OpenSSL-exception AND LGPL-2.1-or-later WITH cryptsetup-OpenSSL-exception
- nixpkgs unstable: cryptsetup 2.8.8
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms