[Bug 1521478] Re: Precise --> Trusty, grub partition install fails, so it gives up

[Phillip Susi]

I didn't ignore it: I said that on upgrade ( which is what you seem to
be talking about ) it uses the same location you originally chose when
you first installed, so apparently you chose the wrong location then (
and I assume you later used something like boot-repair or manual
installation of grub to get the system to boot, but your original choice
was not affected by that ).  Rather than, or after using one of these
steps, you need to run dpkg-reconfigure grub-pc to select the proper
installation location to be used on later upgrades.


** Changed in: grub2 (Ubuntu)
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1521478

Title:
  Precise --> Trusty, grub partition install fails, so it gives up

Status in grub2 package in Ubuntu:
  Invalid

Bug description:
  I have just updated my system from Precise to Trusty. During the
  process grub attempts to install itself in /dev/sda5 (the root
  partition). This fails and complains about blocklists being disabled
  (embedding not possible). Annoyingly the process continues and unless
  you're staring at the screen (which I was) then you're none the wiser.

  The result being an unusable system: grub drops into rescue and at
  that point everything is as clear as mud.

  The solution was to install grub in the MBR (/dev/sda) from a Trust
  live environment. The system is now usable. It took me several hours
  to work this out.

  There needs to be some sort of protection from this happening in the
  future. An ordinary user would have no hope whatsoever in working this
  out and an unusable system is the worst-case scenario to any end user
  (discounting complete data loss).

  Will I be faced with this dreadful problem against on upgrade to 16.04?
  Can't the grub upgrade process at least have the sense to try something else once it has failed?

  I had the sense to image the drive before starting the upgrade
  process, should it should be reproducible, albeit slowly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1521478/+subscriptions