Grub 2:2.06.r322.gd9b4638c5-1 won't boot and goes straight to the BIOS after update

Never mind.

I just did a fresh online installation on this computer (which automatically updated it) and the computer works. Fortunately Documents, etc., were backed up onto hard drives.


1 Like

Regenate grub or reinstall

Grub-mkconfig -o /boot/grub/grub.cfg

Can do

Is the buggy update still available or is it safe to update now?

You can track the package here if you like:

Quick answer, no the grub package has not yet been updated/fixed upstream, hence the need for pinned posts here to help users.

So to summarize:

  1. Update - don’t reboot!

  2. Re-install grub:

sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=EndeavourOS
  1. Update grub:
sudo grub-mkconfig -o /boot/grub/grub.cfg
  1. Oh yeh, reboot :smiley: :smiley:

Correct :+1:

It’s also explained here too in a recent pinned post:

1 Like

@adjagu @dalto Thanks for that posting, much appreciated!

sudo arch-chroot /mnt

I see what i was doing wrong, that command helped. :crazy_face: :flushed: :grimacing: :rofl:

:smiley: was to busy reading this (I was not affected either).

Well, in the past I NEVER manually installed the updated grub. Running grub-mkconfig alone lead to the new grub version being used at the next boot, so I saw no reason to reinstall grub with every update.
And: grub-mkconfig is run automatically with a hook.

1 Like

I don’t expect a fix that fast, but why the hell hasn’t the update been withdrawn? It’s 10 hours since the first reports came in here.

oh yes… it is always your own fault and indeed if it is caused by os-prober usage… its disabled per default on arch so not an issue with the defaults only if you change it…

I will try reproduce os-prober as the reason of the issue…


That didn’t work for me.
I came to a grub rescue instead.

I think I’ll ignore it until package is fixed

EDIT: I do use grub-btrfs added as well so might be why

could be there will be no fix for this…

I tried this but I got

liveuser@eos-2022.06.23 ~]$ sudo grub-mkconfig -o /boot/grub/grub.cfg
/usr/bin/grub-probe: error: failed to get canonical path of `airootfs'.
[liveuser@eos-2022.06.23 ~]$ 


liveuser@eos-2022.06.23 ~]$ sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=EndeavourOS-grub
Installing for x86_64-efi platform.
grub-install: error: failed to get canonical path of `/boot/efi'.
[liveuser@eos-2022.06.23 ~]$ 

I managed to fix this issue by downgrading the grub like everyone else however it still wasn’t booting as the nvidia-uvm kernel module was failing to load.

I fixed this issue by ctrl+alt+f2 to get to tty2 and doing “pacman -Sy nvidia” and then rebooting

Hope this helps other people that are stuck even after downgrading grub.

Apologies for formatting I’m on my phone

1 Like

Arch and it’s many derivatives are very very popular, so there are A LOT of users with various hardware setups that will find bugs the devs did not simply because their hardware is different. Thankfully though, because there is a very healthy amount of Arch users in the wild, a fix or a workaround for critical bugs like this grub issue is almost guaranteed within the first 24-48 hours of an issue that affects most users.

There’s always a plethora of reasons why an Arch dev/maintainer hasn’t fixed it yet (work, family, time zone difference, vacation, sick, etc), but whoever maintains the grub package might be busy right now. I’d expect a fix deployed within the next day or two since this news has already broke out within the Arch communities.


grub-install --version

For Arch to check the grub version?

I can hope someone release a fix that works for me then :slight_smile:
Sadly I’ve tried to update according to the instructions but no dice :frowning:


To check what module has failed to load you can do “systemctl status systemd-modules-load”
And this should show that nvidia-uvm has failed if you have the same problem that I encountered