Setting an alternative UEFI Folder name when installing GRUB causes it to be stuck in 'Minimal Bash-like Editing' mode
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub2 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Info:
Ubuntu Release: Ubuntu 18.04
grub-efi-amd64-bin: 2.02-2ubuntu8.13
I originally reported this to Calamares, because of the fact it affected Feren OS and Feren OS was the original place I found this issue happen, but whenever a custom ID for GRUB is set that isn't 'ubuntu' it will result in GRUB being always in Minimal Bash-like Editing is Supported mode.
Reproduction Steps:
1. Delete everything in /boot/efi/EFI including folders to make a clean slate (excluding Windows EFI Directories if they're there, they won't change anything)
2. Do `grub-install /dev/sda --uefi-secure-boot --bootloader-
3. Restart the system
What was expected:
GRUB would boot normally even with a different EFI folder ID
What actually happened:
GRUB booted into Minimal Bash-like Editing is Supported unless the ID is explicitly set to 'ubuntu'.
Additional Notes:
I also proceeded to do extra tests before reporting this issue in Terminal on the affected machine:
'grub-install /dev/sda --uefi-secure-boot --bootloader-
'grub-install /dev/sda --uefi-secure-boot --bootloader-
'grub-install /dev/sda --uefi-secure-boot --bootloader-
summary: |
- Setting an alternative UEFI ID causes GRUB to be in 'Minimal Bash-like - Editing' mode + Setting an alternative UEFI Folder name when installing GRUB causes it + to be stuck in 'Minimal Bash-like Editing' mode |