After running into this on my testing VMs (FYI: for those using the testing repos (GRUB)), I upgraded my system tonight and my GRUB was hosed. I tried running sudo downgrade, but my pacman cache only had the latest release.
Surprisingly, there have been no other posts about this, so I’m not sure what’s going on. Arch’s bug reporting system is not user-friendly, to say the least.
Most EOS users don’t have hooks that call grub-install or grub-mkconfig so depending on the nature of the issue, it may take longer for them to see it.
However, other distros based on Arch should be seeing it if it is something that impacts most installs.
I updated and had no issue. The updated version of grub came in the updates. I ran sudo grub-install and then ran the grub update command sudo grub-mkconfig -o /boot/grub/grub.cfg Then i rebooted and went into the Bios settings and selected the correct entry to boot on as it does change.
[ricklinux@rick-ms7c37 ~]$ pacman -Qi grub
Name : grub
Version : 2:2.12.r212.g4dc616657-2
This is one thing about Arch-based distros that I find… fascinating, to say the least. I can’t think of one other major distro that doesn’t run grub-install and grub-mkconfig after the GRUB packages are upgraded.
On that note, I did have more instances of GRUB corruption before EOS.
I happen to just do a full system update about 5 minutes ago which included this GRUB package (2:2.12.r212.g4dc616657-2). I haven’t had any issues after updating to it and restarting the system. However, I am using base Arch if that matters for anything.
Because the name changed. It was endeavour before or endeavouros? I can’t remember without booting into the firmware and checking but after it was named grub.
Edit: This is the boot priority that I’m referring to.
OK, that makes sense. Btw, my pacman hooks run the commands listed in this EOS forum post from 2023: Attention grub update - #11 by dalto. Been working without a hitch, until today.
I checked…yes it was endeavouros before and then it changed to grub. You’ll sometimes see entries UEFI OS which i also have. But it won’t boot on those entries anymore.
Are these to hooks stored in /etc/pacman.d/hooks/ ?
I haven’t specifically set anything up for that, and entry in pacman.conf has the hookdir option commented out. GRUB is not by strong point currently as I am still reading up about that so I’m unsure if I found the correct place for where hooks are stored or set. (Or by strong point I mean how pacman sends the updates to it)
Yes you could be right but it doesn’t mention having to do this on the Arch wiki. It is an option and maybe it’s a better way? I don’t have an issue with it changeling the boot priority name. I 've dealt with it enough so I’m used to it.
Okay, no problem. I remember seeing this setting in pacman.conf and not setting it while changing other settings during OS setup so I didn’t know is this was only if I wanted to add my own and there were default ones added by system. At least I know now.
I have (2) hooks, which I mention in the aforementioned testing thread (in the OP).
I see now, I was on that thread before and there has been new replies since. Never mind me then in that case (Again, ).
@ajgringo619
I updated my other nvidia desktop and installed grub but this time i used sudo grub-install --no-nvram and then i ran the grub update command sudo grub-mkconfig -o /boot/grub/grub.cfg and it didn’t change the boot priority name.
Just wanted to let you know that downgrade lets you download older packages from the arch archives. It doesn’t necessarily need to be in your package cache. You then proceeded to do this step manually.
Thanks. I did this on my (2) Arch VMs that blew up, but for some reason on EOS, the sudo downgrade grub command did not list any older packages, local or remote versions. That had never happened to me before; maybe I didn’t setup the chroot correctly.
).