The latest kernel downloads and installs but is never booted into

Ask Fedora
, ,
1

Hi,
I am new to this forum, and I’ve tried to find a solution to my problem but I haven’t found it unfortunately. For some reason when I upgrade my Fedora 30 system the kernel gets downloaded and installed, but when I restart the computer the new kernel is not in use. It happens both when I update through the Software application and when doing ‘dnf upgrade’.
I’ve read a bit and tried ‘dnf reinstall kernel*’ but that didn’t change anything.
Does anyone know what could have happened? It hasn’t been like this before and I’ve used Fedora at least since version 25.

[l@localhost-localdomain ~]$ sudo grubby --info ALL
index=0
kernel="/boot/vmlinuz-5.3.6-200.fc30.x86_64"
args="ro rhgb quiet"
root="UUID=b14dae21-e1ef-42df-bec6-656dd7026987"
initrd="/boot/initramfs-5.3.6-200.fc30.x86_64.img"
title="Fedora (5.3.6-200.fc30.x86_64) 30 (Thirty)"
id="2492266f597a4f3bb7baa128e1999625-5.3.6-200.fc30.x86_64"
index=1
kernel="/boot/vmlinuz-5.2.18-200.fc30.x86_64"
args="ro rhgb quiet"
root="UUID=b14dae21-e1ef-42df-bec6-656dd7026987"
initrd="/boot/initramfs-5.2.18-200.fc30.x86_64.img"
title="Fedora (5.2.18-200.fc30.x86_64) 30 (Thirty)"
id="2492266f597a4f3bb7baa128e1999625-5.2.18-200.fc30.x86_64"
index=2
kernel="/boot/vmlinuz-5.2.11-200.fc30.x86_64"
args="ro rhgb quiet"
root="UUID=b14dae21-e1ef-42df-bec6-656dd7026987"
initrd="/boot/initramfs-5.2.11-200.fc30.x86_64.img"
title="Fedora (5.2.11-200.fc30.x86_64) 30 (Thirty)"
id="2492266f597a4f3bb7baa128e1999625-5.2.11-200.fc30.x86_64"
index=3
kernel="/boot/vmlinuz-0-rescue-2492266f597a4f3bb7baa128e1999625"
args="ro rhgb quiet"
root="UUID=b14dae21-e1ef-42df-bec6-656dd7026987"
initrd="/boot/initramfs-0-rescue-2492266f597a4f3bb7baa128e1999625.img"
title="Fedora (0-rescue-2492266f597a4f3bb7baa128e1999625) 30 (Workstation Edition)"
id="2492266f597a4f3bb7baa128e1999625-0-rescue"
[l@localhost-localdomain ~]$ ll /boot/vmlinuz-*
-rwxr-xr-x. 1 root root 6794376 Jan 17  2017 /boot/vmlinuz-0-rescue-2492266f597a4f3bb7baa128e1999625
-rwxr-xr-x. 1 root root 9204424 Aug 29 15:09 /boot/vmlinuz-5.2.11-200.fc30.x86_64
-rwxr-xr-x. 1 root root 9204424 Oct  1 15:35 /boot/vmlinuz-5.2.18-200.fc30.x86_64
-rwxr-xr-x. 1 root root 9323208 Oct 14 15:32 /boot/vmlinuz-5.3.6-200.fc30.x86_64
[l@localhost-localdomain ~]$ cat /proc/version 
Linux version 5.2.11-200.fc30.x86_64 (mockbuild@bkernel03.phx2.fedoraproject.org) (gcc version 9.1.1 20190503 (Red Hat 9.1.1-1) (GCC)) #1 SMP Thu Aug 29 12:43:20 UTC 2019
[l@localhost-localdomain ~]$ dmesg | grep "Command line"
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.2.11-200.fc30.x86_64 root=/dev/sda1
2

Take a look at this issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1707621#c1

Regards.

3

update your GRUB with grub2-install /dev/sda

4

You can (re)generate your Grub configuration with the instructions given here: GRUB 2 - Fedora Project Wiki

You shoud not follow @robbinespu advice

and run grub2-install if you have an EFI based system!! Please be careful. If you have an legacy-BIOS system it will be fine though.

1 Like
5

Thanks for the answer. Too bad that the issue had been closed though without finding the root cause. It was reported on upgrade from 29->30, but in the meta data it said 28, and therefore it had been closed. Maybe a bit prematurely.

6

I forgot to mention it, but I have a dual boot system with a Ubuntu partition as well, and that disappeared when doing the grub install. Does anyone know how to get it back? It is not very important for me though since I hardly ever use it.

7

Hi @jonascl

Check the link that @florian left for you, there are how you should do grub2-mkconfig to reconige all entries, please read the whole text so what you understad what you need do.

Regards

1 Like
8

Running ‘grub2-mkconfig -o /boot/grub2/grub.cfg’ brought the Ubuntu partition back. Therefore I changed the accepted solution to florian’s. A big thank you to everyone for helping me!

3 Likes
9

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.