Not fear-mongering, just a heads-up! 
Time to remember:
grub-install …
grub-mkconfig -o /boot/grub/grub.cfg
10 Likes
Between dracut, mkinitcpio, grub and systemd-boot on different computers and then what I have in VMs I cheat and use this to update my boots.
sudo pacman -S linux linux-headers
as linux and linux-headers are already installed it doesn’t have to download then and just reinstall and updating my whatever boot system I’m using on that rig. 
1 Like
I installed update-grub from AUR. Excecuted it and it worked fine…
[wombat64@endeavour ~]$ sudo update-grub
[sudo] password for wombat64:
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 ~]$
Just out of curiosity, why would you need an extra package from AUR which is a “Simple wrapper around grub-mkconfig” ?
You can for example make an alias for grub-mkconfig -o /boot/grub/grub.cfg.
Mine is: grup 
1 Like
@pebcak Probably just because of the history I have with Debian/Ubuntu/Mint. Just got used to it, I guess.
1 Like
Fair enough! Yet I reiterate that you could accomplish the same thing with an alias for example in
.bashrc: alias update-grub=‘grub-mkconfig -o /boot/grub/grub.cfg’
3 Likes
I used to have the even shorter “grup” alias:
alias grup="sudo grub-install --no-nvram && sudo grub-mkconfig -o /boot/grub/grub.cfg"
but now I use systemd-boot/dracut like all the best people 
2 Likes
I strangely noticed that the package libguestfs requires grub and therefore grub is installed… even though I am using systemd-boot on my host system. Is it safe to have both installed at the same time?
If you never run:
grub-install …
grub-mkconfig -o /boot/grub/grub.cfg
Then it should not interfere. If you never install grub to the boot sector of the drive with “grub-install” then there is no reason it should interfere with systemd-boot.
I assume @MasterRed installs grub to the root partition of each distro installed rather than the drive, sda1 instead of sda, for example.
1 Like
Yes, I’m running an instance of grub for each distro I have installed (three at the moment) and switch around them with a single systemd-boot instance. Works very well for me!
2 Likes
You mean systemd-boot manages multiple grubs? I imagine you have installed grub on each distro while unplugging the other drives at install time, right?
I let every distro manage its own grub, its easier that way in my experience. Then systemd-boot just points to the corresponding grub.efi file.
1 Like
That’s a nice solution!
Do you use some sort of “chainloading” in a /loader/entries/*****.conf ?
Would you mind sharing how you do it?
Edit: I guess something similar to this?
1 Like
the .conf entries are just two lines:
title EndeavourOS
efi /EFI/endeavouros/grubx64.efi
the loader.conf file looks like this:
timeout 1
default @saved
console-mode keep
2 Likes
That looks neat!
I’ve got a multiple boot system as well each installed with its own Grub. I may try this.
So I would need to do bootctl install from one of the systems and the configure the relelevant files?
Honestly can’t remember exactly how I did it then, but it should just be bootctl install. The system takes care of grub, as if it was the only bootloader, and I just manually edit the .conf files of systemd-boot, if needed.
1 Like
Thanks for bringing up the subject! I’ll look into it.
1 Like
This worked great! Now I can manage the booting of all the installed systems from one and the same boot screen. Works like a charm! Thanks again!
1 Like
Keep in mind that this does not install GRUB, so you are just updating config. This is what caused the famous Grubbening of 2020.
It was installed during the update. Why would I need to install it again? Isn’t updating GRUB after the installation during the update enough?