Partitioning (LUKS)
LUKS (Linux Unified Key Setup) is the standard for Linux hard disk encryption. By providing a standard on-disk-format, it does not only facilitate compatibility among distributions, but also provides secure management of multiple user passwords. LUKS stores all necessary setup information in the partition header, enabling to transport or migrate data seamlessly.
Management of LUKS encrypted devices is done via the cryptsetup
utility.
Nomenclature
Expression | Abbreviation | Meaning |
---|---|---|
Physical Volume | PV | Unix block device node, usable for storage by LVM. Examples: a hard disk, an MBR or GPT partition. |
Volume Group | VG | Group of PVs that serves as a container for LVs. PEs are allocated from a VG for a LV. |
Logical Volume | LV | "Virtual/logical partition" that resides in a VG and is composed of PEs. LVs are Unix block devices analogous to physical partitions, e.g. they can be directly formatted with a file system. |
Physical Extents | PE | The smallest contiguous extent (default 4 MiB) in the PV that can be assigned to a LV. Think of PEs as parts of PVs that can be allocated to any LV. |
LVM on LUKS
LVM on LUKS has the benefit of being able to encrypt an entire drive (useful for laptops with encrypted swap for resume) while only needing to provide a single passphrase to unlock it entirely for simplicity.
However, since the LVM container resides inside the LUKS container it cannot span multiple disks, as it is confined by the boundaries by the parent LUKS container.
NOTE: This partitioning scheme does NOT include an LVM cache device. However, it is technically possible to add a cache device to it.
However, it is not advised to add an LVM cache device to an LVM on LUKS setup, as it leaks plain text contents of the unlocked LUKS container into the cache, which can be read in a hex editor by opening the device node directly — endirely defeating the purpose of encrypting the disk!
A LUKS on LVM setup is recommended instead.
This guide assumes the following:
- This is used on a laptop computer with resume capabilities (Swap partition)
- There is only one drive:
/dev/nvme0n1
- The root file system will be btrfs, with subvolumes for
/
and/home
- To tighten security, this setup assumes a unified kernel image and booting via EFISTUB, with the ESP mounted at
/efi
. Extra steps will be necessary to make the machine bootable.
Preparing the drive
-
List available disks
fdisk -l
-
Start partitionaing tool for primary disk (
cfdisk
is a little easier to use as it has a nice TUI)WARNING: Make sure to select your actually desired device!
cfdisk /dev/nvme0n1
-
Partition with the following scheme
FS Type Size Mount Point Comment | vfat | 1G |
/efi
| EFI System | | LUKS | (remaining) | | Linux file system |
Creating the LUKS container
-
Create the LUKS container and enter a passphrase
WARNING: Do NOT forget your passphrase! In case of loss you won't be able to access the data inside the container anymore!
cryptsetup luksFormat /dev/nvme0n1p2
-
Open the newly created LUKS container
NOTE:
cryptlvm
is used as an example here. Use whatever you like.cryptsetup open /dev/nvme0n1p2 cryptlvm
Creating LVM inside the LUKS container
-
Create an LVM physical volume inside LUKS container
pvcreate /dev/mapper/cryptlvm
-
Create the volume group:
vgcreate vg0 /dev/mapper/cryptlvm
-
Create the logical volumes
NOTE: When using resume, make
lv_swap
as large as RAM. In this example the machine has 16 GB of RAM.lvcreate -L 16G -n lv_swap vg0 # Swap as big as RAM (16 GB) lvcreate -l 100%FREE -n lv_root vg0 # Root file system
Formatting devices
- Create partitions
mkfs.fat -F 32 /dev/nvme0n1p1 # EFI System Partition mkfs.btrfs /dev/mapper/vg0-lv_root # Btrfs root volume mkswap /dev/mapper/vg0-lv_swap # Swap space
- Create Btrfs subvolumes
# First, mount the root file system mount /dev/mapper/vg0-lv_root /mnt # Create subvolumes btrfs subvolume create /mnt/@ btrfs subvolume create /mnt/@home
- Mount partitions
# Unmount the root file system umount -R /mnt # Mount the @ subvolume mount /dev/mapper/vg0-lv_root -o noatime,compress-force=zstd,space_cache=v2,subvol=@ /mnt # Create mountpoints mkdir -p /mnt/{efi,home} # Mount the remaining partitions/subvolumes mount /dev/nvme0n1p1 /mnt/efi mount /dev/mapper/vg0-lv_root -o noatime,compress-force=zstd,space_cache=v2,subvol=@home /mnt/home # Activate swap swapon /dev/mapper/vg0-lv_swap