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

推荐订阅源

Project Zero
Project Zero
Y
Y Combinator Blog
雷峰网
雷峰网
Last Week in AI
Last Week in AI
人人都是产品经理
人人都是产品经理
F
Fortinet All Blogs
Microsoft Azure Blog
Microsoft Azure Blog
有赞技术团队
有赞技术团队
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
博客园 - Franky
博客园 - 聂微东
S
SegmentFault 最新的问题
Engineering at Meta
Engineering at Meta
罗磊的独立博客
M
MIT News - Artificial intelligence
B
Blog
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
大猫的无限游戏
大猫的无限游戏
V
V2EX
I
InfoQ
The Cloudflare Blog
Cloudbric
Cloudbric
Stack Overflow Blog
Stack Overflow Blog
V
Vulnerabilities – Threatpost
博客园_首页
Google DeepMind News
Google DeepMind News
Jina AI
Jina AI
T
The Exploit Database - CXSecurity.com
宝玉的分享
宝玉的分享
H
Hackread – Cybersecurity News, Data Breaches, AI and More
The GitHub Blog
The GitHub Blog
The Register - Security
The Register - Security
美团技术团队
K
Kaspersky official blog
C
CXSECURITY Database RSS Feed - CXSecurity.com
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
T
Tor Project blog
P
Privacy International News Feed
P
Privacy & Cybersecurity Law Blog
G
GRAHAM CLULEY
博客园 - 三生石上(FineUI控件)
Cyberwarzone
Cyberwarzone
Vercel News
Vercel News
Cisco Talos Blog
Cisco Talos Blog
D
Darknet – Hacking Tools, Hacker News & Cyber Security
C
Cisco Blogs
G
Google Developers Blog
Hacker News - Newest:
Hacker News - Newest: "LLM"
A
Arctic Wolf
MongoDB | Blog
MongoDB | Blog

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 Proxmox Backup Server 4.2 released! Advice ceph-osd crashes with kernel 6.17.2-1-pve on Dell system [META] Links on Proxmox Forum Website Hardwarer oder Software RAID Joining a cluster with already created guests VM PDM missing backup jobs from PVE / Log retention Remove VM.Monitor from all users/roles, PVE 9.2 Proxmox Freezing (new instalation) 9.2.2 - Intel 12700T No Web gui and random connection reset by peer [SOLVED] - i40e module for X710 Intel NIC Dutch Proxmox Day 2026 How pools use the space Corosync initiiert Reboot trotz Verfügbarkeit der Systeme Opt-in Linux 7.0 Kernel for Proxmox VE 9 available After PVE 8to9 upgrade, unable to check guest fs freeze status Problem with MegaRAID SAS3508 controller proxmox-kernel-7.0.2-6-pve failing network service Auto sync guest time after rollback of VM snapshot with RAM/state Broadcom BCM57504 (100G) bnxt_en TX timeout and NIC reset on Proxmox 8.1.5 — while BCM57414 (25G) works fine on same host QEMU 11.0 available on pve-test and pve-no-subscription as of now 350 MPM Solventless Lamination Machine for High-Speed Flexible Packaging Making sense of NVMe zfs and SMART errors [SOLVED] - PVE loses network connection after kernel upgrade to proxmox-kernel-7.0.0-3-pve [SOLVED] - Remove or reset cluster configuration. Proxmox 8.4.1 Fresh Install BCM57416 10G Ethernet Adapter Not Recognized PDM 1.1.1 unable to add AD realm with anonymous search [TUTORIAL] - Developer Workstation (Proxmox-VE 9) with cinnamon (LMDE7) SDN zone shows "pending" on peer nodes after node reboot (9.2.x) Cluster not quorate - extending auth key lifetime! Proxmox not rebooting properly (SOLVED) Proxmox 9 Stuck on loading initial ramdisk With new HA-Disarm Feature is there a Documentation for NUT Setup on Clusters? Proxmox 8.3 Installation Issue on ProLiant DL380 Gen9 Cluster networking setup LXC System images unavailable [SOLVED] - Fix: NVIDIA Drivers Failing after upgrade to Proxmox 9.2.2 (Kernel 7.0.2-6-pve) / NovaCore Conflict Install NUT directly on Proxmox VE and control guests from here driver usb for windows 7 System startup error and no network: Failed to start ifupdown2-pre.service - Helper to synchronize boot up for ifupdown. PBS backup space grow up constantly Proxmox Datacenter Manager 1.1 released! IPv4 not available in newly created VM Recommended Setup for Offsite Proxmox Backups? Hetzner Storage Box & Remote PBS Challenges duplicate, please delete this passthrought an USB device "by ID" to CT PDM Installer Freezes at 66% Tried PDM for the first time (version 1.1) - had issues PDM 1.1 automated install Suche Server-Provider für Proxmox connecting sdn to edge firewall SDN, IPAM & DHCP Migrating from read-only file system Ubuntu 26.04 installation fails for unknown reason Status Unbekannt nach Cluster Join Installing Proxmox Backup Server on Mac Mini (Late 2012) kernel 7.0 performance issue with zfs pools PVE becomes unreachable via ethernet but OS is running [SOLVED] - New 9.2 install - can't find 7.0.2-6-pve , not all the time [SOLVED] - Backup and dedupe a VM with LUKS Gibt es mit PVE 2.x ggf. Änderungen bei der RAM-Nutzung, bzw. deren Anzeige bei VMs? I need help for setting up backup solution Way more NAGware, very little functionality, bugs galore Root squashing virtiofsd with --uid-map Intel ixgbe Driver Update Fail Help to fix Proxmox access issues after power cut Passkey Login (not 2FA) Roblox VM detection - can be overcome? [TUTORIAL] - ZFS-Autosnaptshot inkl. Rollback und Daten direkt recovern (Windows/Linux) How to stop PVE Kernel upgrade [SOLVED] - very long waiting to log in to lxc debian 11 ssh [TUTORIAL] - Configuring Fusion-Io (SanDisk) ioDrive, ioDrive2, ioScale and ioScale2 cards with Proxmox Increase maximum USB devices in vm.conf
PVE crashes unexpectedly
invalid@exam · 2026-05-30 · via Proxmox Support Forum

