You are not logged in.
- Topics: Active | Unanswered
#1 2022-08-28 11:56:22
- dungeonseeker
- Member
- Registered: 2022-04-06
- Posts: 7
About the recent grub update that destroyed many installs...
Yeah, it happened to me too, updated yesterday (after not updating for a few days prior) and when I rebooted my system went straight to UEFI. I've seen loads of others here (and users running Arch derivatives like Endevour & Manjaro) who had similar issues. Weirdly enough, I also couldn't use grub-btrfs to roll back using timeshift (same stack pointer error) nor could I even boot my second partition with Linux From Scratch (which has a different kernel and no grub installed at all).
Thought I'd share my findings here, full disclosure, I ended up reinstalling anyway (mostly because I had spent 3 hours troubleshooting and didn't think it was worth the time investment any longer).
I started off by reinstalling grub, this brought grub back to life however I still couldn't boot, it simply said Invalid Stack Pointer during stage 1. Next I killed the kernel, reinstalled it, created a fresh initramfs and ran grub-mkconfig, this did nothing. Next I killed grub, cleaned up all old boot files and reinstalled grub fully (as in pacman -R grub then pacman -S grub), again no change. It was at this point I noticed that the pacman hook to update Packagekit was failing (Unknown file or folder), killed pamac libpamac, pamac-appstream and packagekit then reinstalled the base arch-appstream-data but again no change. As per a suggestion I found I tried killing grub and installing refind, partial success here, it made it to stage 3 before it failed (something about refind not setting nvram). Then I used efibootmgr to remove all entries except for my current grub, no change.
During all this I had also done all the obvious things I could think of like clearing out early loaded kernel modules, removing all optional kernel parameters, replacing my grub.cfg with an entirely fresh one etc etc
Out of ideas I bit the bullet and reinstalled however after I realised, I was running Plymouth and Plymouth is also present on Manjaro & Endevour so now I'm wondering, is this an issue for users running Plymouth? If anyone has had a nuked install and hasn't reinstalled yet, wanna try chrooting in and killing plymouth?
Offline
#2 2022-08-28 18:14:45
- CarbonChauvinist
- Member
- Registered: 2012-06-16
- Posts: 413
- Website
Re: About the recent grub update that destroyed many installs...
"the wind-blown way, wanna win? don't play"
Offline
#3 2022-08-28 18:20:48
- jasonwryan
- Anarchist
- From: .nz
- Registered: 2009-05-09
- Posts: 30,426
- Website
Re: About the recent grub update that destroyed many installs...
Please edit your title and choose something a) less histrionic, and b) more descriptive.
No installs were "destroyed". No data was lost. No animals we harmed. You install Arch without a boot loader, you should be able to fix it change it if necessary.
Offline