Did you also use the grub-customizer ?
Yes, I think some files in /etc/grub.d/
might have been modified by grub-customizer, which prevented grub from regenerating grub.cfg after the update.
It fixed the problem, thank you all!
Now I just can’t edit entries, but I’ll see later and without grub-customizer.
As mentioned above the the customizer is not made for RHEL based Linux systems. Youcan manipulate the paths in the config file and check if you can make it run.
/etc/grub-customizer/grub.cfg
Soruce: FAQ #1397 : Questions : Grub Customizer
Then you can start Grub Customizer using the menu or by runninggksu grub-customizer
/sudo grub-customizer
On some distributions, this may fail (“bootloader not found”), because some of the commands / directories doesn’t exist on the expected names. Please make sure, these commands are accessible:
grub-mkconfig
grub-installand these pathes/files:
/etc/grub.d
/boot/grub
/boot/grub/grub.cfg
/etc/default/grubIf not, there may be alternative commands/pathes, if Grub2 is installed. Please try to find them out and create a config file at /etc/grub-customizer/grub.cfg containing this content (the values of this example are valid on fedora 16 - change them, if they are different):
MKCONFIG_CMD=grub2-mkconfig
INSTALL_CMD=grub2-install
MKFONT_CMD=grub2-mkfont
CFG_DIR=/etc/grub.d
OUTPUT_DIR=/boot/grub2
OUTPUT_FILE=/boot/grub2/grub.cfg
SETTINGS_FILE=/etc/default/grub
DEVICEMAP_FILE=“/boot/grub2/device.map”
MKDEVICEMAP_CMD=“grub2-mkdevicemap --device-map=/dev/stdout”
It says that the examples are valid for F16