Grub was updated. How to install Grub correctly to update Grub in UEFI?

General system Kernel, boot, graphics & hardware
21

Correct. Maybe I had to use ID “UEFI OS” so that the UEFI entry would have been updated?

Looks I’m using the wrong Grub entry now … Till now, I used UEFI OS entry … :frowning:

$ efibootmgr
BootCurrent: 0006
Timeout: 1 seconds
BootOrder: 0006,0000,0001
Boot0000* Windows Boot Manager	HD(1,GPT,ca93c27e-4b07-4f8b-9923-69db68ff19c2,0x800,0x32000)/\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000079000100000010000000040000007fff0400
Boot0001* GRUB	HD(1,GPT,05c28463-43d5-4939-aad4-67e2dbafc820,0x800,0x200000)/\EFI\GRUB\GRUBX64.EFI
Boot0006* UEFI OS	HD(1,GPT,05c28463-43d5-4939-aad4-67e2dbafc820,0x800,0x200000)/\EFI\BOOT\BOOTX64.EFI0000424f
22

No! Please see my comment above.
I would leave things as is. You have a functioning bootloader and that is what matters.

1 Like
23

Just edited my post … Do I have to use the new UEFI entry “GRUB“ now instead of “UEFI OS”?

24

No. You are using the correct one now.

That doesn’t mean that you were using the wrong one before. You were just using the Grub’s bootloader binary in the fallback path.

Just use the one you now created and you will be fine.

Next time you will get an update to the package grub, you don’t need to update the paths in the NVRAM. You can just run the following command to update the binary:

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

Followed by:

sudo grub-mkconfig -o /boot/grub/grub.cfg

That’s about it.

2 Likes
25

Thanks a lot for helping! :heart:

1 Like
26

In my case I think I’ve ever only used the path once on EOS to reinstall grub and update it. Usually i just run sudo grub-install and then the grub update command. :person_shrugging:

27

It was already explained by @Stagger_Lee above why on EOS you don’t need to use --efi-directory= with grub-install.

That also explains why OP needs to use it on their setup.

2 Likes
28

This is true. Never really thought much about it before. :innocent:

1 Like
29

Yesterday, I tried that in EndeavourOS. Wow, that is much much easier than in Arch Linux.

Looks like Arch Linux is not the right OS for me when it comes to trouble … Maybe I need a bit guidance, but only a little bit. That’s why I should think about using EndeavourOS again. :wink:

3 Likes
30

I have mine setup using btrfs with btrfs-assistant, snapper-support, and btrfsmaintenance on grub bootloader so you can boot on a snapshot. No issues with grub. The only issue is if you have to arch-chroot to repair your system then you have to mount all the subvolumes and you can also do the grub-install and update grub from there. But as long as your system is working and booting you can install and update grub from the working EOS.

1 Like
31

This was my setup till some weeks ago. But I decided to try EXT4 without Snapshots now. Let’s see … :wink:

1 Like
32

You were living in darkness
You’ve got to come to know the truth
You were living in darkness
You’ve now come to see the light.
–One Love by Dr. Alban
:grinning_face_with_smiling_eyes:

2 Likes
33

One of my favorite artists from the 90s … :wink:

34

Dont know about that, but I recently heard his remixed song. It was awesome.

1 Like
35

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.