Default EFI bootloader isn't installed leaving system unbootable

Bug #2045498 reported by Shantur Rathore
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
curtin
New
Undecided
Unassigned

Bug Description

Hi,

I am using Curtin via MAAS to setup ARM based systems running u-boot firmware.
Current state of u-boot doesn't support EFI variables and hence needs grub update_nvram: false setting.

There is not EFI Boot entry created for the newly installed OS and there is no default bootloader EFI/BOOT/BootXXXX.efi so there is way for firmware to know which bootloader to load.

grub-install also has --removable option which forces grub to also install default bootloader in EFI/BOOT/BootXXXX.efi but curtin doesn't use this.
This bootloader is also needed when NVRAM is cleared and system needs to boot. Some systems don't have support to select EFI files to boot and they are rendered unbootable.

As a fix, curtin could

1. Always setup a default bootloader by adding --removable flag here https://github.com/canonical/curtin/blob/master/curtin/commands/install_grub.py#L340

2. Setup a default bootloader when update_nvram is false.

Thanks

Revision history for this message
Shantur Rathore (rathore4u) wrote :

Update

2. Setup a default bootloader when update_nvram is false by adding --removable flag

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.