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

[Jeremie Tamburini]

Today I was updating one of the system (Lubuntu) on one of my test partitions.
The system wasn't the default one at the boot, but as the grub packages have been updated, after the re-boot I have discovered that it was set as the boot default system...

This bug creates problems even with the updates.

At least I have found a quicker workaround here http://superuser.com/questions/376470/how-to-reinstall-grub2-efi
All you have to do is booting from the grub menu the *buntu system you would like as the default one and run this command: 

sudo apt-get install --reinstall grub-efi-amd64


This might sounds obvious, but every time I was searching informations related to grub/uefi I always found instructions for external instruments such as boot-repair.

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