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

[Jeremie Tamburini]

Bug is still there.

Quick example when my computer starts:
if I don't do anything, Ubuntu 19.10 will be booted.
If I press [F12] I get the Boot Menu list, which shows:
1. ubuntu
2. deepin
3. CD/DVD Drive ...
4. Drive0 HDD ...

There is only 1 entry for Ubuntu (which is the one for 19.10) but on my computer there are totally 4 different Ubuntu releases:
- Ubuntu 14.04
- Ubuntu 19.04
- Ubuntu 19.10
- Ubuntu 20.04

They should be all mentioned in the Boot Menu, but there is just one
entry.


If you install one of the Ubuntu versions, it will be automatically set as the only "ubuntu" Boot Menu entry. It will also be set as the default system on boot.
To change it you have to boot the Ubuntu version you want as the default one at boot, and run the command "sudo grub-install".


P.S.
I apologize for my old messages (#2 and #3) as they were not strictly connected to this bug, sorry!

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

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