On Wed, 1 Apr 2009 14:21:25 +0200 maximilian attems <[email protected]> wrote:
> reassign 522041 cryptsetup > stop > <snip> > > > did you try to pass a "rootdelay=12" bootparam? > > > > I did experiment with the rootdelay parameter, but please note that the > > reason the system would not boot was clearly the missing > > conf/conf.d/cryptroot file. update-initramfs just failed to pack this > > file into the initrd.img if the root file system was specified by > > LABEL=CRYPTROOT in /etc/fstab. The system setup though was obviously > > ok., I just had to add the file manually to initrd.img and the system > > would boot up normally. The irony herein is that I would not have used > > the LABEL=... thing unless the debian docs had advised me to do so, > > otherwise I might end with an unbootable system ;) > > > > Michael > > just wanted to exclude the nr. 1 trap users fell into, > reassigning to cryptsetup which is responsible for it's own hooks and > conf/conf.d/cryptroot. anyway nicer then LABEL and recommended is UUID > usage, but LABEL should just work too. > > -- > maks Now I got curious and gave it a try, but using UUID it does not work either. Anyway, I see the scripts in question belong to cryptsetup, I should have checked that properly. I guess I got trapped because they sit in /usr/share/initramfs-tools. Apologies for that. Michael -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
