I'm afraid that this is due to a local misconfiguration. Specifically,
this problem occurs when the grub-pc package has not been configured to
install GRUB to the location where it's actually being booted from, so
it thinks it's successfully upgraded but you actually end up booting
from an old version of the GRUB core image, which is now incompatible
with the modules in /boot/grub/. I wrote up a summary of similar
problems on my blog a while back
(http://www.chiark.greenend.org.uk/ucgi/~cjwatson/blosxom/debian/2010-06-21-grub2
-boot-problems.html); my comments about work being done to improve
matters are now dated but the basic summary is still accurate.
Unfortunately, the PC architecture is such that we can't detect this
misconfiguration automatically; I think I've now done all I can do along
those lines without annoying people with questions on every single
update.
The problem should be visible in the output of this command:
sudo debconf-show grub-pc | grep install_devices
To fix your configuration, run 'sudo dpkg-reconfigure grub-pc'. Just
press Enter at all the questions apart from "GRUB install devices:". At
the "GRUB install devices:" prompt, it is normally correct to select the
boot record(s) on all your hard disk(s). People with specialised boot
loader requirements may need to do something slightly different.
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Invalid
** Changed in: update-manager
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/836378
Title:
Oneiric upgrade, boot hangs at error: symbol not found:
grub_divmod64_full
To manage notifications about this bug go to:
https://bugs.launchpad.net/update-manager/+bug/836378/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