Hello everyone,
I could use some help to figure out why my PVE instance crashes randomly. I am running version 6.14.8-2-pve on a Lenovo ThinkStation P360 which I repurposed from a regular desktop machine to run PVE.

Pulling the logs, I can see the following when PVE becomes unavailable and I have to do a hard reboot:

Code:

May 15 00:00:00 pm kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
                             TDH                  <b9>
                             TDT                  <d3>
                             next_to_use          <d3>
                             next_to_clean        <b8>
                           buffer_info[next_to_clean]:
                             time_stamp           <1257dfe98>
                             next_to_watch        <b9>
                             jiffies              <125ca9e00>
                             next_to_watch.status <0>
                           MAC Status             <80083>
                           PHY Status             <796d>
                           PHY 1000BASE-T Status  <3800>
                           PHY Extended Status    <3000>
                           PCI Status             <10>

Any suggestions what I can do to prevent PVE from crashing on me? I am using barely any hardware so it shouldn't be a heat related problem (I assume).

Last edited:

Thanks daanw, much appreciated! I ran the following command and will keep monitoring PVE for any potential hardware unit hangs.

Code:

ethtool -K eno1 gso off gro off tso off

The node has seen another crash within 48 hours. I'm adding the journalctl log from before the crash in case that helps figuring out the cause. Any suggestions?

Code:

