[pkg-cryptsetup-devel] Bug#542928: Bug#542928: Bug#542928: cryptsetup fail with kernel 2.6.30-6

[Jonas Meurer]

hey,

On 26/08/2009 Guillaume JAOUEN wrote:
> You'll find in this mail all the output log.
> 
> I add also dmesg output dpkg get-selections, lshw and lspci output.
> 
> I hope it may help you understand what's happening :
> - dpkg-gzt-selections.txt was made under 2.6.29-2 kernel boot.
> - cat-proc-crypto.log was made under 2.6.30-1 kernel boot.
> - cat-proc-crypto-2.6.29-2.log was made under 2.6.29-2 kernel boot.
> - cat-proc-devices.log was made under 2.6.30-1 kernel boot.
> - cat-proc-devices-2.6.29-2.log was made under 2.6.29-2 kernel boot.
> - cat-proc-modules.log was made under 2.6.30-1 kernel boot.
> - cat-proc-modules-2.6.29-2.log was made under 2.6.29-2 kernel boot.
> - config-2.6.29-2-amd64 and config-2.6.30-1-amd64 were generated into /boot
> - dmesg.log was made under 2.6.30-1 kernel boot.
> - dmesg.2.6.29-2.log was made under 2.6.29-2 kernel boot.
> - lshw-2.6.29-2.log was made under 2.6.29-2 kernel boot.
> - lspci-2.6.29-2.log was made under 2.6.29-2 kernel boot.
> - ps-aux.log was made under 2.6.30-1 kernel boot.
> - uname.log was made under 2.6.30-1 kernel boot.
> - cat-etc-crypttab-2.6.29-2.log was made under 2.6.29-2 kernel boot.
> - cat-etc-fstab-2.6.29-2.log was made under 2.6.29-2 kernel boot.
> 
> With these elements I hope I give you the maximum details about my
> hardware and software configuration.

ok, i just tried to reproduce the bug with similar setup (lvm over luks)
and a selfcompiled kernel using your config-2.6.30-1-amd64, but i
failed. the system still boots as expected.

> My laptop doesn't use xen hypervisor even if the kernel message
> display this information.

some of the xen packages you've installed don't exist in the archive
any longer, xen 3.2 has been replaced by xen 3.4 in the meanwhile.

> I agree with you when you're saying that the lvm setup is broken
> that's what my system complain about since the upgrade of the kernel
> and it's link to the fact that as the device /dev/sda5 isn't
> decrypted, my lvm setup wasn't available on boot process.

in another mail you wrote:

> Output during boot :
> debian kernel 2.6.30-1-amd64
> ...
> failure : failed to assemble all array volume group "debian" not found.
> skipping volume group debian.
> unable to find LVM volume debian/root
> unable to find LVM volume debian/swap_1
> done.
> begin : waiting for root file system... done
> gave up waiting for root device. common problems :
> - boot args cat /proc/cmdline
> - check rootdelay =(did the system wait long enough?)
> - check root =(did the system wait for the right device?)
> - missing modules ( cat /proc/modules)
> ALERT! /dev/mapper/debian-root does not exist
> dropping to a shell.
> busybox V.1.13.3 (debian 1:1.13.3-1) built-in shell (ash)
> Enter 'help' for a list of built-in commands.
> /bin/sh: can't access tty: job control turned off.
> (initramfs)

could you verify that this is the exact output you get at trying to boot
the broken linux kernel 2.6.30-1-amd64?
this is the output i get at booting with a linux kernel 2.6.30-1-amd64
built with your kernel config:
 Volume group "debian" not found
 Skipping volume group debian
Unable to find LVM volume debian/root
 Volume group "debian" not found
 Skipping volume group debian
Unable to find LVM volume debian/swap_1
Unlocking the disk /dev/hda2 (hda2_crypt)
Enter passphrase:

the LVM errors are harmless. they only appear for the reason that lvm
is started both before and after cryptroot. that's to support both "lvm
over luks" and "luks over lvm" setups.

if the boot output above is what you get, then a broken initramfs file
which misses the cryptroot initramfs script might be the reason.
please attach the output of the following commands as well (from a
working system, i.e. with kernel 2.6.29-1-amd64):

ls -al /boot/
[ -f /boot/grub/menu.lst ] && cat /boot/grub/menu.lst
[ -f /boot/grub/grub.conf ] && cat /boot/grub/grub.conf

and attach /tmp/initramfs-2.6.30-1-amd64.log after executing

sh -x mkinitramfs --supported-target-version="2.6.30-1-amd64" \
	-o /tmp/initramfs-2.6.30-1-amd64 2>/tmp/initramfs-log

greetings,
 jonas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-cryptsetup-devel/attachments/20090826/32513cf9/attachment.pgp>