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, 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 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
Bug#542928: [pkg-cryptsetup-devel] Bug#542928: cryptsetup fail with kernel 2.6.30-6
Hello, I use a standard sid install with only nvidia proprietary driver : Paquet : linux-image-2.6.30-1-amd64 Nouveau: oui État: installé Automatiquement installé: non Version : 2.6.30-6 Priorité : optionnel Section : kernel Responsable : Debian Kernel Team Taille décompressée : 86,5M Dépend: module-init-tools, initramfs-tools (>= 0.55) | yaird (>= 0.0.13) | linux-initramfs-tool Pré-dépend: debconf | debconf-2.0 Suggère: linux-doc-2.6.30, grub | lilo Est en conflit: initramfs-tools (< 0.55), yaird (< 0.0.13) Fournit: linux-image, linux-image-2.6, linux-modules-2.6.30-1-amd64 Description : Linux 2.6.30 image on AMD64 This package provides the binary image and pre-built loadable modules for Linux kernel 2.6.30 on all 64bit single- and multiprocessor AMD and Intel machines. This kernel also runs on a Xen hypervisor. It supports only unpriviledged (domU) operation. Étiquettes: admin::kernel, implemented-in::c, role::kernel 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) output of cat /proc /cmdline : (initramfs) root=/dev/mapper/debian-root ro output of cat /proc/crypto : name : stdrng driver : krng module : kernel priority : 200 refcnt : 1 selftest : passed type : rng seedsize : 0 name : md5 driver : md5-generic module : kernel priority : 0 refcnt : 1 selftest : passed type : shash blocksize : 64 digestsize : 16 descsize : 88 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) conf dev etc init lib lib64 proc root sbin scripts sys tmp var output of ls /dev/sd* : sda sda1 sda2 sda5 I can't mount any file system, they are in ext3 format. I try to add a fat32 usb stick (sdd1 in the laptop) but it fail to mount too ... So I can not get a full output of cat /proc/module : ... ata_piix libata sdhci_pci sdhci mmc_core led_class uhci_hcd firewire_ohci firewire_core crc_itu_t tg3 libphy scsi_mod intel_agp ehci_hcd video output thermal fan thermal_sy dm_mirror dm_region_hash dm_log dm_mod If I boot with 2.6.29-2 I get this phrase : enter passphrase to unlock the disk (dev/sda5(sda5_crypt): after entering the passphrase the system boot normaly : cat /proc/cmdline : root=/dev/mapper/debian-root ro cat /proc/crypto : name : ecb(arc4) driver : ecb(arc4-generic) module : ecb priority : 0 refcnt : 3 selftest : passed type : blkcipher blocksize: 1 min keysize : 1 max keysize : 256 ivsize : 0 geniv: name : arc4 driver : arc4-generic module : arc4 priority : 0 refcnt : 3 selftest : passed type : cipher blocksize: 1 min keysize : 1 max keysize : 256 name : sha256 driver : sha256-generic module : sha256_generic priority : 0 refcnt : 1 selftest : passed type : shash blocksize: 64 digestsize : 32 descsize : 168 name : sha224 driver : sha224-generic module : sha256_generic priority : 0 refcnt : 1 selftest : passed type : shash blocksize: 64 digestsize : 28 descsize : 168 name : cbc(aes) driver : cbc(aes-asm) module : kernel priority : 200 refcnt : 2 selftest : passed type : givcipher async: yes blocksize: 16 min keysize : 16 max keysize : 32 ivsize : 16 geniv: chainiv name : cbc(aes) driver : cbc(aes-asm) module : cbc priority : 200 refcnt : 2 selftest : passed type : blkcipher blocksize: 16 min keysize : 16 max keysize : 32 ivsize : 16 geniv: name : aes driver : aes-asm module : aes_x86_64 priority : 200 refcnt : 3 selftest : passed type : cipher blocksize: 16 min keysize : 16 max keysize : 32 name : aes driver : aes-generic module : aes_generic priority : 100 refcnt : 1 selftest : passed type : cipher blocksize: 16 min keysize : 16 max keysize : 32 name : stdrng driver : krng module : kernel priority : 200 refcnt : 2 selftest : passed type : rng seedsi
Bug#542928: [pkg-cryptsetup-devel] Bug#542928: cryptsetup fail with kernel 2.6.30-6
hello, On 22/08/2009 Guillaume JAOUEN wrote: > Since upgrade of the kernel to 2.6.30-6, my laptop fail to start and > doesn't ask for the lucks passphrase so my LVM setup can't start and > the system lost debian-root and debian-swap filesystem... > > Rebooting with 2.6.29 old kernel start properly. thanks for your bugreport. in order to detect the problem it would be very useful if you could provide further information: - do you use a selfcompiled kernel, or did you install the default debian kernel (in package linux-image-2.6.30-1-amd64)? - if you use a selfcompiled kernel, could you attach the .config of both the working 2.6.29 kernel and the broken 2.6.30 kernel? - when you boot the broken 2.6.30 kernel, what exactly happens? do you get some message like 'root filesystem not found'? do you see an emergency shell of the initramfs? - from the initramfs shell, please give the output of 'cat /proc/crypto' and 'cat /proc/modules'. you can do that by saving the output into a logfile on the boot fs. i.e. if your boot partition is /dev/sda1, do the following: mount /dev/sda1 /boot cat /proc/crypto > /boot/proc_crypto_log cat /proc/modules > /boot/proc_modules_log afterwards reboot with the working 2.6.29 kernel and attach both logfiles from /boot to your reply mail. greetings, jonas signature.asc Description: Digital signature
Bug#542928: cryptsetup fail with kernel 2.6.30-6
Package: cryptsetup Version: 2:1.0.7-1 Severity: critical Justification: breaks the whole system Hello, Since upgrade of the kernel to 2.6.30-6, my laptop fail to start and doesn't ask for the lucks passphrase so my LVM setup can't start and the system lost debian-root and debian-swap filesystem... Rebooting with 2.6.29 old kernel start properly. Best regards, Guillaume JAOUEN. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29-2-amd64 (SMP w/2 CPU cores) Locale: lang=fr...@euro, lc_ctype=fr...@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages cryptsetup depends on: ii dmsetup 2:1.02.36-2 The Linux Kernel Device Mapper use ii libc62.9-25 GNU C Library: Shared libraries ii libdevmapper1.02.1 2:1.02.36-1 The Linux Kernel Device Mapper use ii libpopt0 1.14-4 lib for parsing cmdline parameters ii libuuid1 2.16-3 Universally Unique ID library cryptsetup recommends no packages. Versions of packages cryptsetup suggests: ii dosfstools3.0.5-1utilities for making and checking ii initramfs-tools [linux-initra 0.93.4 tools for generating an initramfs ii udev 0.141-2/dev/ and hotplug management daemo -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
