On Mon, December 11, 2006 18:14, Enrico Gatto said: > On Mon, 11 Dec 2006 10:59:24 +0100 (CET) > David Härdeman <[EMAIL PROTECTED]> wrote: > >> could you please provide me with >> .. >> /etc/fstab, > > /dev/mapper/croot / ext3 defaults 0 1 > >> a list of your boot parameters > > /boot/boot/grub/menu.lst contains >
Just to be sure, you meant /boot/grub/menu.lst, right? > kernel /vmlinuz-2.6.18.2 root=/dev/evms/root quiet ro Could you please try to boot after changing the root parameter to root=/dev/mapper/croot and let me know what happens? > initrd /initrd.img-2.6.18.2 > savedefault > >> and a description of your setup (I >> assume you use a combination of evms and crypto?) > > Yes, I'm using evms volumes, some of them are encrypted with > cryptsetup, but I'm having the same problem on another machine without > evms (same configuration except for device names /dev/evms/* that are > substituded by /dev/hd??). When the boot fails and I am on a busybox > shell, I can do > mount /dev/mapper/croot /root -t ext3 > and then the boot process continues correctly. Did you set up the system yourself or did you do it using the crypto support in debian-installer? It seems your root parameter is wrong (it should be the final root dev, i.e. the crypto dev, not the one that is used to setup the crypto device). Please try on this box as well to change the root param to something like root=/dev/mapper/croot. -- David Härdeman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
