-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems during U-boot stage: Unable to read file ubootefi.var, Failed to load EFI variables #37
Comments
Is there a problem? Those messages are expected because the boot option used is the last fallback. This could be avoided but that would mean we need more modifications in u-boot distro_boot environment. |
My machine stuck in this stage. U-Boot 2022.07 (Jul 11 2022 - 17:18:25 +0000) |
ok. From u-boot everything looks ok. It loads and starts |
Sure, there is nothing on display after this. |
If the problem is the broken grub which was for a few days in the package repository following commands should let you start linux from u-boot. Once linux is booted an update will install a fixed grub package. When u-boot ask you to press a key to interrupt auto boot do so. Enter the following commands. (partition numbers are based output). commands and variables (
|
@jannau I'm in the same situation as the original poster. Thanks for your instructions, I can boot again now. But it seems I'm not in efi mode and as such grub won't let me run grub-install. I'm not sure if I remember it correctly, but I might not have been in efi mode to start with (that's how I ended up in this situation, grub-install failed, I ignored/didn't read properly and rebooted after the grub update. I'm not sure what I did to end up in this situation (and why not everyone else also ended up here). And I don't think I know how to get out of it either, so any tips are welcome :-) |
"update-grub" from asahi-scripts, properly upgrades grub. But this means that mindlessly copy/pasting the "grub-install ..." output from the most recent grub update from pacman is what put me in this situation. And might put others in that situation? In any case, I will remember that I need the update-grub script to, well, install grub. So I'm good. |
does |
The grub pacman package just tells you to run:
The dots are just ignored by grub? But really that's just plain guessing on my part. The update-grub script then sets the removable flag, enough for me to get out of this. But any grub-install call without the removable flag would probably end up with the same failure? And if you then ignore the output "won't work with efivars" error, I think that was enough to put me into that situation. Why it's not hitting everyone, I don't know. But I think all I did was pacman update, grub-install (failing), and reboot. |
grub-install fails for me with |
I have run into this issue and managed to boot with the given instructions but once there and I run the grub-update scripts, the issue is not fixed. The update script runs with no errors however, when I reboot, I get the same grub error. The only difference for me is my boot partition is on /dev/nvme0n1p6. Is there something else I am missing? Any help would be much appreciated. |
Device: 2020 Macbook Pro M1, MacOS13, I've got the following errors:
Failed to load '/'
** Unable to read file ubootefi.var **
Failed to load EFI variables
BootOrder not defined
EF1 boot manager: Cannot load any image
Found EFI removable media binary EFI/boot/bootaa64.efi
192512 bytes read in 0 ms
Booting ref i\boot bootaa64.efi
The text was updated successfully, but these errors were encountered: