After pve upgrade from 7 to 8 a wrong kernel is loaded

[ronzle]

Hi upgraded 1 of 6 nodes from 7 to 8
After the upgrade i realized that there is still the kernel 5.4 is loaded.
Does anyone have the same issue ?

root@storage01:~# pveversion
pve-manager/8.1.4/ec5affc9e41f1d79 (running kernel: 5.4.41-1-pve)

root@storage01:~# uname -a
Linux storage01 5.4.41-1-pve #1 SMP PVE 5.4.41-1 (Fri, 15 May 2020 15:06:08 +0200) x86_64 GNU/Linux

root@storage01:~# cat /etc/apt/sources.list.d/*
# deb http://download.proxmox.com/debian/ceph-quincy bullseye main


deb http://download.proxmox.com/debian/ceph-quincy bookworm test


deb https://enterprise.proxmox.com/debian/pve bookworm pve-enterprise
deb http://download.proxmox.com/debian/pve bookworm pve-no-subscription

 

[jsterr]

Hello @ronzle no I did not notice that. But you should not have both repositories enabled (you have enterprise AND no subscription enabled)
Whats the history of /var/log/apt/history.log ?

You could pin the new kernel with proxmox-boot-tool if you want.

 

[ronzle]

Hi i did the pinning, but this 5.4 kernel is still used
all other 5 hosts are working fine, but this one keeps the 5.4 kernel, it doesn't matter what i do
Have you got any experience with

proxmox-boot-tool reinit

 

[jsterr]

Hi i did the pinning, but this 5.4 kernel is still used
all other 5 hosts are working fine, but this one keeps the 5.4 kernel, it doesn't matter what i do
Have you got any experience with

proxmox-boot-tool reinit

Whats the output of proxmox-boot-tool status and proxmox-boot-tool kernel list ?
You can also do update-initramfs -u followed by a proxmox-boot-tool refresh

 

[ronzle]

root@storage01:~# proxmox-boot-tool status
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
E: /etc/kernel/proxmox-boot-uuids does not exist.
root@storage01:~# proxmox-boot-tool kernel list
Manually selected kernels:
6.5.11-8-pve

Automatically selected kernels:
5.4.41-1-pve
6.1.10-1-pve

Will try the commands and reboot .... added the result here

 

[ronzle]

root@storage01:~# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-6.5.11-8-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
root@storage01:~# proxmox-boot-tool refresh
Running hook script 'proxmox-auto-removal'..
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.

 

[jsterr]

root@storage01:~# proxmox-boot-tool status
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
E: /etc/kernel/proxmox-boot-uuids does not exist.
root@storage01:~# proxmox-boot-tool kernel list
Manually selected kernels:
6.5.11-8-pve

Automatically selected kernels:
5.4.41-1-pve
6.1.10-1-pve

Will try the commands and reboot .... added the result here

please also post efibootmgr -v looks like you are not using proxmox-boot-tool for the installation, you might need to check this: https://pve.proxmox.com/wiki/ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool

 

[ronzle]

root@storage01:~# efibootmgr -v
EFI variables are not supported on this system.

yes seems, but all other 5 nodes also not and the upgrade went fine there.

 

[jsterr]

root@storage01:~# efibootmgr -v
EFI variables are not supported on this system.

yes seems, but all other 5 nodes also not and the upgrade went fine there.

Please read the wiki docs, seems like this host was differently installed. The link is not related to the efibootmgr -v, means it might still be needed for your setup.

You will not need this if any of the following points are true:

• System installed using Proxmox VE ISO 6.4 or later
• System uses UEFI to boot and was installed in UEFI mode
• System is not using ZFS as the root filesystem

 

[ronzle]

i think this host was installed with version 5
Ok will check the wiki
Thanks for your help