After LTS->LTS (lucid2precise) upgrade, upon reboot drops into grub recovery shell
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub2 (Ubuntu) |
Fix Released
|
Critical
|
Dimitri John Ledkov | ||
Precise |
Fix Released
|
Critical
|
Dimitri John Ledkov | ||
Quantal |
Fix Released
|
Critical
|
Dimitri John Ledkov |
Bug Description
[Impact]
Any system upgraded from Lucid->Precise is affected, if and only if the user does not opt-in to reinstall grub-pc bootloader during the do-release-
The affected system will fail to reboot, and will drop into grub shell requiring manual boot.
[Workaround]
Users should follow the warnings about potential incompatibilities, and reinstall grub-pc into MBR/partitions as appropriate. This will update their grub to a supported version. If users still preffers to keep old grub, we provide Development and Stable Fixes.
[Development Fix]
In the Development branch, the fix was to use backwards compatible syntax in grub.cfg. Specifically, using ${var} syntax for variable substitution. (NB! the $var syntax was introduced as fully supported after the grub2 1.98 release, that is after lucid)
[Stable Fix]
Patch can be found at: https:/
[Test Case]
1) Install/Have already installed: grub-common grub-pc grub-pc-bin grub2-common from lucid (1.98-1ubuntu5)
2) Make sure version of 1.98-1ubuntu5 of grub2 is used as bootloader, e.g. run `sudo grub-install /dev/sdX # Example: sudo grub-install /dev/sda'
Note: step 1 & 2 can be accomplished by doing a fresh lucid install in environment which uses grub-pc, e.g. desktop or server images, but not ec2 "cloud" images.
3) Upgrade grub-common grub-pc grub-pc-bin grub2-common from precise-proposed (1.99-21ubuntu3.1) but do not reinstall grub into MBR. (as part of do-release-
4) Reboot
Assert True: reboot succeeds.
To test that bug exists: install grub-common grub-pc grub-pc-bin grub2-common from precise (1.99-21ubuntu3) but dot reinstall grub into MBR. Rebooting should drop into grub recovery console.
[Regression Potential]
Regressions are not anticipated, since only variant of valid syntax is changed. Nonetheless users should see https:/
Related branches
- Ubuntu Core Development Team: Pending requested
- Diff: 0 lines
- Ubuntu Core Development Team: Pending requested
-
Diff: 50 lines (+10/-4)3 files modifieddebian/changelog (+6/-0)
debian/patches/ubuntu_gfxpayload_filter.patch (+2/-2)
debian/patches/ubuntu_vt_handoff.patch (+2/-2)
affects: | ubuntu → grub2 (Ubuntu) |
Changed in grub2 (Ubuntu): | |
importance: | Undecided → Critical |
Changed in grub2 (Ubuntu): | |
milestone: | none → ubuntu-12.04 |
Changed in grub2 (Ubuntu): | |
status: | Confirmed → Incomplete |
tags: | added: rls-mgr-p-tracking |
Changed in grub2 (Ubuntu): | |
milestone: | ubuntu-12.04 → precise-updates |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/978464/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]