May 31 10:51:14 pm pvedaemon[1282]: <root@pam> successful auth for user 'mirko@pve'
May 31 11:06:15 pm pvedaemon[1282]: <root@pam> successful auth for user 'mirko@pve'
May 31 11:17:01 pm CRON[238143]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
May 31 11:17:01 pm CRON[238145]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
May 31 11:17:01 pm CRON[238143]: pam_unix(cron:session): session closed for user root
May 31 11:21:16 pm pvedaemon[1280]: <root@pam> successful auth for user 'mirko@pve'
May 31 11:36:17 pm pvedaemon[1281]: <root@pam> successful auth for user 'mirko@pve'
May 31 11:42:52 pm pveproxy[123178]: worker exit
May 31 11:42:52 pm pveproxy[1291]: worker 123178 finished
May 31 11:42:52 pm pveproxy[1291]: starting 1 worker(s)
May 31 11:42:52 pm pveproxy[1291]: worker 242671 started
May 31 11:43:38 pm pveproxy[123177]: worker exit
May 31 11:43:38 pm pveproxy[1291]: worker 123177 finished
May 31 11:43:38 pm pveproxy[1291]: starting 1 worker(s)
May 31 11:43:38 pm pveproxy[1291]: worker 242809 started
May 31 11:44:12 pm pveproxy[123179]: worker exit
May 31 11:44:12 pm pveproxy[1291]: worker 123179 finished
May 31 11:44:12 pm pveproxy[1291]: starting 1 worker(s)
May 31 11:44:12 pm pveproxy[1291]: worker 242941 started
May 31 11:51:45 pm pvedaemon[1281]: <root@pam> successful auth for user 'mirko@pve'
May 31 12:07:45 pm pvedaemon[1280]: <root@pam> successful auth for user 'mirko@pve'
May 31 12:17:01 pm CRON[248560]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
May 31 12:17:01 pm CRON[248562]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
May 31 12:17:01 pm CRON[248560]: pam_unix(cron:session): session closed for user root
May 31 12:23:46 pm pvedaemon[1281]: <root@pam> successful auth for user 'mirko@pve'
May 31 12:49:15 pm systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories...
May 31 12:49:15 pm systemd-tmpfiles[254243]: /usr/lib/tmpfiles.d/legacy.conf:14: Duplicate line for path "/run/lock", ignoring.
May 31 12:49:15 pm systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
May 31 12:49:15 pm systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories.
May 31 13:17:01 pm CRON[259154]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
May 31 13:17:01 pm CRON[259156]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
May 31 13:17:01 pm CRON[259154]: pam_unix(cron:session): session closed for user root
May 31 14:17:01 pm CRON[269660]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
May 31 14:17:01 pm CRON[269662]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
May 31 14:17:01 pm CRON[269660]: pam_unix(cron:session): session closed for user root
May 31 14:38:20 pm kernel: hrtimer: interrupt took 13834 ns
May 31 15:17:01 pm CRON[280904]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
May 31 15:17:01 pm CRON[280906]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
May 31 15:17:01 pm CRON[280904]: pam_unix(cron:session): session closed for user root
May 31 15:20:13 pm systemd[1]: Starting apt-daily.service - Daily apt download activities...
May 31 15:20:13 pm systemd[1]: apt-daily.service: Deactivated successfully.
May 31 15:20:13 pm systemd[1]: Finished apt-daily.service - Daily apt download activities.
May 31 16:17:01 pm CRON[291806]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
May 31 16:17:01 pm CRON[291808]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
May 31 16:17:01 pm CRON[291806]: pam_unix(cron:session): session closed for user root
May 31 17:11:43 pm chronyd[1031]: Leap second list /usr/share/zoneinfo/leap-seconds.list needs update
May 31 17:17:01 pm CRON[302682]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
May 31 17:17:01 pm CRON[302684]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
May 31 17:17:01 pm CRON[302682]: pam_unix(cron:session): session closed for user root
May 31 18:17:01 pm CRON[313554]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
May 31 18:17:01 pm CRON[313556]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
May 31 18:17:01 pm CRON[313554]: pam_unix(cron:session): session closed for user root
May 31 19:17:01 pm CRON[324010]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
May 31 19:17:01 pm CRON[324012]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
May 31 19:17:01 pm CRON[324010]: pam_unix(cron:session): session closed for user root
May 31 20:17:01 pm CRON[334392]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
May 31 20:17:01 pm CRON[334394]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
May 31 20:17:01 pm CRON[334392]: pam_unix(cron:session): session closed for user root
May 31 21:10:13 pm systemd[1]: Starting apt-daily.service - Daily apt download activities...
May 31 21:10:13 pm systemd[1]: apt-daily.service: Deactivated successfully.
May 31 21:10:13 pm systemd[1]: Finished apt-daily.service - Daily apt download activities.
May 31 21:17:01 pm CRON[345399]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
May 31 21:17:01 pm CRON[345401]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
May 31 21:17:01 pm CRON[345399]: pam_unix(cron:session): session closed for user root
May 31 21:56:21 pm kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
                             TDH                  <f8>
                             TDT                  <aa>
                             next_to_use          <aa>
                             next_to_clean        <f7>
                           buffer_info[next_to_clean]:
                             time_stamp           <107257a8d>
                             next_to_watch        <f8>
                             jiffies              <107258240>
                             next_to_watch.status <0>
                           MAC Status             <80083>
                           PHY Status             <796d>
                           PHY 1000BASE-T Status  <3800>
                           PHY Extended Status    <3000>
                           PCI Status             <10>
