[Bug 751057] Re: grub-pc upgrade on Amazon EC2: The GRUB boot loader was previously installed to a disk that is no longer present, or whose unique identifier has changed for some reason.

[David Morgan]

I've just hit this too: in my case updating an 18.04 instance on AWS. It
was not an issue when I last updated/rebooted about a month ago. In my
case it prompted me to install onto a disk and a partition during the
update, via a lurid full screen display. Not knowing quite what to do I
selected *both*, thinking more is safer. I haven't attempted a reboot
yet though, so I will now try to reconfigure that to neither. I'm not
sure whether this would have actually prevented the instance from
booting.

-- 
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/751057

Title:
  grub-pc upgrade on Amazon EC2: The GRUB boot loader was previously
  installed to a disk that is no longer present, or whose unique
  identifier has changed for some reason.

Status in Ubuntu on EC2:
  Invalid
Status in grub2 package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: grub2

  I'm running Natty 11.04 beta in Amazon EC2. ami-5c39c435, ebs/ubuntu-
  images-milestone/ubuntu-natty-11.04-beta1-amd64-server-20110329. The
  objective is to do an apt-get upgrade smoothly, but the upgrade of the
  grub-pc package is causing problems.

  The present version is grub-pc_1.99~rc1-6ubuntu1_amd64. apt attempts
  to install grub-pc_1.99~rc1-8ubuntu1_amd64 and the corresponding
  version of grub-common.

  1.  apt-get update
  2.  apt-get install grub-pc grub-common
  3.  Choose to replace /etc/default/grub (I've looked at it, seems to have no changes on point.)
  4.  Error: "The GRUB boot loader was previously installed to a disk that is no longer present, or whose unique identifier has changed for some reason."
  5.  Regardless of the choices selected from here, the configuration utility seems to get stuck in a loop.

  I don't know if this has anything to do with the fact that Amazon EC2
  partitions are xen, which are in /dev/xvda1 instead of /dev/sda1.

  I understand that grub-legacy-ec2 is installed, which may handle
  bootloading.

  Whatever the cause, apt-get upgrade, which may include new versions of
  the installed grub-pc, should work smoothly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-on-ec2/+bug/751057/+subscriptions