maybe the ones I mentioned earlier
So should I delete these 3 hooks?
Should I uninstall grub-tools?
Should I modify my hook? What to modify? (sorry, plain clueless average Joe)
When it comes to Grub, who am I to plan or not plan something!
You should remove Install trigger, as already suggested. It doesn’t make any sense, and it is not safe, or well controllable behavior (it is an edge case, as already said).
It seems that one of EnOS hooks already updates grub,cfg, and your custom hook repeats this for no apparent benefit.
Either merge those hooks, or remove one of them, unless you don’t mind firing a grub-update twice) 
Grub acts on two targets:
- $ESP (
/boot/efi) creating/modifying a file*.efi - UEFI BIOS environment, adding/replacing a new boot entry in UEFI systems
So, --no-nvram
- if you are not on a UEFI system, it has no meaning (is ignored).
- It ignores the second target (UEFI environment) and only acts on $ESP files
Yes. Technically, it fixes how grub-mkconfig handles the results from os-prober for Arch-based distros.
1 Like
Either uninstall grub-tools or change your hook to not run grub-mkconfig. We no longer ship grub-tools in new installs. The reason you have it installed is because you used an old ISO to install.
1 Like
2 Likes
I believe my system is UEFI, (I do not know how to confirm)
Please check my previous post. I found them. I did not put them there.
Has upstream grub fixed the initrd issue? Is it tested working fine without EnOS hook?
I remember yes, you even told me then to use the new ISO, and I said I do not have it.
So, I will
yay -Rc grub-tools
Then reboot? Update first? Reinstall Grub first?
It should be sufficient to just remove it.
Yup, read that and went through the actual script as well. Just wanted to get a better idea of the things it does, so I know if it’s required for my setup or not. For now, it doesn’t look like it is.
Enough hijacking for now. Thanks for the help friends <3
1 Like
Done
[limo@asus ~]$ yay -Rc grub-tools
[sudo] password for limo:
checking dependencies...
Package (1) Old Version Net Change
grub-tools 1.6.9-2 -0.01 MiB
Total Removed Size: 0.01 MiB
:: Do you want to remove these packages? [Y/n]
:: Running pre-transaction hooks...
(1/1) Performing snapper pre snapshots for the following configurations...
==> root: 230
:: Processing package changes...
(1/1) removing grub-tools [------------------------------------] 100%
:: Running post-transaction hooks...
(1/3) Arming ConditionNeedsUpdate...
(2/3) Generating GRUB config to let grub-btrfs detect new snapshots...
Generating grub configuration file ...
Found theme: /boot/grub/themes/EndeavourOS/theme.txt
Found linux image: /boot/vmlinuz-linux-lts
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux-lts.img
Found fallback initrd image(s) in /boot: intel-ucode.img initramfs-linux-lts-fallback.img
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 be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Adding boot menu entry for UEFI Firmware Settings ...
Detecting snapshots ...
Found snapshot: 2022-10-08 16:08:31 | @/.snapshots/230/snapshot | pre | pacman -R -c --config /etc/pacman.conf -- grub-tools |
Found snapshot: 2022-10-08 16:00:30 | @/.snapshots/229/snapshot | single | timeline
Now I can just reboot without doing anything more?
Without the hook, it will behave exactly as it does from upstream. In this case, it will not generate working entries for other installs of Arch-based distros found by os-prober. Of course, this doesn’t apply to the local EOS install because that doesn’t rely on os-prober.
We have decided to ship grub in it’s completely default form.
4 Likes
I just want to be sure I’ll be safe.
No wondering if it works? 
1 Like
Yes, that package is just hooks so you can reboot now.
1 Like
Happily done and I am back.
Now I can say Grub updates will not cause me problems anymore (unless they change something else that causes another problem)
So, it is OK now. Nothing more needs to be done?
1 Like
Do you dual-boot(or plan to)? If not, you can uninstall os-prober.
1 Like
No way! Why should I if I am on EndeavourOS.
P.S. I dual booted only for one year when I first started Linux, just to feel safe.
After I was OK with Linux, there was no point in wasting disk space.
1 Like
Thanks @petsam
Sorry for late reply.
I believe leaving it would not hurt.
@dalto asked me (earlier post) to test my hook by “installing” Grub.
So, It won’t hurt if I leave it (I think).
Just for clarification and knowledge.
Install happens only when the package is not installed.
If the package is installed, you can’t re-install it, even if we use that term. It is actually a Sync/reSync operation (that’s what -S means 
If you don’t have grub package installed, for some reason, then the Install trigger fires. Then, it starts to make no sense 
. When you really install (for the first time), you might want to run the grub-install command with certain required parameters, which is not the case when you run grub-install while grub is actually installed on $ESP.
If it looks confusing, it is because … it is!
1 Like