Hi List, Since my cry for (fairly minor) help here: https://lists.debian.org/debian-user/2021/08/msg00461.html I think I've dug myself into a bit of a deep hole.
After having overcome a fairly fundamental bug with calamares as described here: https://github.com/calamares/calamares/issues/1564#issuecomment-846321060 And, (unnecessarily as it turned out) re-installed my system, I find I'm unable to boot. Instead of getting a password prompt for my luks lvm partition, I get dropped to the shell with the following error: cryptsetup: ERROR: luks-[some UUID]: cryptsetup failed, bad password or options? /bin/cat: /crypto_keyfile.bin: No such file or directory Nothing to read on input In (initramfs) /cryptroot/crypttab There is luks-[some UUID] UUID=[some UUID] /crypto_keyfile.bin luks,keyscript=/bin/cat I can manually mount my my luks volume so: cryptsetup open /dev/sda3 --type luks [some UUID] Enter passphrase for /dev/sda3: To here: /dev/mapper/[some UUID] But, from there the LVM LVs don't get mounted and if I exit to boot then I get dropped back to the shell. And, lvm2 doesn't seem to be in initramfs. I can reboot to the live install usb image and when I do: sudo cryptsetup open /dev/sda3 --type luks [some UUID] Enter passphrase for /dev/sda3: >From the terminal, then the lvm on luks volumes pop up as expected immediately decrypted, named under /dev/mapped/[some VG-LV-name], /dev/[some VG]/[some LV], enumerated at /dev/dm-xyz etc and mounted under /media/user/[partition label] So, may be calamares has more than one bug with LVM on LUKS? Or, as the above bug only refers to LVM and not LUKS, perhaps I've done (or not done) something silly during the install with calamares and LUKS (though, it does seem a pretty pedestrian walk through of the install process). I guess, there's something not referenced in the initramfs? Any pointers to a way back from Armageddon would be great :) Thanks. -- Morgan Read E mst...@read.org.nz (GM)
