grubby: unable to open /boot/boot.b: No such file or directory

[Michael Schwendt]

On Fri, 27 Jun 2008 01:23:21 +0200, Thomas Rabaix wrote:

> ok, this is my partition table : sda1 and sda2 are ext3
> /dev/sda1             9,9G  3,3G  6,1G  36% /
> /dev/sda2             449G  709M  425G   1% /var
> 
> # e2label /dev/sda1
> /
> # e2label /dev/sda2
> /var
> 
> Yes the file is located into /boot/grub/grub.conf. but there is not
> specific partition for grub, can it be an issue, does grub know how to
> read a etx3 partition ?.

Yes. It can read ext2/ext3 directly. It even loads its grub.conf that
way.
 
> # cat /boot/grub/grub.conf
> default=0
> timeout=50
> title 2.6.25.6-27.fc8
>        root (hd0,0)
>        kernel (hd0,0)/boot/vmlinuz-2.6.25.6-27.fc8 ro root=/dev/sda1
>        initrd (hd0,0)/boot/initrd-2.6.25.6-27.fc8.img
> 
> let's try to understand the last 3 lines
>   - root : " Set the current root device to the device device", so the
> root here is sda1 so h0,0 in grub syntax

GRUB's root is the partition on which the /boot directory is found.
In your case: /dev/sda1 = (hd0,0)

>   - kernel : "define the kernel to load", so we load the kernel from
> disk h0,0 with read only attribute (not sure about the need of this,
> does the system switch to rw after loading?) and we define the root to
> the kernel as /dev/sda1 (look redundant as it is the same as the grub
> one)

It *is* redundant because of the "root (hd0,0)" in the previous line.

As an optimisation, I would boot with root=LABEL=foo instead of root=/dev/sda1
and give sda1 label "foo" and also update /etc/fstab.

> So in your opinion does the grub configuration look fine ?

You can run "grub" as superuser root in a terminal and play in its
command-line shell. Commands like

grub> find /boot/grub/grub.conf
 (hd0,7)
 (hd1,6)
 (hd1,8)

should print (hd0,0) in your case.