[Bug 1056101] Re: grub-efi overwrites an existing grub*.efi file

[Jeremie Tamburini]

Discovered the same problem on Ubuntu 14.04 and 14.10.

One of the worst thing is that a step of the installation (GRUB position
in the "mount point" settings) is just broken and doesn't work properly
with multi-boot systems. The last installed *buntu will be always set as
the default system, even if you DON'T select /dev/sda for GRUB.

After every installation I have to use BootRepair to set the system that
I wanted as the default one. Other wise I can leave everything as it is,
with a secondary system set as default, but at every kernel update
there's the need to run the secondary system to run the "update-grub"
command...

As this bug seems to be quite old, I'm afraid that probably there isn't an easy solution.
Is there at least a easier/faster workaround?

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

Title:
  grub-efi overwrites an existing grub*.efi file

Status in “grub2” package in Ubuntu:
  Triaged

Bug description:
  On Ubuntu 12.04 (grub 1.99), grub-efi creates a
  /efi/ubuntu/grubx64.efi file, which is recognized as an entry in the
  UEFI firmware.

  When you install two Ubuntu (let's say UbuntuA, then UbuntuB) in
  dualboot, UbuntuB will overwrite the /efi/ubuntu/grubx64.efi file
  (linked to UbuntuA) by a new /efi/ubuntu/grubx64.efi file (linked to
  UbuntuB).

  THE PROBLEM IS:
  if UbuntuB's /boot/grub/grub.cfg is damaged or erased, the user can't access neither UbuntuA nor UbuntuB.

  EXPECTED BEHAVIOR:
  UbuntuA creates its own entry (eg /efi/ubuntu/grubx64_uuidA.efi ), and UbuntuB creates another entry (eg /efi/ubuntu/grubx64_uuidB.efi ), so that if UbuntuB's /boot/grub/grub.cfg is damaged, the user can still access UbuntuA via the UEFI firmware.

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