On Sat, 27 Jul 2024 03:49:49 +0200 Thomas Lange <la...@cs.uni-koeln.de> wrote: > Using lsinitrd /boot/initramfs.... you can check which dracut modules > are available in the initrd. > Following modules are available for crypt stuff: > > crypt > systemd-cryptsetup > crypt-gpg > crypt-loop > > Maybe you have to add some of these modules into dracut config.
Hi Thomas, dkg, I also got bit by this one today. Looking at the generated initrds, they look like they have the necessary information in them -- I've attached the lsinitrd for the record, but the modules I'd expect to be there are there (i.e., crypt, lvm, systemd-cryptsetup, tpm2-tss). I don't actually get a password prompt at all, and setting hostonly to either parameter doesn't work, so I think the problem has to do with the way disks are being detected. I'm curious, dkg, how do you have your disks specified in the kernel_cmdline config -- and do you have hostonly set to yes or no? I'd also love to get a copy of the output of blkid from you; were you using the magic UUIDs? Sincerely, -- Harlan Lieberman-Berg ~hlieberman
initrd-hostonly-no.txt.zst
Description: application/zstd
initrd-hostonly-yes.txt.zst
Description: application/zstd
