It is not. You need to install GRUB every time it is updated. The system upgrade only upgrades the package grub, it does not upgrade your actual bootloader.
Use the search feature of the forum, this has been discussed ad nausiam in the past.
3 Likes
Copy that. In all honesty, I haven’t used GRUB in years. I accidentally chose that option upon installing EndeavourOS. I just decided to leave it rather than re-install the OS and choose Systemd. Wish I could just change to Systemd now. I have rebooted a couple times since without issue. I’ll search the forum on explicit instructions to install GRUB again. I may just end up re-installing EndeavourOS and choose Systemd.
You don’t need to reinstall.
It is possible to switch to systemd-boot.
You might be better off creating a new topic for that if you need assistance.
3 Likes
No grub is a package that gets installed. Then you have to install the package grub. Then after installing grub you have to run the grub update command to create the new grub package configuration.
1 Like
Is it as simple as running these 2 commands?
sudo grub-install --no-nvram
sudo grub-mkconfig -o /boot/grub/grub.cfg
2 Likes
I’ve seen some people advise this with 3 periods as opposed to –no-nvram. What is the difference between them and does it matter which I do?
sudo grub-install ...
sudo grub-mkconfig -o /boot/grub/grub.cfg
sudo grub-install --no-nvram
sudo grub-mkconfig -o /boot/grub/grub.cfg
There seems to be some “confusion” regarding grub, the package and grubx64.efi, the efi bootloader binary.
Using pacman -S grub or updating your system with the package already installed, will only install or update the package grub.
Then you would need to install grubx64.efi into the appropriate location.
The command line grub-install will do that and the location by default will be /boot/efi (or rather more precisely: /boot/efi/EFI/NAME, where NAME is the name of the directory containing grubx64.efi).
The … means nothing. I think it is unfortunate that they use this to imply, I guess, that you would need to use appropriate options for your system/usecase.
This means that grubx64.efi will be installed in the default location but the efi boot entry in nvram wont be changed/updated.
1 Like
I don’t think the three periods are correct. It may just be showing there could be other entries such as the path? I’m no expert but i use grub over systemd-boot. It’s just my personal preference. @pebcak is more knowledgeable.
So I could just do the following, without the periods, correct?
sudo grub-install
sudo grub-mkconfig -o /boot/grub/grub.cfg
1 Like
I would add –no-nvram as well.
The efi boot entry in NVRAM won’t need updating each time grub gets updated.
2 Likes
I typically don’t use the --no-nvram but that is because i always forget about it. In the past the ISO’s used naming a convention that had a numbering system so it changed with ISO’s so i wanted it to rewrite the entries. Now It’s not done that way that I see. This all brings me back to the grub fiasco when there were a lot of issues with a newer grub version which hadn’t happened in a while.
2 Likes
quick and painless…
[wombat64@endeavour ~]$ sudo grub-install --no-nvram
[sudo] password for wombat64:
Installing for x86_64-efi platform.
Installation finished. No error reported.
[wombat64@endeavour ~]$ sudo grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
Found background: /usr/share/endeavouros/splash.png
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux.img
Found fallback initrd image(s) in /boot: intel-ucode.img initramfs-linux-fallback.img
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done
[wombat64@endeavour ~]$
Rebooted and all is good. appreciate all the advice here. Many thanks!
3 Likes
I can not find changelog for a new update ? to see why everyone is talking about grub update 
Check your updates in /var/log/pacman.log See if you got a new grub package.
1 Like
You would need to look at the commits since the last update to see what changed.
The Arch grub package isn’t based on grub releasing new code, it is updating to a later commit.
1 Like
Yes, the … is a place holder for whatever else you need on that command. for instance, if I have my system installed on a legacy/bios system, my grub-install command looks like:
grub-install --target=i386-pc /dev/sda
And if I have my installation on a UEFI system, my command looks like this:
grub-install --target=x86_64-efi --efi-directory=/efi --bootloader-id=ezarcher --recheck
So I cannot predict what any user needs to add to the grub-install command to make it complete. The … simply means fill in the right details for your situation.
1 Like
That was sort of what I meant kind of implicitly but thanks for the clarification!
I still think that the choice of … is a bit misleading as I have seen several times other users just run the line as is:
grub-install ...
EXACTLY. It appears the the … is part of the command.
1 Like
I realise I’m not sure if this thread helps me with my grub-anxiety?! 
I got my grub on! 
No anxiety here.
1 Like