On 10/08/10 14:03, Chris Parsons wrote: > Hi all, > > I've completed most of LFS 6.6. I'm on Chapter 8 of the final stages of > trying to get it to boot independently of the host Linux system. It > keeps stopping with a kernel panic message and/or "error: invalid > signature" depending on how I try to launch it. Here are some > background details. > > - Periodically do LFS builds primarily to maintain and increase my Linux > knowledge. > - Using VMware Workstation 7.1 > - Installed Ubuntu 10.4 onto one virtual disk. System sees this disk as > /dev/sda > - Ran through LFS 6.6. > - Added another Vmware disk for LFS. Ubuntu and LFS see this disk as > /dev/sdb. All of the LFS is on this disk. (sdb1) > - Added another VMware disk for LFS swap. Ubuntu and LFS see this disk > as /dev/sdc > - Aside from some minor build issues, build went ok. >
Never used VMware so I can't comment on what effect it may have > # Begin /etc/fstab fstab is irrelevant if the kernel is panicking > When I reboot to the Ubuntu GRUB2 loader screen and choose the LFS > entry, the only error message displayed is "error: invalid signature > press any key to continue.." > > If I then try to manually enter commands as follows, I get: > grub> root (hd1,1) > grub> linux /boot/vmlinux-2.6.32.8 root=/dev/sdb1 > grub> boot > > VFS: Unable to mount root fs via NFS, trying floppy. > VFS: Cannot open root device "sdb1" or unknown-block(2,0) > Please append a correct "root=" boot option; here are the available > partitions: > 0b00 1048575 sr0 driver: sr > Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(2,0?) > > Could someone point me in the right direction? > It could be that the kernel sees the partition you're trying to boot as /dev/sda1 so try that. However, it could also be that your kernel hasn't been compiled with the drivers for your motherboard's chipset or the filesystem you're using. Also, if you didn't use libata but selected the older, deprecated ATA drivers, it could be that your kernel sees the partition as /dev/hdb1 If the problem was with grub it would give an error of some sort. My guess is that the problem lies with your kernel config. Andy -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
