惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Martin Fowler
Martin Fowler
D
DataBreaches.Net
F
Fortinet All Blogs
阮一峰的网络日志
阮一峰的网络日志
博客园_首页
Apple Machine Learning Research
Apple Machine Learning Research
H
Help Net Security
M
MIT News - Artificial intelligence
美团技术团队
人人都是产品经理
人人都是产品经理
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
The Cloudflare Blog
有赞技术团队
有赞技术团队
L
LangChain Blog
博客园 - Franky
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
博客园 - 【当耐特】
S
SegmentFault 最新的问题
V
Visual Studio Blog
Blog — PlanetScale
Blog — PlanetScale
Hugging Face - Blog
Hugging Face - Blog
B
Blog
I
InfoQ

Proxmox Support Forum

[SOLVED] - Github Auth for Mirrors-Kernel Repo? [Automation] Mass migration tool for MS Win11/Server Proxmox GUI hang - not response is it possible to reject or quarantine spam based on conditions I set ? The PVENode task list in PVE9 is partially obscured due to the terminal font being too large. About 100% error reporting due to pveproxy.service hooks Kubernetes overlay networking breaks when upgrading from PVE 9.1 to PVE 9.2.3 Zentraler Speicher No space left on device Combine datastore and direct file archival to tape Kernel panic VFS: Unable to mount root fs on unknown-block (0,0) sobald ein 7.x Kernel verwendet wird. How to migrate disk of a VM from one ZFS to another Windows Server 2025 fails to boot after PVE 9.2 / Linux 7.0 Kernel upgrade Cannot Install Proxmox on T610 Poweredge with H700 PERC card sdn Config. gateway not reachable How to safely change domain/FQDN? Welche Filterquote erreicht ihr? NFS Share status unknown on 2 of 5 nodes Can't connect to PVE9 consoles [solved] Can't connect to PVE9 consoles [solved] [SOLVED] - Use secondary network for PVE commands Created cluster, one node storage gone BUG: proxmox mail gateway FROM = null bypass spam filtering Moving existing PBS from VMWare workstation to PVE cluster Does eBGP SDN fabric support external peering? Bug: PDM 1.1 not recognizing valid license status Proxmox GUI hang - not response PVE crashes unexpectedly Proxmox Backup Server 4.2 released! Advice
Error: Sub-process /usr/bin/dpkg returned an error code (1)
invalid@exam · 2026-06-18 · via Proxmox Support Forum

I went to upgrade my pve nodes today, two out of the three seemed to have no issues at all and the last one failed with this return code. When I run pveversion -v I can see proxmox-ve: not correctly installed (running kernel: 6.14.11-4-pve) Anyone ever run into this? or have an idea on how to get this fixed?

Code:

