grub2 critical bug -- appears to be fixed

[pidsley]

critical bugs of grub2-common (1.99-27.1 -> 2.00-14) <unfixed>
#707653 - grub2-common: After Grub 2.00-14 upgrade, system failed to boot (rescue, old grub 1.99 still in mbr)

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707653

I'm just going to wait until tomorrow...

(edit) this appears to be fixed. I still have my main machine on old Grub, but many people have upgraded successfully, and most of my test machines are now using new Grub.

[machinebacon]

Thanks Pidsley!

The link you posted had a little typo:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707653

Definitely everyone should wait, this is a mean bug! Thanks again

[pidsley]

Thanks bacon. I fixed the typo.

[dkeg]

Thanks! yep logged on this morning to check something and did an upgrade. I saw that, actually came here to post it up. I skipped this upgrade as well.

thanks again!

[Verändert]

I upgraded today and everything worked liked a charm. I guess the crisis is over. We can all relax. And if you don't hear from me tomorrow i just forgot to restart...

[paolo]

I have update and rebooted ...
All is ok here :lol:

[ivanovnegro]

Sid is biting, give it the hot sauce!

[dkeg]

The bug does not appear to have been fixed. So for now ...

Code: Select all

sudo su
echo grub-common hold | dpkg --set-selections
echo grub2-common hold | dpkg --set-selections

[ivanovnegro]

^ I think I will do that tomorrow if still not fixed, far too many packages not

upgraded

at the moment. I need new

shiny

stuffz.

[gurtid]

The bug does not appear to have been fixed. So for now ...

Code: Select all

sudo su
echo grub-common hold | dpkg --set-selections
echo grub2-common hold | dpkg --set-selections

How do you undo that when the bug is finally squashed?

[dkeg]

Replace hold with install

[pidsley]

This bug is still not fixed, so I did an upgrade today after holding grub and grub2. Thanks dkeg. I ignored the LibreOffice apt bug and so far so good.

[ivanovnegro]

^

That

[bizcuit]

Was upgrading Trollinger when saw this debian bug report, held off long enough to investigate the bug report. Decided to do it anyway and @ least here, in Trollinger the upgrade went off w/o a hitch, OS boots fine and has survived the flood of new packages into the Unstable repo's without a hiccup. Though isn't exactly a conventional setup. Atm have easybcd + win7 on mbr, boots another gnu/nix install and then been booting Trollinger from that distro's grub menu.

For me Machine's bbq'ey nixy kickbuttness just keeps on impressing me ...

All that said ... Seems this same bug leveled a Debian Sid install on the ole trusty, crusty desktop ... arghhh ! After an upgrade OS unbootable ... Grub error 15, core.img not found. On the desktop using grub legacy on mbr ( via Slitaz 3.0), in turn boots 3 other gnu/nix installs ( two Sid installs, a perpetual Debian testing install) and XP. Atm left scratching my head, is the problem grub legacy to grub2 incompatibility ? Is it the critical bug from that grub2 version ? Dunno ... for now don't have time to dork with it. Chrooted and messed around with it a bit, so far no good ... Haven't rescued that borked Sid install.

Many solutions have come to mind ... Including switching bootloaders ( like everything else, there's no shortage of bootloaders in gnu/nix.) Considered purging grub2 and install grub legacy or one of the others floating around. Could turn out interesting but so far considering it too time intensive. Also considering just converting those two Sid installs to bbq OS's instead. Been meaning to try more of Machines kickbutt nix creations anyway.

Long babbling way of saying, for me Trollinger keeps right on chugging along after upgrading grub2-common. While found out the hard way, apparently there is something to the critical bug report ... arghhhh ! Well and to add another thanks to MB for hiz time + effort in putting out this kickbutt addition in the nixsphere.

Viva La Linuxbbq and MachineBacon !!! ;)

[ivanovnegro]

Ah, Bizzy was too busy with upgrading. Critical means critical, rule of thumb, don't, just don't upgrade if you are not sure or put that s***er on hold. :D

But I think Trollinger already uses Grub2 because Siduction uses it?

^ No idea why I have this in mind. Cannot find it now.

[Verändert]

Ha ! No risc, no fun ;-)

[machinebacon]

Correctomundo for the GRUB2 being fixed via siduction. If somebody using BBQ runs into troubles, simply purge grub-pc and grub-common as well as grub2 and grub2-common and install them again.

Thanks for the vaseline, seabiscuit :)

[bizcuit]

^ Are certainly welcome for the vase Mr Machine ;) and thanks again for setting up the nix bbq ...

Yeppers ... mostly did out of curiousity Sir Ivan. Everything important on those desktop OS's is kept on a shared partition(s) leaving me with nothing to lose really. Didn't want to conclude that bug report was bs w/o trying it on more than one pc. Trollinger didn't miss a beat, that Debian Sid install crashed n burned ... sighs. :D

Went ahead and followed Dkeg's sound advice/instructions and put grub-common and grub2-common on hold .... Worked like a charm and that 2nd Sid install is still working as expected. All's well ... that ends well/etc. Looks like one of the desktop OS's will soon be joining the nix bbq. :P

Vll! :)

[pidsley]

grub2 is still broken. I upgraded two of my machines just to see what would happen. The BBQ machine is working fine, but the machine where I did a sid netinstall had some serious problems (grub works, but it throws a bunch of annoying errors). So I switched that machine to extlinux. It's working well so far.

[ivanovnegro]

I would say this problem is fixed with version 2.00-17. Feel free to mark it as such Pidsley.

Most of us already have the newest grub due to Siduction or at one point already upgraded like me. It seems the information was not very useful in the BTS. Though, it could be that some issues still exist around grub when you look at the BTS, especially on an individual configuration level. If it is the case for you, post back or open a new thread.