|
|||||||||||
|
Re: Strange kernel boot hang
From: Douglas A. Tutty <dtutty(at)porchlight.ca>
Date: Tue Dec 18 2007 - 12:10:22 EST
> By mounting the filesystems and chrooting into the debian personality to
It appears that you are using LVM for /usr, /home, and /var. To
eliminate LVM problems, try booting with init=/bin/sh. This should
remove any need for those partitions and allow you to focus on getting
the kernel to boot.
which would change your kernel command line to: kernel (hd0,0)/vmlinuz ro root=/dev/sda3 init=/bin/sh I don't know that you need the console= line unless you're using a non-standard console. I've lost what you've tried when and in what order, so I appologize if you've already tried this: Ensure that when you boot, you get the grub menu. If you don't, then grub can't see the /boot directory/partition. If it can't see it, it can't load the kernel from it. If you need to, install grub, then run dpkg-reconfigure [the kernel package] to get the grub menu built correctly and rebuild the initrd. Then manually edit /boot/grub/menu.list so that you automatically get an entry for the standard kernel with init=/bin/sh. After the edit, re-run update-grub to get it to regenerate menu.list. Once you get grub itself working, you can work on getting the kernel to boot with init=/bin/sh. What is the error you get from the kernel? Can it find the root partition? Doug. -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.orgReceived on Tue Dec 18 21:41:38 2007 This archive was generated by hypermail 2.1.8 : Wed Feb 27 2008 - 19:01:56 EST |
||||||||||
|
|||||||||||