Repository navigation
FDE guide: Use UUID instead of /dev/sda* in crypttab #662
Description
The FDE guide here currently shows the following example /etc/crypttab:
voidvm /dev/sda1 /boot/volume.key luks
This should be changed to using the UUID of the encrypted device/partition, as the device file names dev/sdx are not deterministic.
Some user on #voidlinux just had an issue where the key file in the initramfs would sometimes not be picked up, and they were asked to enter a passphrase instead. I think this might be because they had /dev/sda1 in their /etc/crypttab like the guide suggests. They reported that using /dev/disk/by-uuid/* worked.
I think dracut also understands some other syntax like UUID=... and even luks-..., but I'm not sure which one is best/correct here. I think the relevant dracut module is /usr/lib/dracut/modules.d/90crypt.
Reacted by Toyam Cox, Hadet, TheChosenPrometheanKing and Rouben
Activity
synepis commentedon Mar 6, 2025
I would also consider adding the
-Uflag for the fstab generation as it is on the standard chroot installationxgenfstab /mnt > /mnt/etc/fstab->xgenfstab -U /mnt > /mnt/etc/fstabclassabbyamp commentedon Mar 6, 2025
are the uuids of mapper-mounted partitions stable?
synepis commentedon Mar 6, 2025
I'm not sure what you mean by stable, but the UUIDs should be stable across reboots. That, to me, is the more important stability rather than stability when a partition get re-formatted or other such less frequent actions.