[SLL] booting a new kernel - unable to mount root fs

[Jarod Wilson]

On Wed, 2009-02-04 at 08:34 -0800, Mathew D. Watson wrote:
> I have been trying to boot the new kernel I built last week, but I have 
> not yet succeeded. After studying the GRUB manual (and many failed boot 
> attempts), I have finally gotten my menu.lst file to the point where I 
> can't find anything wrong with it.
> 
> The new kernel is /boot/vmlinuz-test.
> 
> The last several lines of /boot/grub/menu.lst are as follows.
> 
> ### END DEBIAN AUTOMAGIC KERNELS LIST
> title		linux-test
> root		(hd0,0)
> uuid		7882317c-a329-41cb-b59d-f7a7d0212c0c
> kernel		/boot/vmlinuz-test root=UUID=7882317c-a329-41cb-b59d-f7a7d0212c0c ro

^^^ no initrd ^^^

> For reference:
> The following entry from /boot/menu.lst boots the stock kernel.
> 
> title		Ubuntu 8.10, kernel 2.6.27-11-generic
> uuid		7882317c-a329-41cb-b59d-f7a7d0212c0c
> kernel		/boot/vmlinuz-2.6.27-11-generic root=UUID=7882317c-a329-41cb-b59
> d-f7a7d0212c0c ro quiet splash
> initrd		/boot/initrd.img-2.6.27-11-generic
> quiet

^^^ has initrd ^^^


> I have tried this without the root (hd0,0) line.
> I have also tried using root=/dev/sda1 as a kernel argument.
> 
> The error message is:
> unable to mount root fs on unknown-block(0,0)
 
Did you build your file system driver into the kernel, or is it built as
a module? If its a module, you *need* an initrd to house the module so
that it can be loaded so that the kernel knows how to handle your root
file system properly.

-- 
Jarod Wilson
jarod at wilsonet.com