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

[Jeremie Tamburini]

@mkukri
A couple of years ago I had 2 installations of EndeavourOS on two different partition, and the Efi menu showed 2 different entries. I can't remember exactly but the menu entries looked like these:
- EndeavourOS 12345...
- EndeavourOS 14789...

I don't know if the boot process is meant to work as it works in Ubuntu or as it works in EndeavourOS. At least it looks it is possible to have two different Efi menu entries for 2 different installation of the same system... and it's good.
If for any reason my default system is broken and I can't access the other grub menu entries, I can still select a working system from the Efi menu. I recently had a situation like that.

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

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