SOLVED: GRUB menu not showing updated kernels

General support questions
User avatar
TrevorH
Forum Moderator
Posts: 21162
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: GRUB menu list problem

Postby TrevorH » 2017/11/21 17:39:31

Do you have an /etc/grub.d/30_os-prober file?
CentOS 5 died in March 2017 - migrate NOW!
Full time Geek, part time moderator. Use the FAQ Luke

pjc123
Posts: 64
Joined: 2010/08/17 16:59:11

Re: GRUB menu list problem

Postby pjc123 » 2017/11/21 17:43:41

TrevorH wrote:Do you have an /etc/grub.d/30_os-prober file?


Yes.

pjc123
Posts: 64
Joined: 2010/08/17 16:59:11

Re: GRUB menu list problem

Postby pjc123 » 2017/11/22 15:52:26

EDIT (11-24-2017)

OK, I restored everything from an image backup dated before I sent the laptop for repair, and both OS's show up again. However, I updated both Centos and Mint to the latest updates and kernels, but I can't get the new kernels to show up on the GRUB menu list.

On the Mint side I ran

"sudo update-grub" and it added all the new Mint kernels there.

On the Centos side I ran

grub2-mkconfig -o /boot/grub2/grub.cfg,

and now all the kernels show up from Centos and Mint in the /boot/grub2/grub.cfg file dated today, but they are still not in the boot up menu.

I do notice that there is a separate and older dated /boot/grub.cfg with the current menu list.

Am I now supposed to copy /boot/grub2/grub/cfg into /boot/grub/cfg and everything will work? If that works it seems like something is not set up properly or I am running the wrong command.

pjc123
Posts: 64
Joined: 2010/08/17 16:59:11

Re: GRUB menu not showing updated kernels

Postby pjc123 » 2017/11/30 19:37:29

SOLVED:

After looking at timestamps and the various grub files I tried the following and it worked:

1) Booted up into Linux Mint and ran

update-grub

2) Booted up into Centos and ran

grub2-mkconfig -o /boot/grub/grub.cfg


The problem was that I was running grub2-mkconfig -o /boot/grub2/grub.cfg like I saw in examples everywhere, but grub was not picking up the grub,cfg file in /boot/grub2, rather it was using /boot/grub/.