SYSTEM DOWN : Proxmox constantly crashes after upgrade to version 5.15.60-1

[jensie]

Hello,

I need your help, I don't know where to start. My system crashed and can't be recovered. The only way, I currently, can access it is via the recovery mode. Even if I change the kernel in the GRUB to a lower version, I'm experiencing the same problem.
Observation : moving from the GRUB to the command line takes seconds, whereas in normal mode it takes forever and blocks.

Below are the details of my system :
proxmox-ve: 7.2-1 (running kernel: 5.15.60-1-pve)
pve-manager: 7.2-11 (running version: 7.2-11/b76d3178)
pve-kernel-helper: 7.2-12
pve-kernel-5.15: 7.2-11
pve-kernel-5.13: 7.1-9
pve-kernel-5.15.60-1-pve: 5.15.60-1
pve-kernel-5.15.53-1-pve: 5.15.53-1
pve-kernel-5.15.39-4-pve: 5.15.39-4
pve-kernel-5.15.39-2-pve: 5.15.39-2
pve-kernel-5.15.39-1-pve: 5.15.39-1
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-4-pve: 5.13.19-9
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 15.2.15-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-2
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-3
libpve-storage-perl: 7.2-10
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.6-1
proxmox-backup-file-restore: 2.2.6-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-2
pve-container: 4.2-2
pve-docs: 7.2-2
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-6
pve-firmware: 3.5-3
pve-ha-manager: 3.4.0
pve-i18n: 2.7-2
pve-qemu-kvm: 7.0.0-3
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.5-pve1

 

[jensie]

in journalctl, I found the following errors :
- acpi PNP0C14:01: duplicate WMI GUID
- MMIO Stale Data CPU bug present and SMT on, data leak possible
- ENERGY_PERF_BIAS: Set to 'nomal', was 'performance'
- device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA Log
- platform elsa.0: EISA : cannot allocate resource for mainboard
- platform elsa.0: Cannot allocate resource for EISA slot 1-8
- spl : loading out-of-tree module taints kernel
- znvpair: module license 'CDDL' taints kernel
- Disabling lock debugging due to kernel taint
- GPT: Primary header thinks ALt. header is not at the end of the disk
- GPT: 12582911 != 222298111
- GPT: Alternate GPT header not at the end of the disk
- GPT: 12582911 != 222298111
- GPT: Use GNU parted to correct GPT errors

 

[jensie]

I made a change to the BIOS - CPU C States to disabled and now the system is up again, but still would like to know what is causing this and if I should be concerned for the future.