David Härdeman wrote: > On Wed, July 9, 2008 10:51, Giorgos D. Pallas wrote: > >> David Härdeman wrote: >> >>> ... (why do you have a cryptroot file by the way? It's supposed >>> to be a cryptsetup internal config file) >>> >> If I understood your question well, my answer is this: I have >> /etc/initramfs-tools/conf.d/*cryptroot containing the line: >> **target=lukspace,source=/dev/hda3,key=none,lvm=vg-root* >> because I have my root partition sitting on LVM, which sits on LUKS. So, >> somehow the initrd image must know that it has to find a LUKS partition >> and ask me for its passphrase. >> >> I hope I'm not talking nonsense. When I tried to set up encrypted root >> partition, I used googling, a bit hacking and imagination. So, there is >> the possibility that an easier method eludes me. >> > > Yes, the "correct" method would be to create a /etc/crypttab file with the > mapping for your root device. See the documentation in > /usr/share/doc/cryptsetup for details on how to do that. > > Once a proper crypttab is setup, cryptsetup will automagically generate > initramfs config files for you. >
Not to my surprise, you were right :-) I just deleted the /etc/initramfs-tools/conf.d/cryptroot file, and run again update-initramfs -u. Laptop boots fine. Btw, I already had /etc/crypttab correctly configured, so it seems that the cryptroot file was redundant. So, probably the bug has to be closed since it was a consequence of a wrong practice, if I got it right. Thanks for all, Giorgos
smime.p7s
Description: S/MIME Cryptographic Signature