Re: LUKS+LVM won't boot: "Cryptodisk module not loaded"
Reply #11 –
After recreating the installation process (this time with the official Artix FDE guide) I did run into this problem again. This time however, not even the PBKDF2 password works. The passwords are either rejected as wrong (even when they're correct) or the aforementioned problem arises.
I did notice one thing:
'nano /boot/grub/grub.cfg' ...
...
search --no-floppy --fs-uuid --set=root --hint='lvmid/Skoq3X-YmuA-Cg21-QxwM-VLok-2tlE-fbe34a/D070Hs-cZHS-AdLj-0fPz-HuX1-W2K8-fcyL2o' f1e7328e-ad52-4e4c-ae7b-2c758e69da12
...
...
the "Skoq3X..." UUID is mentioned multiple times in this file and that the same one that appears in the error message, even though the '/etc/default/grub' contains specifically 'cryptdevice=UUID=0f951dae-7d77-4ac8-b61a-fc0d91b39e8c:lvm root=UUID=f1e7328e-ad52-4e4c-ae7b-2c758e69da12'. No mention of the Skoq3X...
Out of curiosity I also ran ' cat /etc/crypttab' ...
# <name> <device> <password> <options>
lvm UUID=0f951dae-7d77-4ac8-b61a-fc0d91b39e8c none
It includes the UUID of the LUKS drive but not the one of the root lvm within. Not sure if that is correct.