You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
The FDE guide here currently shows the following example
/etc/crypttab
: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 evenluks-...
, but I'm not sure which one is best/correct here. I think the relevant dracut module is/usr/lib/dracut/modules.d/90crypt
.The text was updated successfully, but these errors were encountered: