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
