With I installed the update and updated config, os-prober ran and detected the other distro with no errors. But it dumped me to the grub rescue mode when I rebooted. By contrast, 2.12.3 boots just fine as soon as I downgrade back to it. So unless the 2.12.rxxx require hand-configuration somehow, I think they’re still buggy.
Feel free to report upstreams for them to fix it.
This is why I use systemd-boot or more recently limine (snapshot capable). Grub is just kinda icky anymore (imo) and I try to avoid it.
1 Like
I use grub because I have no issues with it. It works for btrfs snapshots on boot. Installing grub with sudo grub-install and running sudo grub-mkconfig -o /boot/grub/grub.cfg causes me no issues.
1 Like
Grub problems are minor problems only if you are prepared for them.
Particularly, when your Linux use the same disk as Windows, use the same Fat 32 partition as /boot/efi, then, really you know you are in potential trouble. Your bootloader can be kicked out at any time. Or, it may fall on its own sword… Who knows?
If you are prepared, it’s just a 15 minutes drawback. All you need is:
- An Arch iso with a little hand written (or ePub for me) memo with the commands you need to chroot you back in business. Then you can, either reinstall your bootloader, reinstall your Grub, even to a previous version, anything…
- Access to UEFI to check if some values (ie Sec boot) have not been changed.
Just my two cents. 
I haven’t had this happen on any of my installs with dual boot Windows that are on the same disc. But i do understand it can and has for some users. I also see many users have had similar issues with systemd-boot and /efi. I don’t think either is any worse than the other. When they fail as you say sometimes it’s very unexpected and causes panic for some. 
I just speak by experience…
One very handy tool I use to host several isos is a Kingston 64 GB key with Ventoy.
I use it to stockpile some isos, one or two Arch isos, Clonezilla isos and some distros like EndeavourOS or Arcolinux.
I’ve read some bad comments about Ventoy. It’s always reliable with the isos already on the key. That’s already a big plus. It may fail with new isos. The main reason is often that the version of the Ventoy software is not on a par with Ventoy2Disk. If you update the second one, the problem will likely be solved.
That’ll be two cents and a half…
@roger64 would it be possible for you to share with ISO’s do you keep in the Kingston 64 GB key with Ventoy?
Just to confirm, the ISO has to be downloaded into the Kingston 64 GB key and that’s it? Nothing more to be done? The Ventoy recognizes the new ISO and makes it available? Does it permit running of ISO directly from memory/RAM?
Currently I have 12 different isos, some quite old, but also EndeavourOS Mercury. I could still host a lot more. Also I added some ePubs containing notes for rescue purpose. Once you have Ventoy installed, (I use an AUR package named ventoy-bin), and the key is formatted (I did that some years ago, so follow the Ventoy guidelines for this), then you just have to copy the isos to the key.
After that, you can boot from the key (boot from USB must be enabled in the UEFI), it launches the Ventoy menu, you click on your selected iso and you can launch it live.
Pay attention that ventoy and ventoy2disk must have the same version (see image in previous post).
1 Like
I like it when a grub-upgrade fails because then you need to relearn how to chroot and repair your system. 
I got to learn it yesterday when the upgrade failed. But the only fix I needed to do though was to change the boot-order in my bios …
Yeah. A broken system, chrooting, fixing stuff… what’s not to love 
1 Like
A broken system, chrooting, fixing stuff…
3 Likes
Well I DO see the logic, that if you don’t occasionally have to do it, you forget how.
That’s what the internet is for 
I don’t want to have to totally relearn (not parrot what I don’t understand) every time…I’d like an order of retention please, with large fries.
Retention is OK, but not having a problem is better imo even if I forget.
1 Like
sudo pacman -S arch-wiki-docs
All you ever need. EVER!
3 Likes
This ought to be installed by default along with EOS. I did not know that this package existed. Thanks @cactux
1 Like
Thanks @roger64 this helps. So we can have a combination of system rescue ISOs all installed together. For example SystemRescueCD, Conezilla. I am wondering if HirenBootCD can also be incorporated like this? Have you tried this?
You’re welcome.
I once had a Hiren CD many years ago. Now, I do not have use for it anymore