RHEL7 Grub2 boot loader still uses the legacy Grub configuration files while booting the system

General support questions
Post Reply
amoha001
Posts: 1
Joined: 2020/03/20 21:50:50

RHEL7 Grub2 boot loader still uses the legacy Grub configuration files while booting the system

Post by amoha001 » 2020/03/20 21:53:24

We have upgraded our System from RHEL6 to RHEL7 which uses grub2 boot loader however while booting the system we still can see that the boot loader is still looking for the legacy /boot/grub/grub.conf for selecting the kernel and if the file doesn't contains the current installed kernel, it just complains! however it should use the /boot/grub2/grub.cfg instead So any ideas how to tell the system , hey body please wake up and use grub2 configuration files instead :)?

User avatar
jlehtone
Posts: 2589
Joined: 2007/12/11 08:17:33
Location: Finland

Re: RHEL7 Grub2 boot loader still uses the legacy Grub configuration files while booting the system

Post by jlehtone » 2020/03/21 17:52:39

amoha001 wrote:
2020/03/20 21:53:24
We have upgraded our System from RHEL6 to RHEL7
Therefore, you are a paying customer of Red Hat and should use their customer support to solve the issue. There is no upgrade option from CentOS 6 to CentOS 7.


That said, I've seen CentOS 7 in a VM, where the precreated image had /boot/grub/grub.conf. On installation of new kernel the 'grubby' does update bootloader config. Grubby did update the /boot/grub/grub.conf, but GRUB2 does read on boot the /boot/grub2/grub.cfg. Solution was simple: remove /boot/grub/grub.conf; after that grubby focuses on the correct config.
amoha001 wrote:
2020/03/20 21:53:24
if the file doesn't contains the current installed kernel, it just complains!
I was wondering who and how. Grub complains? It won't care about files that are not mentioned in the config, so that cannot be it.
Is it perhaps that "kernel to boot by default" has been saved to grubenv, but no such stanza is in the menu?

Post Reply

Return to “CentOS 7 - General Support”