Skip to main content ↑ ↓
Topic: Grub 2:2.06.r322* might want to be very careful / avoid (Read 1821 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Grub 2:2.06.r322* might want to be very careful / avoid

Grub 2.2.06.r322 went to Arch repos on Aug 25 and seems to be causing near widespread panic that requires an ISO image to chroot.  I'm not sure it's everyone who is affected.

Luckily, this update hasn't yet made it to Artix repos.

Various references and forum carnage:
 
EOS notice: https://forum.endeavouros.com/t/the-latest-grub-package-update-needs-some-manual-intervention/30689
EOS forum thread (HUGE): https://forum.endeavouros.com/t/grub-2-2-06-r322-gd9b4638c5-1-wont-boot-and-goes-straight-to-the-bios-after-update/30653
Arch bbs threads so far:
 - https://bbs.archlinux.org/viewtopic.php?id=279115
 - https://bbs.archlinux.org/viewtopic.php?id=279167
Xerolinux (what is this distro?  it looks great though) : https://forum.xerolinux.xyz/thread-164.html
/r/Archlinux: https://www.reddit.com/r/archlinux/comments/wx90x4/latest_grub_update_testing_repo_couldnt_boot/

Might be a good time to ensure you have a recent ISO image on a USB stick just in case.

Re: Grub 2:2.06.r322* might want to be very careful / avoid

Reply #1 –
can confirm, just tested the update in a arch VM and had the same issue  :o
weird.. hope it'll be fixed upstream soon

Re: Grub 2:2.06.r322* might want to be very careful / avoid

Reply #2 –
Some users as observed have done a 'grub-install' after a -Syu that included the 2:2.06.r322* grub package and before a reboot, and apparently that works.  Or doesn't fail yet.

Re: Grub 2:2.06.r322* might want to be very careful / avoid

Reply #3 –
We'll hold off moving grub to stable, and keep it in our testing repo for now.
artist

Re: Grub 2:2.06.r322* might want to be very careful / avoid

Reply #6 –
Interesting post on the grub dev list.

https://lists.gnu.org/archive/html/grub-devel/2022-08/msg00381.html

Essentially, pointing fingers at Arch based distros for not running
Code: [Select]
grub-install
after updated grub packages are installed.

build 3 of the current Arch package puts messages into the terminal telling you to run
Code: [Select]
grub-install ...
and
Code: [Select]
grub-mkconfig ...
  Essentially users have to manually intervene and ideally before they reboot.  Maybe a pacman hook is put in place to handle this.  Arco lead is going that route for his distro.

Always carry a USB ISO with you though.

Re: Grub 2:2.06.r322* might want to be very careful / avoid

Reply #7 –
Judging from that mailing list post, it seems like Arch should just use a pacman hook and always run it on grub upgrades to me. I've personally never have had to run grub-install more than once, but if upstream expects that to be done on every upgrade then that's what should be followed.

Edit: Although thinking about this some more. Automating grub-install in a pacman hook would be hard because things can be different depending on what the user has installed.

Re: Grub 2:2.06.r322* might want to be very careful / avoid

Reply #8 –
Shortly after this came out I updated a BIOS only gremlins Artix install to the new grub 2:2.06.r322.gd9b4638c5-1 which I guess is the problem version, rebooted, absolutely fine, no action needed, this won't affect everyone (ie those using BIOS boot) - well, probably  ;D . However another machine has 2 drives, one with an old Windows install on the original drive. You can choose which drive to boot from the BIOS boot priorities or choose on the GRUB menu when the BIOS option is set to boot the Linux drive first. Also it has an Ubuntu partition on the other drive along with Artix, Artix grub can't boot the Ubuntu one as it auto set up some BTRFS subvolumes, so the "grub" that boots things is the Ubuntu grub. OK, so that might be possible to resolve but it works. The point is though you'd need to be extremely careful about auto-running grub install on anyone's system without knowing exactly how they have put it all together and what they intend it to do, because for some people that will break their boot setups too.

Re: Grub 2:2.06.r322* might want to be very careful / avoid

Reply #9 –
Quote from: Dudemanguy – on
Judging from that mailing list post, it seems like Arch should just use a pacman hook and always run it on grub upgrades to me. I've personally never have had to run grub-install more than once, but if upstream expects that to be done on every upgrade then that's what should be followed.

Edit: Although thinking about this some more. Automating grub-install in a pacman hook would be hard because things can be different depending on what the user has installed.

>Edit: Although thinking about this some more. Automating grub-install in a pacman hook would be hard because things can be different depending on what the user has installed.

Can we make it an "optional" hook and ask the user to put in the hook file the grub-install command they used, and then run said command everytime a new grub update comes out?

Re: Grub 2:2.06.r322* might want to be very careful / avoid

Reply #10 –
Quote from: Lancia – on
Can we make it an "optional" hook and ask the user to put in the hook file the grub-install command they used, and then run said command everytime a new grub update comes out?

You can always just make your own hook.

Re: Grub 2:2.06.r322* might want to be very careful / avoid

Reply #11 –
Grub 2:2.06.r322.gd9b4638c5-4 landed in the System repo recently.

Watch the CLI messages when you next do a -Syu.as you'll need to run grub-install ... and grub-mkconfig ... with parameters for your system config before you reboot.

Else you'll have to artix-chroot in, mount, and run the two commands.

edit: s/griub/grub

Re: Grub 2:2.06.r322* might want to be very careful / avoid

Reply #12 –
thanks, i just noticed the new grub version when doing a pacman -Syu and wanted to tell about it
hope it won't go sideways like in arch  :D

edit: it went *almost* well. i made a typo in my install-grub, wich messed up my EFI entries..
i was prepared, so rebooted on a live iso on usb, mounted, chrooted, corrected with a new grub-install / grub-update, rebooted, and it booted normally :)

Re: Grub 2:2.06.r322* might want to be very careful / avoid

Reply #13 –
Quote from: AndBenn – on
Grub 2:2.06.r322.gd9b4638c5-4 landed in the System repo recently.

Watch the CLI messages when you next do a -Syu.as you'll need to run griub-install ... and grub-mkconfig ... with parameters for your system config before you reboot.

Else you'll have to artix-chroot in, mount, and run the two commands.
does not say to do "griub-install ... and grub-mkconfig" before rebooting, right?

Re: Grub 2:2.06.r322* might want to be very careful / avoid

Reply #14 –
Typo on "griub" oops and corrected.

I forget what the actual messages are as presented in the update flood in the terminal, but they look like the Arch announcement in that "you might have to do a grub-install and grub-mkconfig...".

Each command may need parameters for your configuration. You might as well note these, as for safety, each future grub update you'll need these - perfect little shell script though.  Or you could consider a pacman hook on grub.

And yes, after your update is done, and before you reboot is the optimal place to do them, unless you want the challenge to chroot in, mount and run them from there.