On Sun, November 25, 2007 18:57, Jonas Meurer wrote: > On 25/11/2007 Max Vozeler wrote: >> quoting from #428329: >>> ... >>> >>> Setting up cryptographic volume sda3_crypt (based on /dev/sda3) >>> Enter LUKS passphrase: _ <-- I give the passphrase here >>> key slot 0 unlocked. >>> Command successfull. >>> Done. ... >>> /init: /init: 1: cannot open /dev/root: No such device or address
Sounds fishy, it should not care about /dev/root (but rather /dev/mapper/sda3_crypt) at this stage. > This all happens because the rootfs is not mounted at all. So the > question here is, what exactly tries (and fails) to mount /dev/root? > > I guess that some configuration script at installation simply ignored > the fact that the rootfs is encrypted, and instead of the dm-crypt root > device (like /dev/mapper/root) added /dev/root to /etc/fstab. > > David, you have better knowledge of the whole installation process, what > do you think about that? I haven't used lilo for years on any machine that I admin but it sounds like the lilo stage of debian-installer got the root device wrong (and passes root=/dev/root to the kernel or something like that). Please provide the contents of /proc/cmdline using the initramfs shell. Also, when in the initramfs shell, you might be able to do something like symlink /dev/root to /dev/mapper/whatever_the_real_root_is_called and then type "exit" which will try to resume the boot. If that works, you should be able to inspect the contents of the lilo config file. -- David Härdeman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
