I have a question regarding the use of mkgrub.sh.
I am establishing an AlmaLinux 8.5 Cobbler server to auto install CentOS 7 machines - legacy boot, EFI boot and EFI with Secure Boot enabled each on bare metal and on HyperV.
I can't get grub.0 or grubx64.efi to get past loading the NBP , they just load it and bomb out to the grub> prompt.
I've installed the grub2 modules for the legacy and EFI scenarios - grub2-pc-modules and grub2-efi-x64-modules (efibootmgr is already present and I havent got to shim yet so forget that right now)
mkgrub does make the necessary -o output files (I don't care about other architectures)
My questions are
Should I be running it on a centos7 machine (target) or on the AlmaLinux server? Presently I am running on the AlmaLinux server as I figured that were probably close enough and it appears to be trying to work.
Secondly while the $SYSLINUX dir in the script default is fine , the $GRUB2_MOD_DIR default is not present in AlmaLinux (usr/share/grub2) only /usr/share/grub , however strangely the script as I said does work even so. Should I install some other modules?
Pardon my ignorance. Not a developer, a sysadmin (grey line these days)
content_server = https://github.com/hbokh/cobbler-loadersper: https://github.com/cobbler/cobbler/issues/2660#issuecomment-859766544 I'll post if\when I get working, appreciate if you could do same