F16: After update to grub2-1.99-1.fc16.x86_64 cannot boot

[Joachim Backes]

After having updated to grub2-1.99-1.fc16.x86_64, grub2 refuses to boot 
(file not found). Getting rid from this by re-installing the bootloader 
to /dev/sda.

Anybody has the same issue?

--

Joachim Backes

http://www.rhrk.uni-kl.de/~backes

[Jóhann B. Guðmundsson]

On 09/02/2011 08:45 AM, Joachim Backes wrote:
> After having updated to grub2-1.99-1.fc16.x86_64, grub2 refuses to 
> boot (file not found). Getting rid from this by re-installing the 
> bootloader to /dev/sda.
>
> Anybody has the same issue?

Confirmed file a bug and add it to the blocker bug list and comment if 
you have edited the config files or not.

JBG

[Joachim Backes]

On 09/02/2011 10:51 AM, "Jóhann B. Guðmundsson" wrote:
> On 09/02/2011 08:45 AM, Joachim Backes wrote:
> > After having updated to grub2-1.99-1.fc16.x86_64, grub2 refuses to
> > boot (file not found). Getting rid from this by re-installing the
> > bootloader to /dev/sda.
> >
> > Anybody has the same issue?
>
> Confirmed file a bug and add it to the blocker bug list and comment if
> you have edited the config files or not.

Done: BZ 735301

[Tom H]

On Fri, Sep 2, 2011 at 4:45 AM, Joachim Backes
 wrote:
> After having updated to grub2-1.99-1.fc16.x86_64, grub2 refuses to boot
> (file not found). Getting rid from this by re-installing the bootloader to
> /dev/sda.
>
> Anybody has the same issue?

Yes. Just happened to me.

"/boot/grub2/" is almost empty after the upgrade except for
"grub.cfg", "devicemap.lst.anacbak", and "locale/". "grub2-install
/dev/sda /dev/sdb" while booted from Anaconda's rescue mode
repopulated the directory.

There's a part of the preuninstall scriplet that deletes all ".mod",
".img" and ".lst" files from "/boot/grub2/" that might somehow be
responsible.

[Joachim Backes]

On 09/02/2011 11:01 AM, Tom H wrote:
> On Fri, Sep 2, 2011 at 4:45 AM, Joachim Backes
>   wrote:
> > After having updated to grub2-1.99-1.fc16.x86_64, grub2 refuses to boot
> > (file not found). Getting rid from this by re-installing the bootloader to
> > /dev/sda.
> >
> > Anybody has the same issue?
>
> Yes. Just happened to me.
>
> "/boot/grub2/" is almost empty after the upgrade except for
> "grub.cfg", "devicemap.lst.anacbak", and "locale/". "grub2-install
> /dev/sda /dev/sdb" while booted from Anaconda's rescue mode
> repopulated the directory.

Not me: after each kernel update I burn a boot cd, so I could boot from 
this cd to a fully operating F16 without usage of the rescue 
cd/anaconda. I can't say that /boot/grub2 was empty before running 
grub2-install.

Then running grub2-install rewrote the bootloader.
> There's a part of the preuninstall scriplet that deletes all ".mod",
> ".img" and ".lst" files from "/boot/grub2/" that might somehow be
> responsible.

[Peter G.]

Joachim Backes wrote:
> after each kernel update I burn a boot cd

Explain how you do this!

It wastes a lot of CDs, but saves a lot of 
wasted time trying to rescue a system.

[Peter G.]

Joachim Backes wrote:
> Anybody has the same issue?

Yes, please HELP! :-)

I am unable to boot my desktop computer. I 
just get a grub rescue command prompt and no 
grub commands except set seem to be 
recognized. I cannot boot into Fedora 15 or 
Fedora 16 alpha.

I am trying to fix by running the 
boot.fedora.iso CD, but I am not hopeful that 
this is the solution I want.

Any ideas how to get grub installed properly 
on a system that only had grub rescue prompt 
and will not boot into any installed fedoras?

[Peter G.]

Peter Gueckel wrote:
> Joachim Backes wrote:
> > Anybody has the same issue?
> Any ideas how to get grub installed properly...?

Many hours of work, my desktop computer is back. I don't care to do that 
agian (and don't ask me what I did, because I couldn't say, in any sensible 
order)!