😎
Docs
  • Tamm - Docs
  • Azure
    • Sentinel KQL Samples
    • Managed Identities
    • Deploy Sentinel with Terraform
  • Docker
    • Allow standard user to interact with Docker
    • Install Docker
    • Installing and working with Traefik
    • Installing specific version of Docker
    • Deploy Guacamole
    • Traefik geoblock
    • Unpoller Prometheus UCG Ultra
  • HomeAssistant
    • HAOS install on Proxmox
    • Zigbee2MQTT
    • HAOS Reverse Proxy
    • ZBDongle-E
  • Kali
    • Enable RDP
  • Kubernetes
    • Cert manager with Cloudflare
    • On prem loadbalancer metallb
    • Nginx ingress
    • Cloudinit Rancher ubuntu
    • Rancher Ubuntu 18.04 node template
    • Velero with minio backend
    • vsphere pvc (in-tree)
    • Velero cheat sheet
    • nginx annotations examples
  • Linux
    • Expand lvm disk vmware
    • Expand lvm disk fresh install
    • Disk usage
    • flush-dns
    • Netplan config example
    • Add user in photon OS
    • SSH-Keys
    • Set timezone
    • sudo nopasswd
    • Add custom alias
    • Rocky Linux commands
  • macOS
    • Uninstall System extensions
    • 1Password Github setup
  • Microsoft 365
    • Powershell Cheat sheet
  • Portainer
    • Install Portainer
    • Add docker node
  • Powershell
    • GenericList example
    • Mixed stuff n things
    • Synopsis Template
    • Powershell Oh-my-posh
    • Powershell Sync Profile
    • Cleanup and install MS Graph module
  • Proxmox
    • Disable No Subscription notification
    • Import from vmware error
    • Proxmox commands
    • Proxmox on Intel NUC
    • Proxmox E1000
  • Terraform
    • Getting started
    • Deploy Sentinel
  • Unifi
    • Unifi Network App (migration)
    • Slow vlan throughput
    • interface-explanation
  • Windows
    • Network settings access denied
    • Windows GVLK Keys
    • Windows Server 2025
Powered by GitBook
On this page

Was this helpful?

  1. Proxmox

Proxmox E1000

This became more prominent in Proxmox 8.4.1 for me but some logs are still present in older versions as well.

journalctl -n 2000 | grep "Detected Hardware Unit Hang"

Would show something like

Apr 30 21:20:43 pve04 kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
Apr 30 21:20:45 pve04 kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
Apr 30 21:20:47 pve04 kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
Apr 30 21:20:49 pve04 kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
Apr 30 21:20:51 pve04 kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
Apr 30 21:20:53 pve04 kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
Apr 30 21:20:55 pve04 kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
Apr 30 21:20:57 pve04 kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
Apr 30 21:20:59 pve04 kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
Apr 30 21:21:01 pve04 kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
Apr 30 21:21:03 pve04 kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
Apr 30 21:21:05 pve04 kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
Apr 30 21:21:07 pve04 kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
Apr 30 21:21:09 pve04 kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
Apr 30 21:21:11 pve04 kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
Apr 30 21:21:13 pve04 kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:

Until the host becomes unresponsive

Seems to be a known issue with larger files and offloading

Fix

Test out (replace eno1 with interface name)

ethtool -K eno1 tso off gso off

More permanent fix would be to add it to the interfaces config

auto lo
iface lo inet loopback

iface eno1 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.1.4/24
        gateway 192.168.1.1
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094        
        post-up /sbin/ethtool -K eno1 tso off gso off
source /etc/network/interfaces.d/*
  1. Create a new service file

nano /etc/systemd/system/disable-offloading.service 
[Unit]
Description=Disable NIC offloading
After=network.target

[Service]
Type=oneshot
ExecStart=/sbin/ethtool -K en01 tso off gso off
RemainAfterExit=true

[Install]
WantedBy=multi-user.target
  1. Load the service and enable

systemctl daemon-reexec && systemctl daemon-reload && systemctl enable disable-offloading.service
PreviousProxmox on Intel NUCNextGetting started

Last updated 22 days ago

Was this helpful?

Another way would be to create a service like cryp0rr has done

https://www.reddit.com/r/Proxmox/comments/1drs89s/intel_nic_e1000e_hardware_unit_hang/
https://forum.proxmox.com/threads/intel-nic-e1000e-hardware-unit-hang.106001/post-765582
https://gist.github.com/crypt0rr/60aaabd4a5c29a256b4f276122765237