No upgrade works properly after proxmox-kernel-6.17.2-2

J

jgswinkels

Member
Jul 20, 2021
11
0
21
62
Hardware Micro-Star International MSI MS-7D91/MAG Z Tomahawk
92 GB Memory
My boot devices are two SATA SSD's and the data is on 2 * 1 TB PCIe x5 M.2 SSD's
I have a working ProxMox server for many years.


Working configuration:
package versions ProxMox booting into kernel 6.17.2-2.pve

proxmox-ve: 9.1.0 (running kernel: 6.17.2-2-pve)
pve-manager: 9.1.4 (running version: 9.1.4/5ac30304265fbd8e)
proxmox-kernel-helper: 9.0.4
proxmox-kernel-6.17.4-2-pve-signed: 6.17.4-2
proxmox-kernel-6.17: 6.17.4-2
proxmox-kernel-6.17.4-1-pve-signed: 6.17.4-1
proxmox-kernel-6.17.2-2-pve-signed: 6.17.2-2
proxmox-kernel-6.14.11-5-pve-signed: 6.14.11-5
proxmox-kernel-6.14: 6.14.11-5
proxmox-kernel-6.14.11-4-pve-signed: 6.14.11-4
proxmox-kernel-6.14.11-2-pve-signed: 6.14.11-2
proxmox-kernel-6.14.11-1-pve-signed: 6.14.11-1
proxmox-kernel-6.14.8-2-pve-signed: 6.14.8-2
ceph-fuse: 19.2.3-pve1
corosync: 3.1.9-pve2
criu: 4.1.1-1
frr-pythontools: 10.4.1-1+pve1
ifupdown2: 3.3.0-1+pmx11
intel-microcode: 3.20250812.1~deb13u1
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.0
libproxmox-backup-qemu0: 2.0.1
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.0.5
libpve-apiclient-perl: 3.4.2
libpve-cluster-api-perl: 9.0.7
libpve-cluster-perl: 9.0.7
libpve-common-perl: 9.1.4
libpve-guest-common-perl: 6.0.2
libpve-http-server-perl: 6.0.5
libpve-network-perl: 1.2.4
libpve-rs-perl: 0.11.4
libpve-storage-perl: 9.1.0
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2+pmx1
lxc-pve: 6.0.5-3
lxcfs: 6.0.4-pve1
novnc-pve: 1.6.0-3
proxmox-backup-client: 4.1.1-1
proxmox-backup-file-restore: 4.1.1-1
proxmox-backup-restore-image: 1.0.0
proxmox-firewall: 1.2.1
proxmox-kernel-helper: 9.0.4
proxmox-mail-forward: 1.0.2
proxmox-mini-journalreader: 1.6
proxmox-offline-mirror-helper: 0.7.3
proxmox-widget-toolkit: 5.1.5
pve-cluster: 9.0.7
pve-container: 6.0.18
pve-docs: 9.1.2
pve-edk2-firmware: 4.2025.05-2
pve-esxi-import-tools: 1.0.1
pve-firewall: 6.0.4
pve-firmware: 3.17-2
pve-ha-manager: 5.1.0
pve-i18n: 3.6.6
pve-qemu-kvm: 10.1.2-5
pve-xtermjs: 5.5.0-3
qemu-server: 9.1.3
smartmontools: 7.4-pve1
spiceterm: 3.4.1
swtpm: 0.8.0+pve3
vncterm: 1.9.1
zfsutils-linux: 2.3.4-pve1


After Upgrade last time ( about 1~2 months ago) I had a non working configuration.
That was proxmox-ve: 9.1.0 (running kernel: 6.17.4-1-pve)
I had to switch back to 6.17.2-2.pve ( current running config)

Today's update executed as recommended:
Changes are:

base-files (13.8+deb13u3) trixie; urgency=medium
base-files (13.8+deb13u2) trixie; urgency=medium
base-files (13.8+deb13u1) trixie; urgency=medium
base-files (13.8) unstable; urgency=medium
base-files (13.7) unstable; urgency=medium
base-files (13.6) unstable; urgency=medium
base-files (13.5) unstable; urgency=medium
base-files (13.4) unstable; urgency=medium
base-files (13.3) unstable; urgency=medium
base-files (13.2) unstable; urgency=medium
base-files (13.1) unstable; urgency=medium
base-files (13) unstable; urgency=medium
base-files (12.4) unstable; urgency=medium
base-files (12.3) unstable; urgency=high
base-files (12.2) unstable; urgency=medium
base-files (12.1) unstable; urgency=medium
base-files (12) unstable; urgency=medium
base-files (11.1) unstable; urgency=medium

etc ..etc ..

base-files (1.2.0-2) unstable; urgency=low
base-files (1.2.0-1) unstable; urgency=low

After reboot the new kernel 6.17.4-2 again a non working configuration.

Again ProxMox booting into old kernel 6.17.2-2 pve is a working system again.

I don't know how to extract any logfiles If a server is not working properly.
Can not access the server, only via KB en I see a lot of stuff I don't understand.
I used to see only the IP addres I need to use to loginto this working server.

Question:
what to do to fix this update issue?

Any help is welcome.
 
You must log in or register to reply here.
Top Bottom