May 31 21:56:23 pm kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
                             TDH                  <f8>
                             TDT                  <aa>
                             next_to_use          <aa>
                             next_to_clean        <f7>
                           buffer_info[next_to_clean]:
                             time_stamp           <107257a8d>
                             next_to_watch        <f8>
                             jiffies              <107258a40>
                             next_to_watch.status <0>
                           MAC Status             <80083>
                           PHY Status             <796d>
                           PHY 1000BASE-T Status  <3800>
                           PHY Extended Status    <3000>
                           PCI Status             <10>

The node has seen another crash within 48 hours. Any suggestions? I'm not sure about the best way to share the log files, do let me know if those would help.

Code:

May 31 21:56:21 pm kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
                             TDH                  <f8>
                             TDT                  <aa>
                             next_to_use          <aa>
                             next_to_clean        <f7>
                           buffer_info[next_to_clean]:
                             time_stamp           <107257a8d>
                             next_to_watch        <f8>
                             jiffies              <107258240>
                             next_to_watch.status <0>
                           MAC Status             <80083>
                           PHY Status             <796d>
                           PHY 1000BASE-T Status  <3800>
                           PHY Extended Status    <3000>
                           PCI Status             <10>
May 31 21:56:23 pm kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
                             TDH                  <f8>
                             TDT                  <aa>
                             next_to_use          <aa>
                             next_to_clean        <f7>
                           buffer_info[next_to_clean]:
                             time_stamp           <107257a8d>
                             next_to_watch        <f8>
                             jiffies              <107258a40>
                             next_to_watch.status <0>
                           MAC Status             <80083>
                           PHY Status             <796d>
                           PHY 1000BASE-T Status  <3800>
                           PHY Extended Status    <3000>
                           PCI Status             <10>

Furthermore here is the config I set for the NIC:

Code:

root@pm:~# ethtool -k eno1
Features for eno1:
rx-checksumming: on
tx-checksumming: on
        tx-checksum-ipv4: off [fixed]
        tx-checksum-ip-generic: on
        tx-checksum-ipv6: off [fixed]
        tx-checksum-fcoe-crc: off [fixed]
        tx-checksum-sctp: off [fixed]
scatter-gather: on
        tx-scatter-gather: on
        tx-scatter-gather-fraglist: off [fixed]
tcp-segmentation-offload: off
        tx-tcp-segmentation: off
        tx-tcp-ecn-segmentation: off [fixed]
        tx-tcp-mangleid-segmentation: off
        tx-tcp6-segmentation: off
generic-segmentation-offload: off
generic-receive-offload: off
large-receive-offload: off [fixed]
rx-vlan-offload: on
tx-vlan-offload: on
ntuple-filters: off [fixed]
receive-hashing: on
highdma: on [fixed]
rx-vlan-filter: off [fixed]
vlan-challenged: off [fixed]
tx-gso-robust: off [fixed]
tx-fcoe-segmentation: off [fixed]
tx-gre-segmentation: off [fixed]
tx-gre-csum-segmentation: off [fixed]
tx-ipxip4-segmentation: off [fixed]
tx-ipxip6-segmentation: off [fixed]
tx-udp_tnl-segmentation: off [fixed]
tx-udp_tnl-csum-segmentation: off [fixed]
tx-gso-partial: off [fixed]
tx-tunnel-remcsum-segmentation: off [fixed]
tx-sctp-segmentation: off [fixed]
tx-esp-segmentation: off [fixed]
tx-udp-segmentation: off [fixed]
tx-gso-list: off [fixed]
tx-nocache-copy: off
loopback: off [fixed]
rx-fcs: off
rx-all: off
tx-vlan-stag-hw-insert: off [fixed]
rx-vlan-stag-hw-parse: off [fixed]
rx-vlan-stag-filter: off [fixed]
l2-fwd-offload: off [fixed]
hw-tc-offload: off [fixed]
esp-hw-offload: off [fixed]
esp-tx-csum-hw-offload: off [fixed]
rx-udp_tunnel-port-offload: off [fixed]
tls-hw-tx-offload: off [fixed]
tls-hw-rx-offload: off [fixed]
rx-gro-hw: off [fixed]
tls-hw-record: off [fixed]
rx-gro-list: off
macsec-hw-offload: off [fixed]
rx-udp-gro-forwarding: off
hsr-tag-ins-offload: off [fixed]
hsr-tag-rm-offload: off [fixed]
hsr-fwd-offload: off [fixed]
hsr-dup-offload: off [fixed]

Not sure if this will solve the problem, but what I did is create a script using the System Daemon to automatically adjust the NIC settings I stated above when the server reboots.

I will monitor for a week and if no further crashes, will update here