Node does not boot on the latest kernel

[GaMMachiPo]

Hello ! )

I saw a few days ago in the updates that the 5.15.107-2 kernel had arrived and I checked in the GUI of the node during a reboot but it the boot loader only loads the old version and I am not sure why.
I tried to force it on the next boot but it still didn't work.

proxmox-boot-tool kernel pin 5.15.107-2-pve --next-boot
I use UEFI with a ZFS pool at boot time (systemd-boot).
I don't know if it's related but when I run the "proxmox-boot-tool status" command, I get "WARN: /dev/disk/by-uuid/FCD2-3E48 does not exist" while the two disks of the pool are well seen by the system, but maybe it's because of the ZFS pool?

# apt list --installed | grep kernel
pve-kernel-5.15.102-1-pve/stable,now 5.15.102-1 amd64 [installed]
pve-kernel-5.15.107-2-pve/stable,now 5.15.107-2 amd64 [installed,automatic]
pve-kernel-5.15/stable,now 7.4-3 all [installed]

# proxmox-boot-tool status
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
System currently booted with uefi
FCD1-C743 is configured with: uefi (versions: 5.15.102-1-pve, 5.15.107-2-pve)
WARN: /dev/disk/by-uuid/FCD2-3E48 does not exist - clean '/etc/kernel/proxmox-boot-uuids'! - skipping

# proxmox-boot-tool kernel list
Manually selected kernels:
None.
Automatically selected kernels:
5.15.102-1-pve
5.15.107-2-pve

Thanks in advance for your help

GaMMa

 

[fiona]

Hi,
did you change anything about the disks recently? Does the second one show up when you do ls /dev/disk/by-uuid?

 

[GaMMachiPo]

Hi,

Indeed I had a problem a few days ago with one of the rpool disks, I had solved the problem by changing the disk but actually I just saw that there was an error when executing this order :

# proxmox-boot-tool format /dev/sdb2

I solved the problem with "--force"

# sgdisk /dev/sda -R /dev/sdb # sgdisk -G /dev/sdb # zpool replace -f rpool /dev/sdb3 /dev/sdb3 # proxmox-boot-tool format /dev/sdb2 # proxmox-boot-tool init /dev/sdb2

I just have a small question concerning the command "zpool replace -f rpool /dev/sdb3 /dev/sdb3" since the old partition and the new one have the same physical path, it gives me an error but the status of the pool goes online anyway so there is no problem?

Moreover I simply have 105M which are copied while the pool is used at 90G, is this normal but after a simple formatting of the disk?

resilvered 103M in 00:00:01 with 0 errors

Best regards,
GaMMa.