Hello David, David Christensen <dpchrist@holgerdanske.com> wrote: > Loading Linux 3.2.0-0.bpo.2-amd64 ... > Loading initial ramdisk ... > Loading, please wait... > 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; ls /dev) > ALERT! /dev/mapper/sda2_crypt does not exist. Dropping to a shell! > Any suggestions? a) Check whether your initrd is, in general, capable of mounting the root device. Check whether the ‘cryptsetup’ command is available. If it is available, try the following: # cryptsetups luksOpen /dev/sda2 sda2_crypt It should ask for the encryption passphrase. If that works, check if /dev/mapper/sda2_crypt exists and if so, try to log out of the busybox shell. It should then continue booting. b) If that doesn’t work - either because cryptsetup is not available or because a module is missing from the initrd, boot into your old kernel. Then try to rebuild the initrd (update-initramfs, IIRC) with the verbose flag and check if it adds the cryptsetup binary and associated kernel modules. If it did, try to reboot. c) If the modules are not added to the initrd or if the cryptsetup binary is not added to the initrd, check if you can add the associated modules to /etc/initramfs-tools/modules. Additionally, you might want to change MODULES=dep to MODULES=most in initramfs.conf and test if that works. You might also want to check whether the packages mentioned at the link provided by Camaleón (lvm2, cryptsetup) are installed, but they _should_ be installed. Best regards, Claudius -- Do not drink and drive. http://chubig.net telnet nightfall.org 4242
Attachment:
signature.asc
Description: PGP signature