proxmox-ve: not correctly installed (running kernel: 6.14.11-4-pve)
pve-manager: 9.2.3 (running version: 9.2.3/d0fde103346cf89a)
proxmox-kernel-helper: 9.2.0
proxmox-kernel-6.14: 6.14.11-9
proxmox-kernel-6.14.11-9-pve-signed: 6.14.11-9
proxmox-kernel-6.14.11-4-pve-signed: 6.14.11-4
proxmox-kernel-6.14.11-3-pve-signed: 6.14.11-3
proxmox-kernel-6.14.8-2-pve-signed: 6.14.8-2
amd64-microcode: 3.20251202.1~bpo13+1
ceph: 19.2.3-pve4
ceph-fuse: 19.2.3-pve4
corosync: 3.1.10-pve2
criu: 4.1.1-1
frr-pythontools: 10.6.1-1+pve2
ifupdown2: 3.3.0-1+pmx12
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.1
libproxmox-backup-qemu0: 2.0.2
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.1.1
libpve-apiclient-perl: 3.4.2
libpve-cluster-api-perl: 9.1.6
libpve-cluster-perl: 9.1.6
libpve-common-perl: 9.1.13
libpve-guest-common-perl: 6.0.3
libpve-http-server-perl: 6.0.5
libpve-network-perl: 1.6.6
libpve-notify-perl: 9.1.6
libpve-rs-perl: 0.15.3
libpve-storage-perl: 9.1.5
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2+pmx1
lxc-pve: 7.0.0-2
lxcfs: 7.0.0-pve1
novnc-pve: 1.7.0-1
proxmox-backup-client: 4.2.1-1
proxmox-backup-file-restore: 4.2.1-1
proxmox-backup-restore-image: 1.0.0
proxmox-firewall: 1.2.3
proxmox-kernel-helper: 9.2.0
proxmox-mail-forward: 1.0.3
proxmox-mini-journalreader: 1.6
proxmox-offline-mirror-helper: 0.7.4
proxmox-widget-toolkit: 5.2.3
pve-cluster: 9.1.6
pve-container: 6.1.10
pve-docs: 9.2.2
pve-edk2-firmware: 4.2025.05-2
pve-esxi-import-tools: 1.0.1
pve-firewall: 6.0.4
pve-firmware: 3.18-4
pve-ha-manager: 5.2.4
pve-i18n: 3.7.5
pve-qemu-kvm: 11.0.0-4
pve-xtermjs: 6.0.0-1
qemu-server: 9.1.16
smartmontools: 7.5-pve2
spiceterm: 3.4.2
swtpm: 0.8.0+pve3
vncterm: 1.9.2
zfsutils-linux: 2.4.2-pve1

Code:

apt dist-upgrade
The following packages were automatically installed and are no longer required:
  proxmox-headers-6.14.11-4-pve  proxmox-kernel-6.14.11-3-pve-signed
  proxmox-headers-6.17.2-1-pve   proxmox-kernel-6.17.2-1-pve-signed
Use 'apt autoremove' to remove them.

Summary:
  Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
  7 not fully installed or removed.
  Space needed: 0 B / 220 GB available

Continue? [Y/n] y
Setting up proxmox-kernel-7.0.6-2-pve-signed (7.0.6-2) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 7.0.6-2-pve /boot/vmlinuz-7.0.6-2-pve
Sign command: /lib/modules/7.0.6-2-pve/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Autoinstall of module kernel-mft-dkms/4.23.0 for kernel 7.0.6-2-pve (x86_64)
Building module(s)...(bad exit status: 2)
Failed command:
make -j48 KERNELRELEASE=7.0.6-2-pve all KPVER=7.0.6-2-pve

Error! Bad return status for module build on kernel: 7.0.6-2-pve (x86_64)
Consult /var/lib/dkms/kernel-mft-dkms/4.23.0/build/make.log for more information.

Autoinstall on 7.0.6-2-pve failed for module(s) kernel-mft-dkms(10).

Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
run-parts: /etc/kernel/postinst.d/dkms exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/proxmox-kernel-7.0.6-2-pve-signed.postinst line 20.
dpkg: error processing package proxmox-kernel-7.0.6-2-pve-signed (--configure):
 installed proxmox-kernel-7.0.6-2-pve-signed package post-installation script subprocess returned error exit status 2
Setting up proxmox-kernel-6.17.13-13-pve-signed (6.17.13-13) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 6.17.13-13-pve /boot/vmlinuz-6.17.13-13-pve
Sign command: /lib/modules/6.17.13-13-pve/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Autoinstall of module kernel-mft-dkms/4.23.0 for kernel 6.17.13-13-pve (x86_64)
Building module(s)...(bad exit status: 2)
Failed command:
make -j48 KERNELRELEASE=6.17.13-13-pve all KPVER=6.17.13-13-pve

Error! Bad return status for module build on kernel: 6.17.13-13-pve (x86_64)
Consult /var/lib/dkms/kernel-mft-dkms/4.23.0/build/make.log for more information.

