Peter Ruskin <firstname.lastname@example.org> wrote:
> On Wednesday 07 May 2008, »Q« wrote:
> > Earlier today, I emerged grub-0.97-r5 on my x86 laptop, replacing
> > 0.97-r4. I didn't run grub and didn't expect anything to be done
> > to my boot partition. Now I've read
> > <http://bugs.gentoo.org/show_bug.cgi?id=218599>, and I suspect my
> > current problem has to do with that, though I don't recall
> > anything in grub.conf that would lead to trouble.
> > I can't access the boot partition right now, and I'm posting this
> > in hopes of pointers for what to look at once I get the chance to
> > boot from a livecd.
> > When I try to boot, the word GRUB gets written to the screen over
> > and over and over, filling the screen. Pressing keys, AFAICT so
> > far, doesn't stop this. The screen is just filled with "GRUB",
> > and I think it's an ongoing thing because of a little flicker at
> > the bottom right.
> When you emerged grub-0.97-r5, this was displayed on your console:
> WARN: postinst
> *** IMPORTANT NOTE: you must run grub and install
> the new version's stage1 to your MBR. Until you do,
> stage1 and stage2 will still be the old version, but
> later stages will be the new version, which could
> cause problems such as an unbootable system.
Thanks. I had assumed (d'oh!) that I could wait and read the elog if I
ever decided to install the new grub to my boot partition. I'm not so
happy with the boot partition being mounted and screwed with by the
ebuild, especially given I was using a grub from Fedora, not Gentoo.
Now I've got DONT_MOUNT_BOOT="yes" in make.conf, so I should never have
this kind of problem again.
Once I booted a livecd, running the setup command within grub fixed
the problem. Then once I booted Gentoo, I did it again, to get
whatever goodness is in this latest revision.
> To make life easier for situations like this, you could install grub
> on a floppy.
Even if I had a floppy drive, I'm not sure portage wouldn't find the
floppy and overwrite it.
I usually have a livecd or two in my bag, but of course not when I most
email@example.com mailing list