[Bug 1450783] Re: grub-install with --bootloader-id option creates unusable boot configuration with secure boot

mr calvin 1450783 at bugs.launchpad.net
Thu Mar 28 21:58:50 UTC 2019


Another similar bug report 1247933

Im my case I have had big issues installing "new" hard disks or even USB
flash drives, which also have the equal hardcoded "ubuntu" bootloader-
id, and as you then have several disk with the same ID you have problems
booting. As a main rule you should be able to name your bootloader
something rather unique for each installation so future HDD mix want
cause boot problems. Calling them all the same is in my experience a bad
practice.

I really this could be fixed/up-prioritized.

I know time is limited resource for everybody, but having an option
"--bootloader-id" that actually doesn't work for how maaaaany years is
really critisable. At least remove the option from the documentation if
knowone plan to fix it in the near future. A lot a people might waste a
lot of time, I did for sure!

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

Title:
  grub-install with --bootloader-id option creates unusable boot
  configuration with secure boot

Status in grub2 package in Ubuntu:
  Triaged

Bug description:
  When manually creating an EFI boot entry using `grub-install
  --bootloader-id=<myid>`, where myid is a string different from
  "ubuntu", the resulting boot configuration is broken.

  The signed grub EFI binary `grubx64.efi` seems to contain a hardcoded
  path to `/EFI/ubuntu`, from which grub will then read the grub.cfg
  configuration file specifying the UUID of the root partition. This
  approach only works if the bootloader id is in fact equal to "ubuntu".

  Either calling grub-install with both an alternative bootloader id and
  UEFI secure boot options should fail and print an error explaining the
  situation, or the signed boot image should be fixed (i.e. the
  hardcoded path removed) so that it reads the grub.cfg from the same
  directory in which the image itself is located, which seems preferable
  because it allows multi-booting more than one Ubuntu installation on
  the same system.

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



More information about the foundations-bugs mailing list