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

[joekamprad]

@jonathon

There’s no clear pattern in this thread about what systems are affected or why, and that would be something very useful to collate.

from what i see it’s not affecting legacy Bios systems only UEFI…
And indeed as EndeavourOS enables os-prober usage most users will have os-prober in use?

[jonathon]

@joekamprad

EndeavourOS enables os-prober

Ah, so that will likely be the cause, then. Interesting default…

[dalto]

@NX-01

It’s not clear if it’s broken? Could it just be a coincident that multiple ppl here can’t boot after the update?

That doesn’t mean it is broken. The situation here is that the latest update requires running grub-install after updating. The question that nobody has clearly been able to answer yet is “Were we supposed to be doing that?” or is it a bug.

@NX-01

And do you really think that the devs (I hope it’s not just one guy) didn’t get any reports yet?

Well, there is a clear mechanism for reporting such bugs and when I last checked, nobody had done so.

@anon11595408

Anyone filing it from here!?

Before filing a bug, someone would need to recreate it on Arch. You can’t report Arch bugs from EOS.

[BONK]

I wish i could recreate it on arch. None of my systems be it arch or archlabs have this issue. The only difference is I do not use os-prober Why doesn’t someone just do an offline endeavour install and remove os-prober and then update and see what happens.

[sradjoker]

On it

[Mihir]

I ran the following
sudo mount /dev/nvme0n1p6 /mnt
sudo mount /dev/nvme0n1p4 /mnt/boot
sudo arch-chroot /mnt
downgrade grub and selected grub2:2.06.r297.g0c6c1aff2-1
and yeah Now when I notice carefully there is an error… says

Generating grub configuration file …
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
ERROR: mkdir /var/lock/dmraid
Adding boot menu entry for UEFI Firmware Settings …
done
(3/4) Checking which packages need to be rebuilt
(4/4) Updating the info directory file…

Please help.

[Scotty_Trees]

@NX-01

Well, that sounds pretty unprofessional for me.

Unprofessional? My dude, this is all run by volunteers for free on their own personal time. If you want something “professional” install Windows or Mac. You can’t realistically expect volunteer Arch devs who come from all types of various tech backgrounds to be on par with software companies that make billions.

[anon49550872]

What I noticed so far:

• Only happening to EFI, legacy Bios systems are not affected.
• It happens to all partitions types, such as btrfs ext4 and etc.
• os-prober: based on what I read on this thread, this is not the problem, I don’t use and got into this.
• grub-btrfs: based on what I read on this thread, this is not the problem since its also happening to ext4 installs.
• dual boot could be a factor, we could check if this is common between the people that were affected by this.

Did I forget something?

[dalto]

@BONK

Why doesn’t someone just do an offline endeavour install and remove os-prober and then update and see what happens.

Speaking only for myself. Because I am still at work.

[jonathon]

@Scotty_Trees

You can’t realistically expect volunteer Arch devs who come from all types of various tech backgrounds to be on par with software companies that make billions.

On the contrary, Arch has had fewer broken updates than Windows has.

@anon49550872

os-prober: based on what I read on this thread, this is not the problem, I don’t use and got into this.

OK, so this throws a spanner into the works…

[NX-01]

Sorry, but I don’t get all of this. Grub is pretty common, it’s not something that just 90 ppl on earth use. So I guess the devs have access to more than just 2 or 3 systems to test this.

Anyway, (and this is for @dalto also) if it is indeed not clear if the update causes problems, then pls ask whoever is in charge here to change the statement on the startpage of the forums, cause this clearly states that the update is the problem:

" Grub Update Causing Unbootable OS On UEFI Systems
A grub update today is causing boot issues on UEFI systems. "

It doesn’t say “maybe” or “propably” or “could”, it clearly says “is”!

[ricklinux]

I am using btrfs and i have triple boot with rEFInd and I’m using grub on each install but i have os-prober disabled on each. My rEFInd is installed on Xfce/i3 and i also have sway and Kde installed. So i updated on Kde and it didn’t boot. The solution for me was to arch-chroot and downgrade grub on kde. I haven’t updated the others yet. It was simple enough other than I’m not real experienced with btrfs so i had to think and follow some things but not difficult.

[dalto]

@NX-01

It doesn’t say “maybe” or “propably” or “could”, it clearly says “is”!

It is causing problems, but that doesn’t mean those problems are caused by a bug.

[Stagger_Lee]

@jonathon - just curious, are you getting reports of this from Garuda users?

[George5610]

I only have Endeavour OS install, no dual booting and this bug affected me

[jonathon]

One so far, which is why I’m very interested to know why EnOS is seeing such a large number of cases.

[amarkuni]

@anon49550872

dual boot could be a factor, we could check if this is common between the people that were affected by this.

I am affected, but I don’t have a dual-boot system. ‘os-prober’ is installed on my system, but I don’t think I use it:

grub config:
GRUB_DISABLE_OS_PROBER=true

[Mihir]

Please help here !

[anon11595408]

@amarkuni

I am affected, but I don’t have a dual-boot system. ‘os-prober’ is installed on my system, but I don’t think I use it:

grub config:
GRUB_DISABLE_OS_PROBER=true

Oha!

More pointing towards a BUG.

[Scotty_Trees]

Happening on Garuda Linux too:

Stuck in boot loop after update