On 12/04/10 14:45, mas...@mail.com wrote:
> Hi i got this error when i tried to boot in to my LFS system.
> could it be that my fstab is screwed up, or is it something i forgot to
> do with the kernel?
It's definitely nothing to do with fstab, quite possibly something to do with
your kernel config. I can boot this system with no /etc/fstab. It causes errors
for the bootscripts but the kernel mounts the partition grub tells it to an it
gets to a login prompt for root to login and fix the situation.
> I'm using the LFS 6.6 book, and i am doing this in vmware.
I've no idea what vmware is but I expect it has something to do with your
problem
> This is my grub.cfg:
> #
> # DO NOT EDIT THIS FILE
> #
> # It is automatically generated by /usr/sbin/grub-mkconfig using
> templates
> # from /etc/grub.d and settings from /etc/default/grub
> #
>
> ### BEGIN /etc/grub.d/00_header ###
> set default=0
> set timeout=5
> ### END /etc/grub.d/00_header ###
>
> ### BEGIN /etc/grub.d/10_linux ###
> menuentry "GNU/Linux, with Linux 2.6.32.8-lfs-6.6" {
> insmod ext2
> set root=(hd0,1)
> search --no-floppy --fs-uuid --set
> dd263110-8c28-48f1-bb0e-5c779c97e9ac
Are these search lines needed? I don't put them in my grub.cfg
> linux /vmlinux-2.6.32.8-lfs-6.6 root=/dev/sda2 ro
> }
> menuentry "GNU/Linux, with Linux 2.6.32.8-lfs-6.6 (recovery mode)" {
> insmod ext2
> set root=(hd0,1)
> search --no-floppy --fs-uuid --set
> dd263110-8c28-48f1-bb0e-5c779c97e9ac
Are these search lines needed? I don't put them in my grub.cfg
> when i reboot i get:
> Kernel panic - not syncing: VFS; Unable to mount root fs on
> unknown-block(2.0)
> VFS: Cannot open root device "sda2" or unknown-block(2.0)
> Please append a correct "root=" boot option; here are the available
> partitions:
> 0b00 1048575 sr0 driver: sr
>
> What could be the problem?
My guess is that you haven't compiled support for your motherboard's chipset
into
your kernel. Use lspci to learn about your motherboard's chipset. Also, on your
host system, use lsmod to see what modules it is using.
It could be that you didn't compile libata and the kernel is calling
the partition hda2. It could also be that you didn't compile in support for your
root filesystem.
Andy
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
