FYI: for those using the testing repos (GRUB)

General system Kernel, boot, graphics & hardware
1

I had (2) separate Arch-based systems crash on GRUB loading screen after updating today. The failed package in grub 2:2.12.r212.g4dc616657-2: Downgrading to grub 2.12 worked.

2

I’m on grub 2.2.12-3 on my system without issues.
( so far )

3

I am on GRUB version 2:2.12-3 currently and been fine so far, I assume this is a higher version than grub 2:2.12.r212.g4dc616657-2

I may have misunderstood the versions versions though, but I don’t have any new GRUB updates available currently.

4

I’m also on grub 2:2.12-3. I don’t see any new grub version in testing.

Edit: It’s in core testing.

Screenshot_20250221_212203
Screenshot_20250221_2122031920×1080 140 KB

5

@anon26269396, @_Six: my EOS workstation is also on the 2.2.12-3 version. The version I mentioned was from the core-testing repo.

1 Like
6

It was just posted sometime today.

1 Like
7

I see, thanks for clarifying, my mistake, I didn’t realise it was from testing.

1 Like
8

I’ll have to keep an eye out for it then so when it comes down the pipe i can install it and then run the grub update command.

9

I have pacman hooks to do that, so the new version was getting installed (no errors, btw), just wouldn’t boot afterwards.

10

Do the hooks on eos automatically do that? I’m not sure. :thinking:

11

No, they don’t, at least not the installation part.

12

I didn’t think so and that’s probably a good thing. But anyway I know you actually have to run the install for the new package and then run the grub update command. That’s what i always do anyway.

13 
$ pacman -Qi grub
Name            : grub
Version         : 2:2.12.r212.g4dc616657-2

I tried grub from core-testing repo on two Archlinux installation. It works correctly for me.
I did also this from Archlinux wiki after updating:

# grub-install --target=x86_64-efi --efi-directory=/efi --bootloader-id=GRUB
# grub-mkconfig -o /boot/grub/grub.cfg
14

Well that didn’t work for me and just brought me to grub rescue.

Edit: Only screwed up the bootloader. :thinking:

Edi: Okay i got it back. Normally i just use grub-install without a path. Not sure if this is the correct way but always worked. Using the command it changed the boot disc entry so i just changed it and now boots.

Edit:

[ricklinux@rick-ms7c37 ~]$ grub-install --version
grub-install (GRUB) 2:2.12.r212.g4dc616657-2
[ricklinux@rick-ms7c37 ~]$
15

Sorry, I mentioned Archlinux. I use /efi for bootloader directory. Maybe EndeavourOS uses another directory and tha was causing problem?

16

I use /boot/efi for all of my systems, including EOS/Arch. I have (2) GRUB pacman hooks that have always worked:

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

[Action]
Description = Update grub install
When = PostTransaction
Exec = /usr/bin/grub-install --no-nvram --efi-directory=/boot/efi

[Trigger]
Type = Package
Operation = Install
Operation = Upgrade
Operation = Remove
Target = linux*
Target = grub

[Action]
Description = Update grub config
When = PostTransaction
Exec = grub-mkconfig -o /boot/grub/grub.cfg
17

Ya you probably did but i wasn’t thinking about that. So now since i used your path I’ve probably screwed it up even though i am booting. How can I change it back to /boot/efi?

Edit: Can i just change the path in the command to?

sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB

Edit: I did this and ran the grub update command and is working. I didn’t have to change the boot order priority this time. So I guess it’s back to /boot/efi? How do i know for sure?

Edit: Not to worry I can go back to a previous snapshot and try this grub update again. I always knew it was /boot/efi on eos but it didn’t even dawn on me when making the change.

1 Like