Bug#542928: [pkg-cryptsetup-devel] Bug#542928: Bug#542928: cryptsetup fail with kernel 2.6.30-6
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 signature.asc Description: Digital signature
Bug#542928: [pkg-cryptsetup-devel] Bug#542928: Bug#542928: cryptsetup fail with kernel 2.6.30-6
hey, On 27/08/2009 Guillaume JAOUEN wrote: I start again the laptop with kernel 2.6.30-1 amd64 and write carefully the output during the boot : ... Begin : Assembling all MD arrays... mdadm : No arrays found in config file or automatically Failure : failed to assemble all arrays. done. 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 done. up to here, everything seems fine: mdadm is started but no software raid configured, then lvm is started but no volume group available yet. Begin: Waiting for root file system... done Gave up waiting for root device. that one indicates that the root device is not available to cryptroot. for some reason, the encrypted device (/dev/sda5) is not available. either missing hardware driver or wrong device might be reasons. 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;ls /dev) ALERT! /dev/mapper/debian-root does not exist. Dropping to a shell ! BusyBox v1.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) in the initramfs emergency shell, please give output of the following commands: cat /conf/conf.d/cryproot ls -al /dev/sda5 and if the device file exists, try unlocking it manually: cryptsetup luksOpen /dev/sda5 sda5_crypt lvm vgchange -a y ls -al /dev/mapper/debian-root if the device doesn't exist, then please give output of 'ls -al /dev' from initramfs as well. You'll find the output of this command in attachement : dell-xps:/boot/grub# sh -x mkinitramfs --supported-target-version=2.6.30-1-amd64 \ -o /tmp/initramfs-2.6.30-1-amd64 2/tmp/initramfs-log dell-xps:/boot/grub# sorry, the command was wrong. please use the following instead: sh -x mkinitramfs -o /tmp/initramfs 2.6.30-1-amd64 2/tmp/initramfs.log and attach /tmp/initramfs.log to the mail. also, please update your initramfs, try to reboot with the broken kernel afterwards and seee whether that helps: mv /boot/initramfs-2.6.30-1-amd64 /boot/initramfs-2.6.30-1-amd64.orig update-initramfs -c -k 2.6.30-1-amd64 sorry for asking that many questions, but i simply don't have a straight idea what the problem on your system might be. apparently the same kernel and system setup works for me. greetings, jonas signature.asc Description: Digital signature
Bug#542928: [pkg-cryptsetup-devel] Bug#542928: Bug#542928: cryptsetup fail with kernel 2.6.30-6
hey again, On 25/08/2009 Guillaume JAOUEN wrote: I use a standard sid install with only nvidia proprietary driver : thanks for the information. i run several debian/sid installations with linux-image-2.6.30-1-amd64 (2.6.30-6) without any issues, and so far I was unable to reproduce the bug you reported. let's see ... This kernel also runs on a Xen hypervisor. It supports only unpriviledged (domU) operation. so the system on which you discovered the bug runs as domU, right? 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 volume group debian not found. skipping volume group debian. 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) do you use lvm? seems like the lvm setup is broken. in case that your root device is on lvm (the default for guided encrypted partitioning in debian-installer), then that might be the real issue here. output of cat /proc /cmdline : (initramfs) root=/dev/mapper/debian-root ro output of mount /dev/sda1 /boot/ : mount: mounting /dev/sda1 on /boot/ failed no such file or directory. output of ls / : bin boot ( I had to create it with mkdir) ok, and is it possible to mount /dev/sda1 after creating /boot? i.e. 'mkdir /boot mount -t ext3 /dev/sda1 /boot' output of ls /dev/sd* : sda sda1 sda2 sda5 from the initramfs, please give the output of 'for dev in /dev/sda[125]; do echo $dev:; fstype $dev; done' I can't mount any file system, they are in ext3 format. what is the exact error message if you try to mount them? on your system (booted with a working kernel), please give the output of /etc/fstab and /etc/crypttab. greetings, jonas signature.asc Description: Digital signature
