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

Hello,

I just update my Fedora 8 with yum, and I don't want to reboot it as I
get an error during the update. I cannot easily rescue it in
case of problem as the host is located at a remote location (datacenter).

so the /boot/boot.b is missing, the bootloader is lilo.

How can I regenerate this file ?

I have include more information about my configuration.

Thanks for your help.

Thomas

INFORMATION
============

I have a Fedora 8 :

# cat /etc/fedora-release
Fedora release 8 (Werewolf)

I had updated the system from a FC4 to Fedora 8 a month ago, I just
follow the instruction from the wiki. Everything went fine.

Now today I run the command sudo yum update , I resume the
dependencies to kernel packages :

Installing:
kernel i686 2.6.25.6-27.fc8 updates 18 M
kernel-devel i686 2.6.25.6-27.fc8 updates 5.2 M

Updating:
kernel-headers i386 2.6.25.6-27.fc8 updates 734 k

Removing:
kernel i686 2.6.23.17-88.fc7 installed 44 M
kernel-devel i686 2.6.23.17-88.fc7 installed 15 M

during the installation I get

Installing: kernel ##################### [ 20/144]
grubby: unable to open /boot/boot.b: No such file or directory

The bootloader is Lilo :
# dd if=/dev/sda obs=512 count=1 2>/dev/null|grep LILO
Binary File ... matches

my lilo.conf

#cat lilo.conf
prompt
timeout=50
default=2.6.25.6-27.fc8
boot=/dev/sda
map=/boot/map
install=/boot/boot.b
lba32
append=""
#serial=0,9600n8

image=/boot/vmlinuz-2.6.25.6-27.fc8
label=2.6.25.6-27.fc8
read-only
root=/dev/sda1
initrd=/boot/initrd-2.6.25.6-27.fc8.img
image=/boot/vmlinuz-2.6.24.7-92.fc8
label=2.6.24.7-92.fc8
read-only
root=/dev/sda1
initrd=/boot/initrd-2.6.24.7-92.fc8.img
image=/boot/bzImage-2.6.24.5-xxxx-grs-ipv4-32
label=linux
read-only
root=/dev/sda1

The default kernel is present
# ls -lsa /boot/vmlinuz-2.6.25.6-27.fc8
2052 -rw-r--r-- 1 root root 2095904 jun 13 22:47 /boot/vmlinuz-2.6.25.6-27.fc8

--
Thomas Rabaix

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

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

On Thu, 26 Jun 2008 12:03:50 +0200, Thomas Rabaix wrote:

> Hello,
>
> I just update my Fedora 8 with yum, and I don't want to reboot it as I
> get an error during the update. I cannot easily rescue it in
> case of problem as the host is located at a remote location (datacenter).
>
> so the /boot/boot.b is missing, the bootloader is lilo.

LILO is not included in the Fedora repositories.
Fedora uses GRUB for a long time.

> How can I regenerate this file ?

By reinstalling LILO. Manually or as a package.

> Installing: kernel ##################### [ 20/144]
> grubby: unable to open /boot/boot.b: No such file or directory
>
> The bootloader is Lilo :
> # dd if=/dev/sda obs=512 count=1 2>/dev/null|grep LILO
> Binary File ... matches

That test is invalid.

$ sudo dd if=/dev/sda obs=512 count=1 2>/dev/null|strings
lbaLILO
ZRrI
D|f1
GRUB
Geom
Hard Disk
Read
Error

--
Fedora release 8 (Werewolf) - Linux 2.6.25.6-27.fc8
loadavg: 1.37 1.15 1.09

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

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

Hello,

Thanks for your reply. It is what I have. I have to mention that I
updgrade from a FC4 to F8.
More over I have a file called 'boot.0800', can it be the boot.b file (backup) ?

