Hey Jiri, On 16/08/2010 Jiri Kanicky wrote: > Hi. > > I attached picture with the boot message. > > I was digging into the problem more today and found the following: > > - looks like LVM does not activate the /dev/data_vg/knightrider-sec > volume on the boot and therefore cryptsetup cannot see the volume. > It only activates one LV; knightrider-root. > > - in the (initramfs) mode on the picture I typed "lvm" which took me > to (lvm) mode. I activated all volumes in the data_vg group > "vgchange -ya" and exited all. This brought the cryptsetup enter > passphrase line. I entered the passphrase and the system booted. > > - The interesting bit is that executing "update-initramfs" right > after "apt-get update; apt-get upgrade" will not output line with > "cryptsetup" (bellow). However, entering it after the faulty boot, > it will find the encrypted LV and note it in the cryptsetup line. > > update-initramfs: Generating /boot/initrd.img-2.6.34-1-686 > cryptsetup: NOTE: using /dev/mapper/data_vg-knightrider--sec instead > of /dev/data_vg/knightrider-sec for knightrider-sec > > Any idea where can be the problem?
ok, now i've an idea where the problem is located. in order to reproduce the situation, i need more detailed information. please send me contents of your /etc/fstab, /etc/crypttab. additionally i need the debug ouput of mkinitramfs, both righty after 'apt-get upgrade' and after the faulty boot. to produce debug output, you need to change the first line of /usr/share/initramfs-tools/hooks/cryptroot to '#!/bin/sh -x', and run the following command: 'sh -x mkinitramfs -o /tmp/initramfs.debug 2>/tmp/mkinitramfs.log' /tmp/mkinitramfs.log contains the required debug log. you can revert the changes in /usr/share/initramfs-tools/hooks/cryptroot afterwards. greetings, jonas
signature.asc
Description: Digital signature