grubaa64.efi Fails to Be Started Due to Multiple Startup Items
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.1k
- Forks
- 348
- PR merge metrics
- No merged PRs in 30d
Description
shim-15.4 During the boot from EFI/BOOT/BOOTAA64.EFI, if multiple os directories exist in the /EFI/ directory and each directory contains BOOTAA64.CSV, only one directory does not contain gubaa64.efi. The following error message is displayed:
Failed to open \EFI\myOS\grubaa64.efi - Not Found
Failed to load image \EFI\myOS\grubaa64.efi - Not Found
start_image() returned Not Found
The fbaa64.efi file checks only the BOOTAA64.CSV file and does not check the gubaa64.efi file when loading the BootLoader.Whether some functions need to be added to check whether grubaa64.efi exists.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the EFI/BOOT/BOOTAA64.EFI path and the fbaa64.efi logic described in the report. Reproduce the case with multiple directories under /EFI/, each containing BOOTAA64.CSV, and inspect how the BootLoader is selected. Done means a missing grubaa64.efi is not selected and the boot process avoids the reported Not Found error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100