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

General system
1

Hey everyone! After the latest grub update (1h ago), I restarted my laptop and it didn’t even go to the grub menu. Laptop shuts down and restarts going into BIOS screen.
I didn’t have issues with grub’s earlier update this week because I don’t have grub-customizer.
I chrooted through a live usb, downgraded grub and everything seems to work again.
Anyone having the same issue? also I don’t seem to find anything in the journal.

Moderation note:
go here to the tutorial on solving the issue:
https://forum.endeavouros.com/t/the-latest-grub-package-update-needs-some-manual-intervention

2

I’m experiencing the exact same issue. Resolution was same as you: downgrading grub. There’s a reddit post highlighting the issue as well:

3

Yeah, I get exactly the same here. Can’t believe this bug made it into stable.

5

Apparently, this is an upstream bug, seeing reports also on Reddit and Telegram.

6

Yeah just woke up and my grub was dead after update.

7

Some heads up for newbies like me if you don’t know what to do

https://discovery.endeavouros.com/system-rescue/repair-a-non-booting-grub/2021/03/

https://discovery.endeavouros.com/system-rescue/arch-chroot-for-efi-uefi-systems/2021/03/

8

This is second time in this week when grub update makes my system unbootable :tired_face:

I highly considering going to systemd now :rofl: :

9

Just checked and i can see that it only happen on uefi installs no problem on legacy Bios systems…
And i can boot up again after chrooting and regenerating grubcfg grub-mkconfig -o /boot/grub/grub.cfg
and reinstall grub files----> grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=EndeavourOS
So no downgrade is needed but chroot… can be really a bad moment if you do not have any live medium to boot…

Would be nice to get a solution for users with no way to chroot … i have no clue on that at the moment…

10

I am on systemd-boot for my personal installs :wink:

11

Yeah, even their official install script uses systemd for uefi installs last time I checked.

12

@bitterhalt grub=morefancyhalt :wink: but yes we already have the plan on removing grub for uefi or make it optional…

13

Just happened to me also on my kde. Good thing i have triple boot and i have grub separated on each. Now i have to figure out how can i fix it since it only boots directly into the UEFI screen if i select kde from rEFInd. :scream:

Edit: Of course I’m on btrfs also. :grimacing:

Edit2: Was able to arch-chroot on my btrfs setup with rEFInd and downgrade grub. Now I’m back in! I’m surprised i could figure out the btrfs to mount it properly. :smiling_face:

14

that did not solve it for me (UEFI, FAT32 efi-Partition for EndeavourOS only, ext4 root and home) - I had to downgrade grub to be able to boot again.

15

Same thing here, downgrading grub was only way to boot.

16

I just performed the update on a ThinkPad T450, which does use EFI boot and it rebooted fine.
I didn’t perform the update on my newer ThinkPad AMD Ryzen, though. I have enough technical hassles at the moment to overcome…

17

Can post a step by step list what to Do?

Thanks in advance.
Marvin

18

Hello EOS again after few months, I did update today and pc won’t boot , after that I did reinstall EOS, I got update and I did update, again broken :person_shrugging:.

19

I updated several installs and haven’t had any problem yet. Although…I don’t use grub so maybe that is related somehow… :thinking:

Well yeah, doing the same thing twice typically ends in the same result.

There was really no need to reinstall in that situation.

20

Chroot your system: https://discovery.endeavouros.com/system-rescue/arch-chroot-for-efi-uefi-systems/2021/03/

Then type: downgrade grub and choose version

If you want you can also skip grub updates temporarily by editing your /etc/pacman.conf
Screenshot_20220825_143000