Andrew Benton wrote:
> On 12/04/10 14:45, [email protected] 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.
vmware should be fine.
>> ### 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
>> linux /vmlinux-2.6.32.8-lfs-6.6 root=/dev/sda2 ro
>> }
> Are these search lines needed? I don't put them in my grub.cfg
Andy, the search lines are added by GRUB, they are ignored by LFS, but I
agree that it would be clearer if they were removed. Otherwise, the
entry looks correct.
>> 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)
> 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.
Not building a required driver into the kernel is almost certainly the
problem here. lsmod on an earlier system and lspci are exactly the
right tools to figure out the needed drivers. After that rebuilding the
kernel and retrying are the boot will be needed.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
