Proxmox kernel 6.8.4-3-pve not booting - Intel microcode not installing

[golruck]

Hi there,

First post and quite newbie in Linux.

After posting the following post in the Proxmox forum, I have been advised to post it there too as I have an issue since the last update of Proxmox based on the kernel 6.8.4-3-pve:

https://forum.proxmox.com/threads/proxm ... ng.147327/

I have been advised to install the Intel microcode - my cpu 06-3c-03 - but it seems not wanting to load/install despite different attempts.

I am not sure what else would you need to help me but but please let me know. I tried to describe it clearly on the Proxmox forum but I can add some more here is you need anything.

My hardware:
Main Board ASRock E3C224-4L latest firmware
CPU INTEL "Haswell", 4x 3.4GHz, Socket 1150, Boxed (BX80646E31240V3)
Memory KINGSTON ValueRAM KVR16E11K4/32

The servers boot in the Recovery mode but not in the normal mode with the latest kernel. What does that mean? Can I leave it running in the recovery mode 24/7?

Would the microcode solve my issue or it is linked to something else?

I assume it would still be good to have the microcode installed for security/bugs reason so I would be grateful if someone could help me with this.

Thank you!

[Aki]

Hello,

After posting the following post in the Proxmox forum, I have been advised to post it there too as I have an issue since the last update of Proxmox based on the kernel 6.8.4-3-pve:
https://forum.proxmox.com/threads/proxm ... ng.147327/
I have been advised to install the Intel microcode - my cpu 06-3c-03 - but it seems not wanting to load/install despite different attempts.
[..]

The 6.8.4-3-pve kernel is not from the Debian repositories, but from a version customised by Promox, I presume.

These are current kernel version in Debian repositories:

Code: Select all

$ rmadison linux-image-amd64
linux-image-amd64 | 4.19+105+deb10u16  | oldoldstable               | amd64
linux-image-amd64 | 5.10.127-2~bpo10+1 | buster-backports           | amd64
linux-image-amd64 | 5.10.209-2         | oldstable                  | amd64
linux-image-amd64 | 5.10.216-1         | oldstable-proposed-updates | amd64
linux-image-amd64 | 6.1.67-1           | stable-updates             | amd64
linux-image-amd64 | 6.1.76-1~bpo11+1   | bullseye-backports         | amd64
linux-image-amd64 | 6.1.76-1           | stable                     | amd64
linux-image-amd64 | 6.1.90-1           | proposed-updates           | amd64
linux-image-amd64 | 6.7.12-1~bpo12+1   | stable-backports           | amd64
linux-image-amd64 | 6.7.12-1           | testing                    | amd64
linux-image-amd64 | 6.8.9-1            | unstable                   | amd64

Missing CPU microcode is generally not a reason for the kernel to fail to boot, unless the kernel has been modified to do so.

Therefore, there must be a reason other than microcode for the 6.8.4-3-pve Promox kernel to fail to boot.

These are the available versions for intel-microcode package in Debian repositories:

Code: Select all

$ rmadison intel-microcode
intel-microcode | 3.20201118.1~bpo10+1 | buster-backports/non-free           | source, amd64, i386
intel-microcode | 3.20220207.1~bpo11+1 | bullseye-backports/non-free         | source, amd64, i386
intel-microcode | 3.20220510.1~deb10u1 | oldoldstable/non-free               | source, amd64, i386
intel-microcode | 3.20231114.1~deb11u1 | oldstable/non-free                  | source, amd64, i386
intel-microcode | 3.20231114.1~deb12u1 | stable/non-free-firmware            | source, amd64, i386
intel-microcode | 3.20240312.1~deb11u1 | oldstable-proposed-updates/non-free | source, amd64, i386
intel-microcode | 3.20240312.1~deb12u1 | proposed-updates/non-free-firmware  | source, amd64, i386
intel-microcode | 3.20240514.1         | testing/non-free-firmware           | source, amd64, i386
intel-microcode | 3.20240514.1         | unstable/non-free-firmware          | source, amd64, i386

Hope this helps.

note: moved to "Off-Topic" sub-forum since it is not about Debian, but about a Promox customized kernel.

[golruck]

Thank you Aki for the quick reply and analyse on this - very helpful.

That is then clearly a Proxmox issue and I will seek further help from them.

I will keep this post updated once I have some more information unless you prefer I close it.

Best