CRITICAL: 13.10->14.04 upgrade BREAKS GRUP, renders computer UNBOOTABLE
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-release-upgrader (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Great!
I decided to finally upgrade from 13.10 to 14.04, and after the whole upgrade process and the restart, the computer won't boot!!
I get a black screen with this error instead of the familiar boot menu:
error: symbol `grub_term_
grub rescue> _
Not only can't I boot ubuntu, I can't boot any other OS I had installed on the computer (namely Windows 8).
I am reporting this from another computer.
How do I fix it now?
Do you test distribution upgrades before releasing them? Well, obviously not enough. And _after_ releasing them, because it's been a f***ing month or two since it was released.
At EVERY SINGLE UPGRADE I always get some huge problem that renders my system completely unusable and needs some pretty radical fix. But this is the most f***ed up and low level one ever. At the next upgrade I guess I'll get hardware damage.
During the upgrade there was some crash: the "system problem detected" (or whatever it is called) window popped up, informing of some crash related to VirtualBox (and uslessly offering me the option to report it, just to later tell me it couldn't be reported, as usual with third-party packages). I don't know if that is related and I know that's a third party package, however distribution-
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: ubuntu-
ProcVersionSign
Uname: Linux 3.8.0-31-generic i686
NonfreeKernelMo
ApportVersion: 2.9.2-0ubuntu8.4
Architecture: i386
CrashDB: ubuntu
Date: Sat May 24 19:48:05 2014
InstallationDate: Installed on 2010-06-23 (1431 days ago)
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MarkForUpload: True
PackageArchitec
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-
Symptom: dist-upgrade
UpgradeStatus: Upgraded to raring on 2013-08-10 (287 days ago)
VarLogDistupgra
Changing to confirmed because one single case is enough. No point in waiting for some other user to have its system destroyed.