Autoinstall on 6.17.13-13-pve failed for module(s) kernel-mft-dkms(10).

Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
run-parts: /etc/kernel/postinst.d/dkms exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/proxmox-kernel-6.17.13-13-pve-signed.postinst line 20.
dpkg: error processing package proxmox-kernel-6.17.13-13-pve-signed (--configure):
 installed proxmox-kernel-6.17.13-13-pve-signed package post-installation script subprocess returned error exit status 2
Setting up proxmox-kernel-6.17.2-1-pve-signed (6.17.2-1) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 6.17.2-1-pve /boot/vmlinuz-6.17.2-1-pve
Sign command: /lib/modules/6.17.2-1-pve/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Autoinstall of module kernel-mft-dkms/4.23.0 for kernel 6.17.2-1-pve (x86_64)
Building module(s)...(bad exit status: 2)
Failed command:
make -j48 KERNELRELEASE=6.17.2-1-pve all KPVER=6.17.2-1-pve

Error! Bad return status for module build on kernel: 6.17.2-1-pve (x86_64)
Consult /var/lib/dkms/kernel-mft-dkms/4.23.0/build/make.log for more information.

Autoinstall on 6.17.2-1-pve failed for module(s) kernel-mft-dkms(10).

Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
run-parts: /etc/kernel/postinst.d/dkms exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/proxmox-kernel-6.17.2-1-pve-signed.postinst line 20.
dpkg: error processing package proxmox-kernel-6.17.2-1-pve-signed (--configure):
 installed proxmox-kernel-6.17.2-1-pve-signed package post-installation script subprocess returned error exit status 2
dpkg: dependency problems prevent configuration of proxmox-kernel-6.17:
 proxmox-kernel-6.17 depends on proxmox-kernel-6.17.13-13-pve-signed | proxmox-kernel-6.17.13-13-pve; however:
  Package proxmox-kernel-6.17.13-13-pve-signed is not configured yet.
  Package proxmox-kernel-6.17.13-13-pve is not installed.
  Package proxmox-kernel-6.17.13-13-pve-signed which provides proxmox-kernel-6.17.13-13-pve is not configured yet.

dpkg: error processing package proxmox-kernel-6.17 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-kernel-7.0:
 proxmox-kernel-7.0 depends on proxmox-kernel-7.0.6-2-pve-signed | proxmox-kernel-7.0.6-2-pve; however:
  Package proxmox-kernel-7.0.6-2-pve-signed is not configured yet.
  Package proxmox-kernel-7.0.6-2-pve is not installed.
  Package proxmox-kernel-7.0.6-2-pve-signed which provides proxmox-kernel-7.0.6-2-pve is not configured yet.

dpkg: error processing package proxmox-kernel-7.0 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-default-kernel:
 proxmox-default-kernel depends on proxmox-kernel-7.0; however:
  Package proxmox-kernel-7.0 is not configured yet.

dpkg: error processing package proxmox-default-kernel (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve:
 proxmox-ve depends on proxmox-default-kernel; however:
  Package proxmox-default-kernel is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 proxmox-kernel-7.0.6-2-pve-signed
 proxmox-kernel-6.17.13-13-pve-signed
 proxmox-kernel-6.17.2-1-pve-signed
 proxmox-kernel-6.17
 proxmox-kernel-7.0
 proxmox-default-kernel
 proxmox-ve
Error: Sub-process /usr/bin/dpkg returned an error code (1)

Autoinstall of module kernel-mft-dkms/4.23.0 for kernel 7.0.6-2-pve (x86_64)
Building module(s)...(bad exit status: 2)
Failed command:
make -j48 KERNELRELEASE=7.0.6-2-pve all KPVER=7.0.6-2-pve

Error! Bad return status for module build on kernel: 7.0.6-2-pve (x86_64)
Consult /var/lib/dkms/kernel-mft-dkms/4.23.0/build/make.log for more information.

You installed a third-party kernel module that is not compatible with this Linux kernel versions. Please ask the maintainers of kernel-mft-dkms to provide you with a newer version and to support you. Looks like such incompatibilities have happened before: https://forum.proxmox.com/threads/pve7to8-broken-kernel.130989/post-577876