REFORM-SETUP-ENCRYPTED-DISK(1)

✨ reform-setup-encrypted-disk ✨

okay bestie, gather round, because this is the reform-setup-encrypted-disk page from the User Commands section and it is literally the glow-up your disk has been waiting for 💅

---

🌸 NAME 🌸

reform-setup-encrypted-disk — setup encrypted disk 🔐

like. the name says it all. we're setting up an encrypted disk. iconic behaviour.

---

🦋 SYNOPSIS 🦋

reform-setup-encrypted-disk [--help] [DEVICE_PATH]

that's it. that's the whole vibe. one optional flag-ish thing and one optional path. no cap.

---

💖 DESCRIPTION 💖

so here's the tea 🍵 — this tool sets up a disk with LUKS encryption holding LVM2 volumes, one for swap and one for the rootfs. locked down, organised, main character energy.

and because it's a considerate little script, it also offers to run reform-migrate and reform-boot-config to set up the initramfs in /boot on the first partition of the eMMC or SD-card, so that booting can actually load the rootfs off the encrypted disk. it's giving "I'll handle the logistics, you just exist" 🫶

---

🎀 OPTIONS 🎀

• --help — displays this help and dips out. shows you the goods, then exits. queen behaviour honestly.
• --force — avoids user interaction entirely: it runs reform-migrate and puts /boot on eMMC if allowed. ⚠️ requires the passphrase on standard input. so no chatting, no prompts, just vibes and a piped passphrase.

💀 heads up bestie: --force means no interaction. if you weren't planning on feeding it a passphrase through stdin, this is gonna be a bad time.

🌈 Arguments: 🌈

• [DEVICE_PATH] — the disk, partition or regular file you want set up with LUKS and LVM. if you just... don't pass it? it defaults to the SSD. no thoughts, head empty, SSD it is.

now, if you hand it the eMMC device, it gets partitioned like this: first partition for /boot, second partition for LUKS&LVM. two partitions, two jobs, we love a structured queen.

and there are shorthands, because typing full paths is so much effort:

• ssd → install to the SSD
• emmc → install to the eMMC
• sd → install to the SD card
• usb → install to a USB drive

🙈 okay but here's the trap: what if you want to copy to a file that happens to be named exactly one of those shorthands? then you prefix the filename with a dot and a slash to make it a relative path. like ./ssd. otherwise it'll think you mean the SSD and not your lil file. iykyk.

---

⭐ EXAMPLES ⭐

Example 1: you're booted from the SD-card, and you wanna set up the first partition on eMMC as /boot plus set up the SSD with LUKS. then inside LUKS you set up LVM with one volume for swap and the other for the root file system, and copy the current system to /dev/reformvg/root:

./bin/reform-setup-encrypted-disk

Example 2: booted from SD-card again, but this time you set up eMMC with two partitions — first one for /boot, second for LUKS. LVM goes inside LUKS with one volume for swap and the other for the root file system, and the current system gets copied to /dev/reformvg/root. you suppress any interactivity with --force and grab the LUKS passphrase from standard input:

echo hunter2 | ./bin/reform-setup-encrypted-disk --force emmc

🍓 yes the passphrase in that example is hunter2. we're all thinking it. moving on. 💀

---

👑 SEE ALSO 👑

no SEE ALSO on this one bestie — it's a standalone baddie. go forth and encrypt. 🌟

---

this lil page is reform-setup-encrypted-disk version 1.71, dated December 2025, and yeah it's still filed under REFORM-SETUP-ENCRYPTED-DISK(1) in the User Commands section. periodt. 💜