Proxmox server crash

K

kermitxyz

New Member
Jun 26, 2025
10
0
1
Hello

My Proxmox server crashed with the following errors in the log. Please could someone explain how to interpret this? Thank you

Code: 
Jun 30 14:02:24 bagpuss kernel: e1000e 0000:00:1f.6 nic0: Detected Hardware Unit Hang:
                                  TDH                  <fc>
                                  TDT                  <1b>
                                  next_to_use          <1b>
                                  next_to_clean        <fb>
                                buffer_info[next_to_clean]:
                                  time_stamp           <10479cedf>
                                  next_to_watch        <fc>
                                  jiffies              <10479d300>
                                  next_to_watch.status <0>
                                MAC Status             <80083>
                                PHY Status             <796d>
                                PHY 1000BASE-T Status  <3800>
                                PHY Extended Status    <3000>
                                PCI Status             <10>
Jun 30 14:02:25 bagpuss corosync[1097]:   [KNET  ] link: host: 2 link: 0 is down
Jun 30 14:02:25 bagpuss corosync[1097]:   [KNET  ] host: host: 2 (passive) best link: 0 (pri: 1)
Jun 30 14:02:25 bagpuss corosync[1097]:   [KNET  ] host: host: 2 has no active links
Jun 30 14:02:25 bagpuss corosync[1097]:   [TOTEM ] Token has not been received in 2250 ms
Jun 30 14:02:26 bagpuss corosync[1097]:   [TOTEM ] A processor failed, forming new configuration: token timed out (3000ms), waiting 3600>
Jun 30 14:02:26 bagpuss kernel: e1000e 0000:00:1f.6 nic0: Detected Hardware Unit Hang:
                                  TDH                  <fc>
                                  TDT                  <1b>
                                  next_to_use          <1b>
                                  next_to_clean        <fb>
                                buffer_info[next_to_clean]:
                                  time_stamp           <10479cedf>
                                  next_to_watch        <fc>
                                  jiffies              <10479dac0>
                                  next_to_watch.status <0>
                                MAC Status             <80083>
                                PHY Status             <796d>
                                PHY 1000BASE-T Status  <3800>
                                PHY Extended Status    <3000>
                                PCI Status             <10>
Jun 30 14:02:28 bagpuss kernel: e1000e 0000:00:1f.6 nic0: Detected Hardware Unit Hang:
                                  TDH                  <fc>
                                  TDT                  <1b>
                                  next_to_use          <1b>
                                  next_to_clean        <fb>
                                buffer_info[next_to_clean]:
                                  time_stamp           <10479cedf>
                                  next_to_watch        <fc>
                                  jiffies              <10479e280>
                                  next_to_watch.status <0>
                                MAC Status             <80083>
                                PHY Status             <796d>
                                PHY 1000BASE-T Status  <3800>
                                PHY Extended Status    <3000>
                                PCI Status             <10>
Jun 30 14:02:30 bagpuss corosync[1097]:   [QUORUM] Sync members[1]: 1
Jun 30 14:02:30 bagpuss corosync[1097]:   [QUORUM] Sync left[1]: 2
Jun 30 14:02:30 bagpuss corosync[1097]:   [TOTEM ] A new membership (1.78) was formed. Members left: 2
Jun 30 14:02:30 bagpuss corosync[1097]:   [TOTEM ] Failed to receive the leave message. failed: 2
Jun 30 14:02:30 bagpuss pmxcfs[948]: [dcdb] notice: members: 1/948
Jun 30 14:02:30 bagpuss pmxcfs[948]: [status] notice: members: 1/948
Jun 30 14:02:30 bagpuss corosync[1097]:   [QUORUM] This node is within the non-primary component and will NOT provide any services.
Jun 30 14:02:30 bagpuss corosync[1097]:   [QUORUM] Members[1]: 1
Jun 30 14:02:30 bagpuss corosync[1097]:   [MAIN  ] Completed service synchronization, ready to provide service.
Jun 30 14:02:30 bagpuss pmxcfs[948]: [status] notice: node lost quorum
Jun 30 14:02:30 bagpuss pmxcfs[948]: [dcdb] crit: received write while not quorate - trigger resync
Jun 30 14:02:30 bagpuss pmxcfs[948]: [dcdb] crit: leaving CPG group
Jun 30 14:02:30 bagpuss pve-ha-lrm[1186]: unable to write lrm status file - unable to open file '/etc/pve/nodes/bagpuss/lrm_status.tmp.1>
Jun 30 14:02:30 bagpuss pmxcfs[948]: [dcdb] notice: start cluster connection
Jun 30 14:02:30 bagpuss pmxcfs[948]: [dcdb] crit: cpg_join failed: CS_ERR_EXIST
Jun 30 14:02:30 bagpuss pmxcfs[948]: [dcdb] crit: can't initialize service
Jun 30 14:02:30 bagpuss kernel: e1000e 0000:00:1f.6 nic0: Detected Hardware Unit Hang:
 
Your network card crashed. This unfortunately is a common issue with e1000e.

See for example:
A

Thread 'e1000 driver hang'

In the past week we are seeing random e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang failuresacross all our nodes, even different hardware hosts. Must do a reset of the host.

There are lots of references to this issue going back 5+ years. Was there a driver change with the latest updates? We've run years with this hardware without issue. Now just this week its popping up all over.

Kernel Version Linux 5.0.21-2-pve #1 SMP PVE 5.0.21-3 (Thu, 05 Sep 2019 13:56:01 +0200)
PVE Manager Version pve-manager/6.0-7/2898402

Sep 22 20:03:08 vmhost03 kernel: [154458.471981] e1000e...
  • Like
B

Thread 'e1000e eno1: Detected Hardware Unit Hang:'

Hello,

i am using Proxmox on an Intel NUC NUC8i3BEH2.
Actually it is running quite stable for a long time, but recently there is some more persistent network throuput (5-10 mb/s for several hours) on an Qemu vm and I get the following message from time to time "Detected Hardware Unit Hang" (see dmesg output). When I reboot the system it works for maybe 1-2 hours and than (after the persistent network throughput) I got the message again. I also tried ethtool -K eno1 tso off gso off but the hang still appears.
I got some lxc containers which are connected directly with bridge...
  • Like
J

Thread 'Internet connection to Proxmox failing'

Hi,

I've recently switched my home assistant instance to a refurbished HP Elitedesk running proxmox. It's all running fine except for that once every few weeks or so it seems to lose it's internet connection making both HA and Proxmox unreachable. The fix at that moment is quite simple, just take out the ethernet cable and plug it back in after a few seconds. I've tried to see if there is a fault logged in proxmox, but can't see where this would be. I did see that the uptime is over 3 weeks, suggesting that proxmox didn't even recognise that it's lost its connection, although this might...
 
Last edited:
  • Like
Reactions: news and leesteken
You must log in or register to reply here.
Top Bottom
Back