CRYPTSETUP-ISLUKS(8)

💅 CRYPTSETUP-ISLUKS 💅

okay bestie, welcome to cryptsetup-isLuks — she's a lil command from the cryptsetup manual (section 8, Maintenance Commands, iykyk) and honestly? she's giving "am I LUKS or not" and nothing else. queen of the yes/no question. 🎀

---

✨ NAME ✨

cryptsetup-isLuks — check if a device is a LUKS device 🦋

---

🌸 SYNOPSIS 🌸

cryptsetup isLuks [<options>] <device>

---

💖 DESCRIPTION 💖

So basically: this returns true if <device> is a LUKS device, and false otherwise. That's it. That's the whole job. iconic behaviour honestly. 💅

Slap on the -v option and you get actual human-readable feedback instead of cryptic silence. If it prints 'Command successful.' — congrats babe, that device is a LUKS device. 🎉

And if you wanna get specific? By specifying --type you can query for a particular LUKS version. main character energy: know exactly which version you're asking about. 👑

Oh and for the record, <options> can be [--header, --type, --disable-locks]. that's the whole guest list. 🫶

---

🌈 OPTIONS 🌈

• --batch-mode, -q — suppresses all the confirmation questions. no "are you sure" energy, just vibes. Use with care! 😭 Also — heads up — if the --verify-passphrase option is not specified, this option also switches off the passphrase verification. so yeah, careful bestie.
• --debug or --debug-json — run in debug mode with full diagnostic logs. every debug output line is always prefixed by #. And if you go with --debug-json, you also get additional LUKS2 JSON data structures printed out. extra data? we love to see it. ✨
• --disable-locks — turns off lock protection for metadata on disk. This option is valid only for LUKS2 and gets ignored for every other format. ngl, it only works for one of the girlies. 💀

⚠️ WARNING: do not use this option unless you're running cryptsetup in a restricted environment where locking is literally impossible to perform (like, where the /run directory cannot be used). fr fr, this one is a last resort. 🚨

• --header <device or file storing the LUKS header> — use a detached (separated) metadata device or file where the LUKS header lives. this option lets you keep the ciphertext and the LUKS header on different devices — long-distance relationship, but make it storage. 🦋

For commands that change the LUKS header (e.g., luksAddKey), specify the device or file with the LUKS header directly as the LUKS device. yes, directly. no middleman. 💅

• --help, -? — show help text and default parameters. always read the manual, bestie. 📖
• --type type — specifies the required device type. for more info, read the BASIC ACTIONS section in cryptsetup(8). go read it, I'll wait. 🫶
• --usage — show short option help. the lil snack-sized version. 🍓
• --verbose, -v — print more information on command execution. this is the one that gives you the human-readable feedback, remember? ✨
• --version, -V — show the program version. gotta know which era of cryptsetup you're living in. 🌸

---

😭 REPORTING BUGS 😭

Found a bug? Report it at the cryptsetup mailing list <cryptsetup@lists.linux.dev> or in the Issues project section at <https://gitlab.com/cryptsetup/cryptsetup/-/issues/new>. 🐛

And please — pretty please — attach the output of the failed command with the --debug option added. we need the receipts, bestie. 💜

---

👑 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/>. the whole squad. 💖

---

and that's the page, babe! this was cryptsetup 2.8.8, dated 2026-09-07 — literally the freshest. now go check if your device is LUKS, periodt. 💅✨🦋