13 Feb
2017
13 Feb
'17
10:05 a.m.
On 13/02/2017 09:53, Dominic Cleal wrote:
Make sure that /etc/grub2.cfg exists and is a symlink
to
/boot/grub2/grub.cfg.
Yes, it does after running grub2-mkconfig before.
Otherwise try running `new-kernel-pkg -v --package
kernel --install
3.10.0-514.6.1.el7.x86_64` (for a version you've got installed) and it
should state why it's not running grubby.
That also appears to work now:
[root@osprey ~]# new-kernel-pkg -v --package kernel --install
3.10.0-514.6.1.el7.x86_64
initrdfile is /boot/initrd-3.10.0-514.6.1.el7.x86_64.img
making it the default based on config
/etc/grub.conf does not exist, not running grubby for grub 0.97
adding 3.10.0-514.6.1.el7.x86_64 to /boot/grub2/grub.cfg
- Making a normal entry.
/etc/grub2-efi.cfg does not exist, not running grubby for grub 2 with UEFI
/etc/lilo.conf does not exist, not running grubby
/etc/extlinux.conf does not exist, not running grubby for extlinux
From that output, I'm assuming that it wasn't
creating an entry before
because /boot/grub2/grub.cfg didn't exist. Now that it
actually exists
it should hopefully add an entry for any new kernel updates.
Thanks,
Mike