I updated my proxmox today and got this. Might explain what happened.
amd64-microcode (3.20251030.1) unstable; urgency=high
This release ships microcode for family 0x1ah (Zen5) that cannot be
loaded by very outdated system firmware, due to the fix for the
"Entrysign" microcode signature issue (as described by AMD-SB-7033).
This release ships two sets of microcode for family 0x19h (Zen3,
Zen3+, Zen4):
* The most recent set of microcode updates, which will only work for
systems that had their system firmware (BIOS) properly updated to
address the Entrysign microcode signature vulnerability.
* A second set of older microcode "updates", for systems with outdated
system firmware still vulnerable to the Entrysign vulnerability.
As described by AMD:
"In order to not fully abandon machines affected by AMD-SB-7033 that
have not received the BIOS update, the family 19h microcode container
now includes a second patch for these machines that brings the microcode
to the highest possible level without the microcode signing fix. While a
BIOS update is highly recommended to receive the latest security updates
issued after the microcode signing vulnerability, this will allow
non-updated systems to at least receive some microcode updates beyond
the version provided by BIOS."
Note that any such systems *will remain vulnerable* to Entrysign and
anything else that has been fixed by microcode updates since then.
For more details, refer to AMD-SB-7033:
https://www.amd.com/en/resources/product-security/bulletin/amd-sb-7033.html
IMPORTANT NOTE: an updated Linux kernel with an updated AMD microcode
update driver is required in order to the "set of older microcode
updates" to be selected on systems with outdated firmware.
-- Henrique de Moraes Holschuh <hmh@debian.org> Sat, 08 Nov 2025 19:20:02 -0300Maybe installing the micro code from proxmox repo might help?
Good luck
The zfs plugin updates were supposed to fix the problem you are having - you have zfs-dkms installed when you don't need it with the proxmox kernel and it is failing to build the zfs module for 6.17 proxmox kernel. What is the output of:
dpkg -l | grep openme
sudo omv-salt deploy run zfs
Everything in your output is fine. What about:
dpkg -l | grep -E "zfs|linux-image|proxmox-"
I don"t know if this helps but this is what proxmox wants to do.
root@pve:~# apt dist-upgrade
The following package was automatically installed and is no longer required:
libzpool6linux
Use 'apt autoremove' to remove it.
Upgrading:
amd64-microcode libnvpair3linux proxmox-kernel-6.17 zfs-zed
ifupdown2 libuutil3linux zfs-initramfs zfsutils-linux
Installing dependencies:
libzfs7linux libzpool7linux proxmox-kernel-6.17.9-1-pve-signed
REMOVING:
libzfs6linux
Summary:
Upgrading: 8, Installing: 3, Removing: 1, Not Upgrading: 0
Download size: 128 MB
Space needed: 995 MB / 17.6 GB available
Continue? [Y/n] FYI
I don"t know if this helps but this is what proxmox wants to do.
That makes sense. Looks like your system is doing the correct actions. Proxmox put the libzpool7linux package in the repo which conflicts with the libzpool6linux package. That is why the libzpool6linux dependency was removed from the zfs plugin.
looks fine other than I would remove the debian kernels.
You should be able to. I would run this just in case
sudo apt-get install --reinstall proxmox-kernel-6.17
then reboot to the 6.17 kernel
Don’t have an account yet? Register yourself now and be a part of our community!
