Bug#428725: initramfs-tools: please provide hook to initialize LVM before mounting crypto-root

[maximilian attems <max@stro.at>]

reassign 428725 cryptsetup
stop

[ please keep me on cc on future replies, i'm not cryptsetup subscribed ]

heya marc,

the cryptsetup utility is responsible for its own hooks
thus reassigning.

On Wed, 13 Jun 2007, Marc Haber wrote:

> 
> I have my root filesystem on an encrypted LV:
> 
> $ grep root /etc/crypttab
> root              /dev/vg0/c_root      none  luks,keyscript=/etc/keyscript_scyw00225
> $ grep root /etc/fstab
> /dev/mapper/root /              ext3    defaults,errors=remount-ro 0 1
> $
> 
> In this setup, the initrd does not start the LVM before trying to
> unlock the crypto filesystem. From my diagnosis, it looks like
> scripts/local-top/lvm2 looks whether the file system given to the
> kernel on its command line is directly on an LV and only starts the
> appropriate VG in this case. It does not seem to detect the
> possibility of the root FS being on an encrypted LV.

hmmm i certainly know that cryptoroot works with initramfs-tools.
according to your description above it is on top of lvm2?
right?

i'm 100% sure that this is supported,
so either your bootargs are wrong or the crypttab.
 
> A possible solution to this would be to provide a hook to override the
> ROOT variable for the lvm2 script.
> 
> I have worked around this by copying the lvm2 script to
> /etc/initramfs-tools/scripts/local-top and to hardcode an "activate_vg
> /dev/mapper/vg0-c_root" there.

hope that david will shed some light on your bug report.

> -- Package-specific info:
> -- /proc/cmdline
> root=/dev/mapper/root ro video=radeon:force_sleep,1400x1050-24@60 initrd=initrd BOOT_IMAGE=vmlinuz 
> 

best regards

-- 
maks