LinuxBBQ

A dist-upgrade today report me this one:
It scared the hell out of me (due to my lack of knowledge about LVM2) so I stopped the dist-upgrade.

I would say it affects only LVM installations but I could be wrong. Though there seems to be also a good workaround with:

Updating /etc/default/grub helped for me:

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
GRUB_DISABLE_LINUX_UUID="true"

(and re-running update-grub2)

Edit: There was a similar bug in the past and it was indeed an LVM issue.

Thanks for the clarification, ivan. Just dist-upgraded, rebooted and here I am. Everything's fine, without the need for that fix. Though it changed my grub background image, but I can fix that.

Great.
Yeah, the fix is only if it breaks.

Mark it fixed please. ;)

Ran a DU on a 64 bit system and grub borked. Gives the error shown in the title, looks like that's just a line somewhere in grub that should say something like color_highlight=black/white, but where it goes or how to edit from the grub rescue > prompt hasn't shown in any search I've done. I can chroot into sda2 from a rescue cd.

there was an upgrade warning posted here a few days ago, related to lvm2 and grub.

from another system, rebuild the grub. if you have a bbq rescue stick, try with 'sudo grubrepair'

I'm getting an error saying "Please enter device you want to install grub to (MBR). GTK-Message: Failed to load module "canberra-gtk-module"

I'm using an Ubuntu 12.10 DVD because, well, it was what I had. For some reason every BBQ 64 bit cd I have refused to open, even though I've installed from all of them before. Poo happens.

EDIT: Looks like maybe something screwed up with Ubuntu, the stuff I'm seeing about this bug is from Ubuntu, circa 2011. I also have a Fedora 64 bit DVD, may try it with that.

OK, just tried on Fedora, same error, gives me a blank "page" instead of the sda 'list' of partitions that came up in Ubuntu. I also tried grubrepair /dev/sda2 and that didn't work. Stoopid computers.

Guess it might help to show the output:
Installed libcanberra-gtk3-module, still didn't work. Just figured that could be because I haven't loaded the modual, but modprobe doesn't work because I don't have permission in chroot, evidently.

unsure abt. these, its just a bash script (not gtk),anyway this won't work outside bbq. try
sudo grub-install /dev/sda2 (or your device) and then sudo update-grub.

Do yourself a favour and create another bbq cd or usb. I fixed this issue in about 1 minute running the bbq tools from a live bakewell usb when I got your intial problem a few days ago.

I will reopen this bug and merge the newest grub errors with it. My fault for suggesting closing it down so quickly.

It seems on some machines the newest grub in sid will fuck up your system. We think it relates only to LVM but we could be wrong.

So, do not upgrade if you are not sure and wait the patch that will come to fix the problem or put grub2-common and grub-pc on hold!

I would also suggest to put the crap on hold, though interestingly on my no-other-OS-just-Linux computers the new GRUB works well, but I don't use LVM and recently also no systemd (if this maybe plays a role). Thanks Ivan for the reopening and merging, would have been too sweet if this shit solves itself easily.

Just in case you see the patch coming from Siduction to solve the Grub issue, maybe you still want to wait rather than do a d-u.

Tim speaks:

http://forum.siduction.org/index.php?to ... 8#msg36448

IMO, stay on hold.

Edit: Of course, by now it is not only grub2-common, it is the whole Grub crap but I think you know that already. When you hold grub2-common and grub-pc it should automatically prevent other Grub packages from upgrading.

Stay safe. ;)

I got caught by this, but there is an easy work-around:
While on the grub menu, use the grub 'E' (editor) feature to replace by replacing VG10-sid with your logical volume name.
Press F10 to boot.

After booting edit /boot/grub/grub.cfg
and apply the same modification.

Of course you will have to do that every time after running update-grub, until the issue gets solved.

Something caught my eye on a followup to bug #741342 (post #31)regarding the usbhid module not being found (which sounds like it could cause the scenario in #741464).

(741342)
https://bugs.debian.org/cgi-bin/bugrepo ... =741342#31

(741464)
https://bugs.debian.org/cgi-bin/bugrepo ... bug=741464

(edit - probably would have been good to include the actual links in the post. :p)

This problem still persists, especially because of grub-pc-bin. I still recommend to stay on the older Grub packages if you are not able to fix it by yourself.

Reference

Closing this.