Updated Grub Package

General system Kernel, boot, graphics & hardware
1

I just noticed we got an updated grub package

Version : 2:2.06.r499.ge67a551a4-1

I hope everyone noticed and followed the requirements?

Edit:

[2023-04-16T19:04:59-0400] [PACMAN] starting full system upgrade
[2023-04-16T19:05:01-0400] [ALPM] running '05-snap-pac-pre.hook'...
[2023-04-16T19:05:01-0400] [ALPM-SCRIPTLET] ==> root: 616
[2023-04-16T19:05:01-0400] [ALPM] transaction started
[2023-04-16T19:05:02-0400] [ALPM] upgraded grub (2:2.06.r456.g65bc45963-1 -> 2:2.06.r499.ge67a551a4-1)
[2023-04-16T19:05:02-0400] [ALPM-SCRIPTLET] :: To use the new features provided in this GRUB update, it is recommended
[2023-04-16T19:05:02-0400] [ALPM-SCRIPTLET]    to install it to the MBR or UEFI. Due to potential configuration
[2023-04-16T19:05:02-0400] [ALPM-SCRIPTLET]    incompatibilities, it is advised to run both, installation and generation
[2023-04-16T19:05:02-0400] [ALPM-SCRIPTLET]    of configuration:
[2023-04-16T19:05:02-0400] [ALPM-SCRIPTLET]      $ grub-install ...
[2023-04-16T19:05:02-0400] [ALPM-SCRIPTLET]      $ grub-mkconfig -o /boot/grub/grub.cfg
[2023-04-16T19:05:02-0400] [ALPM] transaction completed
[2023-04-16T19:05:02-0400] [ALPM] running '30-systemd-update.hook'...
[2023-04-16T19:05:02-0400] [ALPM] running 'rebuild-detector.hook'...
[2023-04-16T19:05:02-0400] [ALPM] running 'texinfo-install.hook'...
[2023-04-16T19:05:02-0400] [ALPM] running 'zz-snap-pac-post.hook'...
[2023-04-16T19:05:03-0400] [ALPM-SCRIPTLET] ==> root: 617
[2023-04-16T19:41:58-0400] [PACMAN] Running 'pacman -S -y --config /etc/pacman.conf --'
[2023-04-16T19:41:58-0400] [PACMAN] synchronizing package lists
7 Likes
2

Perhaps we should help with the requirements? (aka what to do)

2 Likes
3

no : error on step build , they remove mm-debug , that was active on version r456

5

Wasn’t this addressed after the huge debacle with grub last year? I don’t think you have to run grub-install after an update anymore unless I’m sorely mistaken and about to screw up my system.

6

it’s probably a precaution, i’ve been update grub for a few versions without this recommendation, so far it’s fine. the other way around, the two lines are a small effort in contrast if something goes wrong again.
:man_shrugging:

1 Like
7

If you are on an UEFI based install, afaik the grub-install and grub-update are still needed. (I might be wrong, as I’ve been on Legacy-Bios, only for evermore…).

8

just BE careful with cryptoluks
see this r456 …
https://forum.manjaro.org/t/cant-boot-luks-encrypted-install-after-2023-03-31-stable-update/137411/7

1 Like
9

I hope this isn’t causing a huge problem. I just posted it to be aware there was a grub package update. I did update and ran the commands to reinstall grub and update grub and I didn’t have any issues. I don’t know if it is necessary but i followed the guidance. :thinking:

2 Likes
10

You can make a pacman hook.
If I am not mistaken, it could be a set-and-forget solution.

11

That could require an @dalto -response, if I am not mistaken. :wink:

As it depends on what the grub-devs have had in mind now, and in the future? :rofl:

12

I have one for Grub updates.
So far, it has been working fine on my system. :thinking:

13

Yes. But what, if…?

14

That’s a “philosophical” question :sweat_smile:

15

Sure, that I am. But I have so many systems running, and I always like to stay on the safe side. And people with UEFI systems still come asking, and I don’t have an UEFI system. So I can be a philosopher on that question… :wink:

Yet, to lessen the confusion about to embrace a whole community now, the Arch Devs haven’t changed anything yet in their politics, so the hook you have installed may still be very practical for any and all UEFI installs. :wink:

16

You should run it every time. For two reasons:

  1. You never know when backwards incompatible changes will be introduced
  2. If you don’t, you won’t be getting all of the updates including many of the security related updates.

Sure. As long as you understand the correct options to pass to grub-install, you can make a hook for a given installation. In most(but not all) cases, it is sufficient to run grub-install --no-nvram on UEFI installs.

4 Likes
17

This is exactly what I have in the hook and so far it has been fine through a couple of Grub updates on two of my systems.

18

So now @ricklinux (OP), with @dalto 's response can mark this thread as solved, finally.

Thank you all. :v:

19

I know this is solved, but how would you do the hook like @pebcak mentioned? I think this would be great to add as part of the solution for future reference.

Maybe @dalto could expand with quick instructions on the solution post?

2 Likes
20

Probably something like this:

[Trigger]
Operation = Upgrade
Type = Package
Target = grub

[Action]
Description = Reinstall Grub when the package is updated
When = PostTransaction
Exec = /bin/sh -c "/usr/bin/grub-install --no-nvram && /usr/bin/grub-mkconfig -o /boot/grub/grub.cfg"

Place in /etc/pacman.d/hooks.

As mentioned, the Grub installation command needs to be adjusted to what is appropriate for the specific system–there is not a single command that will work for everyone.

2 Likes