Andrew Benton wrote:
> On Sun, 13 Nov 2011 10:36:34 +0000
> spiky <[email protected]> wrote:
> 
>> Ok I used grub prompt it showed the usb drive
>> hd0,msdos1(LFS-7.0),2(swap),3(home).
>> then entered set root=(hd0,msdos)

That seems right.  The msdos part is the boot record type, not a 
partition type,


>> linux /boot/vmlinux-3.1-7.0 (it found with tab)root=/devsda1

Is there a missing / or just a typo?  Should be /dev/sda1

>> boot

>> i get 
>> "no filesystem could mount root tried ext 3 ,2, 4 etc
>> also Kernel panic not syncing VFS unable to mount root fs on unknown
>> block (8.1).

When you have a problem with a lot of new things, isolate the new from 
the old.  I recommend going back to a ext3 partition until you get it 
working.

>> This is the same as I get when I let it boot as normal for this drive.

> That looks like a kernel panic, which is good because it means you've
> got past the BIOS and grub. 

Right.

> It
> could also be that the kernel config is fine but you've passed it the
> wrong root= option on the grub command line. 

That would be my thought too.

I'm pretty sure I'd get a
> similar looking kernel panic if I tried to boot my kernel with root=
> pointing to my swap partition. Another possibility is that the kernel
> sees the partition as /dev/sdb1 or /dev/hdc1 or some such. There's no
> way to be sure other than to try all the combinations you can think of
> and see what works. If none of them work then the problem is probably
> with your kernel config so you'll have to work on that recompile your
> kernel until you get one that boots.

BTW, the kernel doesn't understand root=UUID=uuid.  You have to have a 
initrd for that.  I'm not sure if the kernel understands 
root=LABEL=label or not.

Just remember that grub's root and the kernel's root are not, in 
general, the same thing, although they could point to the same place.

   -- Bruce
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to