I am running Ubuntu on a Lenovo G770 laptop. I left the original Lenovo Win 7 config on the HDD (it's the only Windows boot image I have left and I need it for contingency) -- albeit with a minimal pair of partitions and configured dual boot pretty much as per the Trusty guide though I did this back with 12.10. I have upgraded Ubuntu 8 times, 3 on this laptop, and this has been my only fail. I use a standard grub-pc install, and am a reasonably experienced sysadmin and developer.
@psusi, I won't bother enumerating all the false tries, and cascade failures. The underlying failure appears to be that the upgrade process *silently* failed to install the new 2.02-beta2-9 MBR loader on my HDD, and as you described above, the root failure was that the MBR and /boot grub2 components were out of sync. Given that part 0 starts at a block 2K block rather than block 39, there is no reason why this MBR bootstrap installation should have failed. So a simple sudo grub- install /dev/sda fixed this, and now both images are booting cleanly. Some general comments: * LTS releases are supposed to be *stable*. Why are we rolling out a "beta2-9" version of anything? Especially if anything goes wrong it will render the entire system unbootable; and the fix requires intimate sysadmin knowledge so is not really user-workable. * As others have said, any upgrade process which can leave a significant percentage of users system unusable is badly specified / implemented. This sort of bug is "Critical", IMO and not "High". At a minimum the upgrade process should carry out the necessary validation checks *before* starting the upgrade and abort with an informational error if there is going to be a failure. * The https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes#Known_issues page does not list this. It should. * The user comments in this bugrep include a lot of misleading chaff. A clearly defined diagnostic process and recovery process should be documented by the release team and referenced in the this known issues section. Blaming the users for this happening is a mistake. Mistakes happen both by users and in development. The main goal here should be to move forward in a positive manner, and to minimise the total impact. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1289977 Title: Ubuntu 14.04 Update breaks grub, resulting in "error: symbol 'grub_term_highlight_color' not found" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1289977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