# dd if=/dev/sda obs=512 count=1 2>/dev/null|strings
LILO
7H9|
LILOu)^h
`UUfP
fPYX
@](:


On Thu, Jun 26, 2008 at 5:06 PM, Michael Schwendt <mschwendt@gmail.com> wrote:
> On Thu, 26 Jun 2008 12:03:50 +0200, Thomas Rabaix wrote:
>
>> Hello,
>>
>> I just update my Fedora 8 with yum, and I don't want to reboot it as I
>> get an error during the update. I cannot easily rescue it in
>> case of problem as the host is located at a remote location (datacenter).
>>
>> so the /boot/boot.b is missing, the bootloader is lilo.
>
> LILO is not included in the Fedora repositories.
> Fedora uses GRUB for a long time.
>
>> How can I regenerate this file ?
>
> By reinstalling LILO. Manually or as a package.
>
>> Installing: kernel ##################### [ 20/144]
>> grubby: unable to open /boot/boot.b: No such file or directory
>>
>> The bootloader is Lilo :
>> # dd if=/dev/sda obs=512 count=1 2>/dev/null|grep LILO
>> Binary File ... matches
>
> That test is invalid.
>
> $ sudo dd if=/dev/sda obs=512 count=1 2>/dev/null|strings
> lbaLILO
> ZRrI
> D|f1
> GRUB
> Geom
> Hard Disk
> Read
> Error
>
> --
> Fedora release 8 (Werewolf) - Linux 2.6.25.6-27.fc8
> loadavg: 1.37 1.15 1.09
>
> --
> fedora-list mailing list
> fedora-list@redhat.com
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>



--
Thomas Rabaix

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

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

On Thu, 2008-06-26 at 17:06 +0200, Michael Schwendt wrote:
> On Thu, 26 Jun 2008 12:03:50 +0200, Thomas Rabaix wrote:
>
> > Hello,
> >
> > I just update my Fedora 8 with yum, and I don't want to reboot it as I
> > get an error during the update. I cannot easily rescue it in
> > case of problem as the host is located at a remote location (datacenter).
> >
> > so the /boot/boot.b is missing, the bootloader is lilo.
>
> LILO is not included in the Fedora repositories.
> Fedora uses GRUB for a long time.
>
> > How can I regenerate this file ?
>
> By reinstalling LILO. Manually or as a package.
>
> > Installing: kernel ##################### [ 20/144]
> > grubby: unable to open /boot/boot.b: No such file or directory
> >
----
watching this thread with interest.

I have several Dell Optiplex 320's that will not boot with grub but will
boot with lilo and so I have lilo installed on them.

Unfortunately though, kernel updates do produce the error above (unable
to open /boot/boot.b) generated by grubby. Is there any way around
getting grubby to re-run lilo to execute an update when new kernels are
installed?

Craig

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

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

On Thu, 26 Jun 2008 17:15:10 +0200, Thomas Rabaix wrote:

> Hello,
>
> Thanks for your reply. It is what I have. I have to mention that I
> updgrade from a FC4 to F8.

Doesn't make a difference, because FC4 also used GRUB.

> More over I have a file called 'boot.0800', can it be the boot.b file (backup) ?
>

No, afair it is the backup copy of the boot sector before LILO was
installed into it. The backups have different names for (E)IDE and
SCSI. Read the manual page. It's explained there.

/boot/boot.b is part of LILO. If you lost it, reinstall LILO.

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

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

On Thu, 26 Jun 2008 08:16:58 -0700, Craig White wrote:

> watching this thread with interest.
>
> I have several Dell Optiplex 320's that will not boot with grub but will
> boot with lilo and so I have lilo installed on them.

Is this problem known upstream?

> Unfortunately though, kernel updates do produce the error above (unable
> to open /boot/boot.b) generated by grubby. Is there any way around
> getting grubby to re-run lilo to execute an update when new kernels are
> installed?

With LILO, no. LILO must be rewritten with every change in lilo.conf.
GRUB, on the contrary, must not be rewritten after modifying grub.conf,
because it can read the ext2/ext3 fs directly to load its config file.

If you're interested in where grubby is executed, take a look at
/sbin/new-kernel-pkg which is called by the "kernel" package scriptlets.

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

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

On Thu, 26 Jun 2008 18:08:20 +0200, Michael Schwendt wrote:

> On Thu, 26 Jun 2008 08:16:58 -0700, Craig White wrote:
>
> > watching this thread with interest.
> >
> > I have several Dell Optiplex 320's that will not boot with grub but will
> > boot with lilo and so I have lilo installed on them.
>
> Is this problem known upstream?
>
> > Unfortunately though, kernel updates do produce the error above (unable
> > to open /boot/boot.b) generated by grubby. Is there any way around
> > getting grubby to re-run lilo to execute an update when new kernels are
> > installed?
>
> With LILO, no. LILO must be rewritten with every change in lilo.conf.
> GRUB, on the contrary, must not be rewritten after modifying grub.conf,

typo: must not => need not

> because it can read the ext2/ext3 fs directly to load its config file.
>
> If you're interested in where grubby is executed, take a look at
> /sbin/new-kernel-pkg which is called by the "kernel" package scriptlets.

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

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

On Thu, 2008-06-26 at 18:08 +0200, Michael Schwendt wrote:
> On Thu, 26 Jun 2008 08:16:58 -0700, Craig White wrote:
>
> > watching this thread with interest.
> >
> > I have several Dell Optiplex 320's that will not boot with grub but will
> > boot with lilo and so I have lilo installed on them.
>
> Is this problem known upstream?
----
very much so
https://bugzilla.redhat.com/show_bug.cgi?id=379201
https://bugzilla.redhat.com/show_bug.cgi?id=219715
----
>
> > Unfortunately though, kernel updates do produce the error above (unable
> > to open /boot/boot.b) generated by grubby. Is there any way around
> > getting grubby to re-run lilo to execute an update when new kernels are
> > installed?
>
> With LILO, no. LILO must be rewritten with every change in lilo.conf.
> GRUB, on the contrary, must not be rewritten after modifying grub.conf,
> because it can read the ext2/ext3 fs directly to load its config file.
>
> If you're interested in where grubby is executed, take a look at
> /sbin/new-kernel-pkg which is called by the "kernel" package scriptlets.
----
been there...never could figure out what to change
as noted here...
https://bugzilla.redhat.com/show_bug.cgi?id=219715#c18

Craig

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

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

On Thu, 26 Jun 2008 09:27:46 -0700, Craig White wrote:

> On Thu, 2008-06-26 at 18:08 +0200, Michael Schwendt wrote:
> > On Thu, 26 Jun 2008 08:16:58 -0700, Craig White wrote:
> >
> > > watching this thread with interest.
> > >
> > > I have several Dell Optiplex 320's that will not boot with grub but will
> > > boot with lilo and so I have lilo installed on them.
> >
> > Is this problem known upstream?
> ----
> very much so
> https://bugzilla.redhat.com/show_bug.cgi?id=379201
> https://bugzilla.redhat.com/show_bug.cgi?id=219715

Those are about grub and the kernel. If you think grubby suffers from a
bug when updating LILO installations, grubby is part of the "mkinitrd"
package.

> ----
> >
> > > Unfortunately though, kernel updates do produce the error above (unable
> > > to open /boot/boot.b) generated by grubby. Is there any way around
> > > getting grubby to re-run lilo to execute an update when new kernels are
> > > installed?
> >
> > With LILO, no. LILO must be rewritten with every change in lilo.conf.
> > GRUB, on the contrary, must not be rewritten after modifying grub.conf,
> > because it can read the ext2/ext3 fs directly to load its config file.
> >
> > If you're interested in where grubby is executed, take a look at
> > /sbin/new-kernel-pkg which is called by the "kernel" package scriptlets.
> ----
> been there...never could figure out what to change
> as noted here...
> https://bugzilla.redhat.com/show_bug.cgi?id=219715#c18

Well, if you have reason to believe that grubby does something wrong,
find out what it does wrong. Run it manually, it has a man page, too.
And /boot/boot.b must exist when it is specified in lilo.conf. Do you
say that grubby deletes that file by accident?

And if you're really fed up with grubby, you could modify new-kernel-pkg
to execute your own lilo-update script/program instead of grubby.

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

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

Ok, my host install FC4 with lilo, so I update to F8. I suppose the
update script from Fedora keep lilo and don't use grub at all.

Now how can I reinstall lilo to make boot.b appears. I have only one
chance :) (remote location)

I am not sure that my system will reboot properly without this file,
am i right ?

Thanks

Thomas

On Thu, Jun 26, 2008 at 8:42 PM, Michael Schwendt <mschwendt@gmail.com> wrote:
> On Thu, 26 Jun 2008 09:27:46 -0700, Craig White wrote:
>
>> On Thu, 2008-06-26 at 18:08 +0200, Michael Schwendt wrote:
>> > On Thu, 26 Jun 2008 08:16:58 -0700, Craig White wrote:
>> >
>> > > watching this thread with interest.
>> > >
>> > > I have several Dell Optiplex 320's that will not boot with grub but will
>> > > boot with lilo and so I have lilo installed on them.
>> >
>> > Is this problem known upstream?
>> ----
>> very much so
>> https://bugzilla.redhat.com/show_bug.cgi?id=379201
>> https://bugzilla.redhat.com/show_bug.cgi?id=219715
>
> Those are about grub and the kernel. If you think grubby suffers from a
> bug when updating LILO installations, grubby is part of the "mkinitrd"
> package.
>
>> ----
>> >
>> > > Unfortunately though, kernel updates do produce the error above (unable
>> > > to open /boot/boot.b) generated by grubby. Is there any way around
>> > > getting grubby to re-run lilo to execute an update when new kernels are
>> > > installed?
>> >
>> > With LILO, no. LILO must be rewritten with every change in lilo.conf.
>> > GRUB, on the contrary, must not be rewritten after modifying grub.conf,
>> > because it can read the ext2/ext3 fs directly to load its config file.
>> >
>> > If you're interested in where grubby is executed, take a look at
>> > /sbin/new-kernel-pkg which is called by the "kernel" package scriptlets.
>> ----
>> been there...never could figure out what to change
>> as noted here...
>> https://bugzilla.redhat.com/show_bug.cgi?id=219715#c18
>
> Well, if you have reason to believe that grubby does something wrong,
> find out what it does wrong. Run it manually, it has a man page, too.
> And /boot/boot.b must exist when it is specified in lilo.conf. Do you
> say that grubby deletes that file by accident?
>
> And if you're really fed up with grubby, you could modify new-kernel-pkg
> to execute your own lilo-update script/program instead of grubby.
>
> --
> fedora-list mailing list
> fedora-list@redhat.com
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list