Hi all,
I am running into an issue with HA. I have updated HA completely and afterwards updated Proxmox (8.4.21) and all of its packages. After this HA works, but after a couple of hours becomes unresponsive. On the image below you can see that at a certain moment the CPU goes to 100% and that moment it looks like it stops responding. I had the same yesterday, did a hard restart and it worked again, but after a couple of hours it’s unresponsive again.
What can I do best now to fix this?
What happened at 10pm? Any automations kick in?
Are you sure it is not doing some more updates behind the scenes?
Anything of note in the system error logs?
Have you tried restarting in safe mode?
If you are running the core beta version there is proxmox cpu bug. See the Discord Beta channel.
I don’t think I am on a beta version.
There are no repairs listed and the system information can be found below. The logs also show nothing special.
I haven’t changed anything in automations or so, but just updated everything. When it happens, both HA and Proxmox are unresponsive. Could it still be the proxmox cpu bug or something else?
| version | core-2026.8.3 |
|---|---|
| installation_type | Home Assistant OS |
| dev | false |
| hassio | true |
| docker | true |
| container_arch | amd64 |
| user | root |
| virtualenv | false |
| python_version | 3.14.6 |
| os_name | Linux |
| os_version | 6.18.39-haos |
| arch | x86_64 |
| timezone | Europe/Amsterdam |
| config_dir | /config |
| logged_in | false |
|---|---|
| can_reach_cert_server | ok |
| can_reach_cloud_auth | ok |
| can_reach_cloud | ok |
| GitHub API | ok |
|---|---|
| GitHub Content | ok |
| GitHub Web | ok |
| HACS Data | ok |
| GitHub API Calls Remaining | 5000 |
| Installed Version | 2.0.5 |
| Stage | running |
| Available Repositories | 4089 |
| Downloaded Repositories | 21 |
| host_os | Home Assistant OS 18.2 |
|---|---|
| update_channel | stable |
| supervisor_version | supervisor-2026.08.0 |
| agent_version | 1.10.0 |
| docker_version | 29.6.2 |
| disk_total | 30.8 GB |
| disk_used | 20.0 GB |
| nameservers | 2a02:e040:13ff:ef00:2e3a:fdff:fe16:d125, 8.8.8.8, fdcd:154:f8f0:0:2e3a:fdff:fe16:d125 |
| healthy | true |
| supported | true |
| host_connectivity | true |
| supervisor_connectivity | true |
| ntp_synchronized | true |
| virtualization | kvm |
| board | ova |
| supervisor_api | ok |
| version_api | ok |
| installed_addons | File editor (6.1.0), AppDaemon (0.18.5), Duck DNS (2.0.0), Advanced SSH & Web Terminal (24.1.3), Node-RED (22.0.2), Mosquitto broker (7.1.0), Zigbee2mqtt (1.18.1-1), Z-Wave JS (1.7.1), pgAdmin4 (4.0.0), UniFi Network Application (5.3.0), Limited guest access (0.1.34), Samba share (12.10.0), Zigbee2mqtt Edge (edge) |
| dashboards | 3 |
|---|---|
| resources | 10 |
| views | 23 |
| mode | storage |
| adapters | lo (disabled), enp0s18 (enabled, default, auto), docker0 (disabled), hassio (disabled), vethf6ff198 (disabled), veth247a0ff (disabled), veth7cf8919 (disabled), vetha8b4636 (disabled), veth9bc718e (disabled), vetha353732 (disabled), veth37afa3a (disabled), veth1d2ded6 (disabled), veth7a5a663 (disabled) |
|---|---|
| ipv4_addresses | lo (127.0.0.1/8), enp0s18 (192.168.178.220/24), docker0 (172.30.232.1/23), hassio (172.30.32.1/23), vethf6ff198 (), veth247a0ff (), veth7cf8919 (), vetha8b4636 (), veth9bc718e (), vetha353732 (), veth37afa3a (), veth1d2ded6 (), veth7a5a663 () |
| ipv6_addresses | lo (::1/128), enp0s18 (2a02:e040:13ff:ef00:15a2:4eec:e908:ac82/64, fdcd:154:f8f0:0:f447:c5d1:7ffd:25cb/64, fe80::7208:d4fb:b531:152/64), docker0 (fd14:e94e:88a0::1/64, fe80::a41a:71ff:fe8e:d85c/64), hassio (fd0c:ac1e:2100::1/48, fe80::b8a0:36ff:fe4a:a625/64), vethf6ff198 (fe80::b434:4dff:fea8:bdac/64), veth247a0ff (fe80::a01b:10ff:fe88:d3f8/64), veth7cf8919 (fe80::5c60:8bff:fe37:8164/64), vetha8b4636 (fe80::2037:2dff:fef8:b60d/64), veth9bc718e (fe80::c090:b9ff:fe56:d5fc/64), vetha353732 (fe80::3444:6dff:feb9:9bd4/64), veth37afa3a (fe80::4883:94ff:fec7:9074/64), veth1d2ded6 (fe80::c821:f2ff:fe7a:a1f1/64), veth7a5a663 (fe80::c84b:2aff:fe91:7aad/64) |
| announce_addresses | 192.168.178.220, 2a02:e040:13ff:ef00:15a2:4eec:e908:ac82, fdcd:154:f8f0:0:f447:c5d1:7ffd:25cb, fe80::7208:d4fb:b531:152 |
| oldest_recorder_run | 21 augustus 2026 om 14:04 |
|---|---|
| current_recorder_run | 29 augustus 2026 om 11:22 |
| estimated_db_size | 2194.49 MiB |
| database_engine | sqlite |
| database_version | 3.53.2 |
| version | 3.12.2 (871119a) |
|---|---|
| cloud_online | 7 / 7 |
| local_online | 7 / 7 |
I am also checking the logs of Proxmox and found a lot of these (until I restarted):
Aug 29 09:52:13 proxmox kernel: e1000e 0000:00:19.0 eno1: Detected Hardware Unit Hang:
TDH <6d>
TDT <7a>
next_to_use <7a>
next_to_clean <6c>
buffer_info\[next_to_clean\]:
time_stamp <10038b2f4>
next_to_watch <6d>
jiffies <102916f80>
next_to_watch.status <0>
MAC Status <40080083>
PHY Status <796d>
PHY 1000BASE-T Status <3800>
PHY Extended Status <3000>
PCI Status <10>
Some additional details:
root@proxmox:~# ethtool eno1
Settings for eno1:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Link partner advertised pause frame use: Symmetric Receive-only
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 1000Mb/s
Duplex: Full
Auto-negotiation: on
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
MDI-X: on (auto)
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
root@proxmox:~# ethtool -S eno1
NIC statistics:
rx_packets: 272277
tx_packets: 76192
rx_bytes: 345627825
tx_bytes: 28563862
rx_broadcast: 4502
tx_broadcast: 166
rx_multicast: 10633
tx_multicast: 130
rx_errors: 0
tx_errors: 0
tx_dropped: 0
multicast: 10633
collisions: 0
rx_length_errors: 0
rx_over_errors: 0
rx_crc_errors: 0
rx_frame_errors: 0
rx_no_buffer_count: 0
rx_missed_errors: 0
tx_aborted_errors: 0
tx_carrier_errors: 0
tx_fifo_errors: 0
tx_heartbeat_errors: 0
tx_window_errors: 0
tx_abort_late_coll: 0
tx_deferred_ok: 0
tx_single_coll_ok: 0
tx_multi_coll_ok: 0
tx_timeout_count: 0
tx_restart_queue: 0
rx_long_length_errors: 0
rx_short_length_errors: 0
rx_align_errors: 0
tx_tcp_seg_good: 2589
tx_tcp_seg_failed: 0
rx_flow_control_xon: 0
rx_flow_control_xoff: 0
tx_flow_control_xon: 0
tx_flow_control_xoff: 0
rx_csum_offload_good: 269277
rx_csum_offload_errors: 0
rx_header_split: 0
alloc_rx_buff_failed: 0
tx_smbus: 0
rx_smbus: 0
dropped_smbus: 0
rx_dma_failed: 0
tx_dma_failed: 0
rx_hwtstamp_cleared: 0
uncorr_ecc_errors: 0
corr_ecc_errors: 0
tx_hwtstamp_timeouts: 0
tx_hwtstamp_skipped: 0
Seems to be a Very Known issue ( And old )
A simple google Search for
e1000e 0000:00:19.0 eno1: Detected Hardware Unit Hang:
Have you tried this “fix/workaround” ?
@rednas
use
Just did it:
_ ____________ ____ __________ ___ ____ _ __ __
/ | / / _/ ____/ / __ \/ __/ __/ /___ ____ _____/ (_)___ ____ _ / __ \(_)________ _/ /_ / /__ _____
/ |/ // // / / / / / /_/ /_/ / __ \/ __ `/ __ / / __ \/ __ `/ / / / / / ___/ __ `/ __ \/ / _ \/ ___/
/ /| // // /___ / /_/ / __/ __/ / /_/ / /_/ / /_/ / / / / / /_/ / / /_/ / (__ ) /_/ / /_/ / / __/ /
/_/ |_/___/\____/ \____/_/ /_/ /_/\____/\__,_/\__,_/_/_/ /_/\__, / /_____/_/____/\__,_/_.___/_/\___/_/
/____/
Enhanced version supporting both e1000e and e1000 drivers
ℹ️ Searching for Intel e1000e and e1000 interfaces...
✔️ Found 1 Intel e1000e/e1000 interfaces
✔️ Selected interface: eno1 (e1000e)
ℹ️ Creating systemd service for interface: eno1 (e1000e)...
✔️ Service for eno1 (e1000e) created and enabled!
ℹ️ Service: disable-nic-offload-eno1.service...
ℹ️ Status: Active...
ℹ️ Start on boot: Enabled...
✔️ Intel e1000e/e1000 optimization complete for 1 interface(s)!
ℹ️ Verification commands:...
ethtool -k eno1 # Check offloading status
systemctl status disable-nic-offload-eno1.service # Check service status
Verification:
root@proxmox:~# ethtool -k eno1
Features for eno1:
rx-checksumming: off
tx-checksumming: off
tx-checksum-ipv4: off [fixed]
tx-checksum-ip-generic: off
tx-checksum-ipv6: off [fixed]
tx-checksum-fcoe-crc: off [fixed]
tx-checksum-sctp: off [fixed]
scatter-gather: off
tx-scatter-gather: off
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: off
tx-vlan-offload: off
ntuple-filters: off [fixed]
receive-hashing: on
highdma: on [fixed]
rx-vlan-filter: off [fixed]
vlan-challenged: off [fixed]
tx-lockless: off [fixed]
netns-local: 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]
fcoe-mtu: 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]
root@proxmox:~# systemctl status disable-nic-offload-eno1.service
● disable-nic-offload-eno1.service - Disable NIC offloading for Intel e1000e interface eno1
Loaded: loaded (/etc/systemd/system/disable-nic-offload-eno1.service; enabled; preset: enabled)
Active: active (exited) since Sat 2026-08-29 11:58:11 CEST; 3min 0s ago
Main PID: 8398 (code=exited, status=0/SUCCESS)
CPU: 22ms
Aug 29 11:58:10 proxmox systemd[1]: Starting disable-nic-offload-eno1.service - Disable NIC offloading for Intel e10>
Aug 29 11:58:11 proxmox systemd[1]: Finished disable-nic-offload-eno1.service - Disable NIC offloading for Intel e10>
lines 1-8/8 (END)
From the log:
Aug 29 11:58:10 proxmox systemd\[1\]: Reloading.
Aug 29 11:58:10 proxmox systemd\[1\]: Starting disable-nic-offload-eno1.service - Disable NIC offloading for Intel e1000e interface eno1...
Aug 29 11:58:11 proxmox kernel: vmbr0: port 1(eno1) entered disabled state
Aug 29 11:58:11 proxmox systemd\[1\]: Finished disable-nic-offload-eno1.service - Disable NIC offloading for Intel e1000e interface eno1.
Aug 29 11:58:11 proxmox systemd\[1\]: Reloading.
Aug 29 11:58:14 proxmox kernel: e1000e 0000:00:19.0 eno1: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Aug 29 11:58:14 proxmox kernel: vmbr0: port 1(eno1) entered blocking state
Aug 29 11:58:14 proxmox kernel: vmbr0: port 1(eno1) entered forwarding state
Now we need some time I guess….
It froze again..
However, I don’t see the same issue as before. Any clue what it could be? I have added the proxmox log for about the last 12 hours.
Aug 29 22:34:14 proxmox pveproxy[90318]: worker exit
Aug 29 22:34:14 proxmox pveproxy[914]: worker 90318 finished
Aug 29 22:34:14 proxmox pveproxy[914]: starting 1 worker(s)
Aug 29 22:34:14 proxmox pveproxy[914]: worker 120232 started
Aug 29 22:50:23 proxmox smartd[556]: Device: /dev/sda [SAT], 3 Currently unreadable (pending) sectors
Aug 29 22:55:23 proxmox pvedaemon[83809]: <***> successful auth for user '***'
Aug 29 23:17:01 proxmox CRON[127671]: pam_unix(cron:session): session opened for user ***(uid=0) by (uid=0)
Aug 29 23:17:01 proxmox CRON[127672]: (***) CMD (cd / && run-parts --report /etc/cron.hourly)
Aug 29 23:17:01 proxmox CRON[127671]: pam_unix(cron:session): session closed for user ***
Aug 29 23:20:23 proxmox smartd[556]: Device: /dev/sda [SAT], 3 Currently unreadable (pending) sectors
Aug 29 23:50:24 proxmox smartd[556]: Device: /dev/sda [SAT], 3 Currently unreadable (pending) sectors
Aug 29 23:50:24 proxmox pveproxy[93866]: worker exit
Aug 29 23:50:24 proxmox pveproxy[914]: worker 93866 finished
Aug 29 23:50:24 proxmox pveproxy[914]: starting 1 worker(s)
Aug 29 23:50:24 proxmox pveproxy[914]: worker 133461 started
Aug 29 23:55:24 proxmox pvedaemon[92354]: <***> successful auth for user '***'
Aug 30 00:00:29 proxmox systemd[1]: Starting dpkg-db-backup.service - Daily dpkg database backup service...
Aug 30 00:00:29 proxmox systemd[1]: Starting logrotate.service - Rotate log files...
Aug 30 00:00:29 proxmox systemd[1]: dpkg-db-backup.service: Deactivated successfully.
Aug 30 00:00:29 proxmox systemd[1]: Finished dpkg-db-backup.service - Daily dpkg database backup service.
Aug 30 00:00:30 proxmox systemd[1]: Reloading pveproxy.service - PVE API Proxy Server...
Aug 30 00:00:32 proxmox pveproxy[135257]: send HUP to 914
Aug 30 00:00:32 proxmox pveproxy[914]: received signal HUP
Aug 30 00:00:32 proxmox pveproxy[914]: server closing
Aug 30 00:00:32 proxmox pveproxy[914]: server shutdown (restart)
Aug 30 00:00:32 proxmox systemd[1]: Reloaded pveproxy.service - PVE API Proxy Server.
Aug 30 00:00:32 proxmox systemd[1]: Reloading spiceproxy.service - PVE SPICE Proxy Server...
Aug 30 00:00:32 proxmox spiceproxy[135262]: send HUP to 919
Aug 30 00:00:32 proxmox spiceproxy[919]: received signal HUP
Aug 30 00:00:32 proxmox spiceproxy[919]: server closing
Aug 30 00:00:32 proxmox spiceproxy[919]: server shutdown (restart)
Aug 30 00:00:32 proxmox systemd[1]: Reloaded spiceproxy.service - PVE SPICE Proxy Server.
Aug 30 00:00:32 proxmox pvefw-logger[530]: received terminate request (signal)
Aug 30 00:00:32 proxmox systemd[1]: Stopping pvefw-logger.service - Proxmox VE firewall logger...
Aug 30 00:00:32 proxmox pvefw-logger[530]: stopping pvefw logger
Aug 30 00:00:33 proxmox systemd[1]: pvefw-logger.service: Deactivated successfully.
Aug 30 00:00:33 proxmox systemd[1]: Stopped pvefw-logger.service - Proxmox VE firewall logger.
Aug 30 00:00:33 proxmox systemd[1]: pvefw-logger.service: Consumed 5.948s CPU time.
Aug 30 00:00:33 proxmox systemd[1]: Starting pvefw-logger.service - Proxmox VE firewall logger...
Aug 30 00:00:33 proxmox pvefw-logger[135272]: starting pvefw logger
Aug 30 00:00:33 proxmox systemd[1]: Started pvefw-logger.service - Proxmox VE firewall logger.
Aug 30 00:00:33 proxmox systemd[1]: logrotate.service: Deactivated successfully.
Aug 30 00:00:33 proxmox systemd[1]: Finished logrotate.service - Rotate log files.
Aug 30 00:00:33 proxmox spiceproxy[919]: restarting server
Aug 30 00:00:33 proxmox spiceproxy[919]: starting 1 worker(s)
Aug 30 00:00:33 proxmox spiceproxy[919]: worker 135276 started
Aug 30 00:00:34 proxmox pveproxy[914]: restarting server
Aug 30 00:00:34 proxmox pveproxy[914]: starting 3 worker(s)
Aug 30 00:00:34 proxmox pveproxy[914]: worker 135277 started
Aug 30 00:00:34 proxmox pveproxy[914]: worker 135278 started
Aug 30 00:00:34 proxmox pveproxy[914]: worker 135279 started
Aug 30 00:00:38 proxmox spiceproxy[920]: worker exit
Aug 30 00:00:38 proxmox spiceproxy[919]: worker 920 finished
Aug 30 00:00:39 proxmox pveproxy[120232]: worker exit
Aug 30 00:00:39 proxmox pveproxy[107515]: worker exit
Aug 30 00:00:39 proxmox pveproxy[133461]: worker exit
Aug 30 00:00:39 proxmox pveproxy[914]: worker 107515 finished
Aug 30 00:00:39 proxmox pveproxy[914]: worker 133461 finished
Aug 30 00:00:39 proxmox pveproxy[914]: worker 120232 finished
Aug 30 00:17:01 proxmox CRON[138117]: pam_unix(cron:session): session opened for user ***(uid=0) by (uid=0)
Aug 30 00:17:01 proxmox CRON[138118]: (***) CMD (cd / && run-parts --report /etc/cron.hourly)
Aug 30 00:17:01 proxmox CRON[138117]: pam_unix(cron:session): session closed for user ***
Aug 30 00:20:23 proxmox smartd[556]: Device: /dev/sda [SAT], 3 Currently unreadable (pending) sectors
Aug 30 00:50:23 proxmox smartd[556]: Device: /dev/sda [SAT], 3 Currently unreadable (pending) sectors
Aug 30 00:56:14 proxmox pvedaemon[83809]: <***> successful auth for user '***'
Aug 30 01:17:01 proxmox CRON[148452]: pam_unix(cron:session): session opened for user ***(uid=0) by (uid=0)
Aug 30 01:17:01 proxmox CRON[148453]: (***) CMD (cd / && run-parts --report /etc/cron.hourly)
Aug 30 01:17:01 proxmox CRON[148452]: pam_unix(cron:session): session closed for user ***
Aug 30 01:20:23 proxmox smartd[556]: Device: /dev/sda [SAT], 3 Currently unreadable (pending) sectors
Aug 30 01:50:23 proxmox smartd[556]: Device: /dev/sda [SAT], 3 Currently unreadable (pending) sectors
Aug 30 01:56:14 proxmox pvedaemon[83640]: <***> successful auth for user '***'
Aug 30 01:56:14 proxmox pvedaemon[92354]: <***> successful auth for user '***'
Aug 30 02:17:01 proxmox CRON[158809]: pam_unix(cron:session): session opened for user ***(uid=0) by (uid=0)
Aug 30 02:17:01 proxmox CRON[158810]: (***) CMD (cd / && run-parts --report /etc/cron.hourly)
Aug 30 02:17:01 proxmox CRON[158809]: pam_unix(cron:session): session closed for user ***
Aug 30 02:20:23 proxmox smartd[556]: Device: /dev/sda [SAT], 3 Currently unreadable (pending) sectors
Aug 30 02:38:15 proxmox pvedaemon[83809]: worker exit
Aug 30 02:38:15 proxmox pvedaemon[904]: worker 83809 finished
Aug 30 02:38:15 proxmox pvedaemon[904]: starting 1 worker(s)
Aug 30 02:38:15 proxmox pvedaemon[904]: worker 162451 started
Aug 30 02:40:15 proxmox pvedaemon[83640]: worker exit
Aug 30 02:40:15 proxmox pvedaemon[904]: worker 83640 finished
Aug 30 02:40:15 proxmox pvedaemon[904]: starting 1 worker(s)
Aug 30 02:40:15 proxmox pvedaemon[904]: worker 162799 started
Aug 30 02:50:23 proxmox smartd[556]: Device: /dev/sda [SAT], 3 Currently unreadable (pending) sectors
Aug 30 02:56:15 proxmox pvedaemon[162451]: <***> successful auth for user '***'
Aug 30 02:56:15 proxmox pvedaemon[162799]: <***> successful auth for user '***'
Aug 30 02:56:15 proxmox pvedaemon[162799]: <***> successful auth for user '***'
Aug 30 03:02:14 proxmox pveproxy[135279]: worker exit
Aug 30 03:02:14 proxmox pveproxy[914]: worker 135279 finished
Aug 30 03:02:14 proxmox pveproxy[914]: starting 1 worker(s)
Aug 30 03:02:14 proxmox pveproxy[914]: worker 166608 started
Aug 30 03:02:26 proxmox pveproxy[135277]: worker exit
Aug 30 03:02:26 proxmox pveproxy[914]: worker 135277 finished
Aug 30 03:02:26 proxmox pveproxy[914]: starting 1 worker(s)
Aug 30 03:02:26 proxmox pveproxy[914]: worker 166640 started
Aug 30 03:10:01 proxmox CRON[167958]: pam_unix(cron:session): session opened for user ***(uid=0) by (uid=0)
Aug 30 03:10:01 proxmox CRON[167959]: (***) CMD (test -e /run/systemd/system || SERVICE_MODE=1 /sbin/e2scrub_all -A -r)
Aug 30 03:10:01 proxmox CRON[167958]: pam_unix(cron:session): session closed for user ***
Aug 30 03:11:29 proxmox systemd[1]: Starting e2scrub_all.service - Online ext4 Metadata Check for All Filesystems...
Aug 30 03:11:29 proxmox systemd[1]: e2scrub_all.service: Deactivated successfully.
Aug 30 03:11:29 proxmox systemd[1]: Finished e2scrub_all.service - Online ext4 Metadata Check for All Filesystems.
Aug 30 03:17:01 proxmox CRON[169178]: pam_unix(cron:session): session opened for user ***(uid=0) by (uid=0)
Aug 30 03:17:01 proxmox CRON[169179]: (***) CMD (cd / && run-parts --report /etc/cron.hourly)
Aug 30 03:17:01 proxmox CRON[169178]: pam_unix(cron:session): session closed for user ***
Aug 30 03:20:23 proxmox smartd[556]: Device: /dev/sda [SAT], 3 Currently unreadable (pending) sectors
Aug 30 03:30:01 proxmox CRON[171428]: pam_unix(cron:session): session opened for user ***(uid=0) by (uid=0)
Aug 30 03:30:01 proxmox CRON[171429]: (***) CMD (test -e /run/systemd/system || SERVICE_MODE=1 /usr/lib/x86_64-linux-gnu/e2fsprogs/e2scrub_all_cron)
Aug 30 03:30:01 proxmox CRON[171428]: pam_unix(cron:session): session closed for user ***
Aug 30 03:50:23 proxmox smartd[556]: Device: /dev/sda [SAT], 3 Currently unreadable (pending) sectors
Aug 30 03:54:29 proxmox systemd[1]: Starting pve-daily-update.service - Daily PVE download activities...
Aug 30 03:54:31 proxmox pveupdate[175647]: <***> starting task UPID:proxmox:0002AE3E:005B0709:6A938D57:aptupdate::***:
Aug 30 03:54:33 proxmox pveupdate[175678]: update new package list: /var/lib/pve-manager/pkgupdates
Aug 30 03:54:37 proxmox pveupdate[175647]: <***> end task UPID:proxmox:0002AE3E:005B0709:6A938D57:aptupdate::***: OK
Aug 30 03:54:37 proxmox systemd[1]: pve-daily-update.service: Deactivated successfully.
Aug 30 03:54:37 proxmox systemd[1]: Finished pve-daily-update.service - Daily PVE download activities.
Aug 30 03:54:37 proxmox systemd[1]: pve-daily-update.service: Consumed 7.502s CPU time.
Aug 30 03:56:29 proxmox pvedaemon[162799]: <***> successful auth for user '***'
Aug 30 04:04:15 proxmox pveproxy[135278]: worker exit
Aug 30 04:04:15 proxmox pveproxy[914]: worker 135278 finished
Aug 30 04:04:15 proxmox pveproxy[914]: starting 1 worker(s)
Aug 30 04:04:15 proxmox pveproxy[914]: worker 177752 started
Aug 30 04:17:01 proxmox CRON[180320]: pam_unix(cron:session): session opened for user ***(uid=0) by (uid=0)
Aug 30 04:17:01 proxmox CRON[180321]: (***) CMD (cd / && run-parts --report /etc/cron.hourly)
Aug 30 04:17:01 proxmox CRON[180320]: pam_unix(cron:session): session closed for user ***
Aug 30 04:20:23 proxmox smartd[556]: Device: /dev/sda [SAT], 3 Currently unreadable (pending) sectors
Aug 30 04:34:33 proxmox pvedaemon[92354]: worker exit
Aug 30 04:34:33 proxmox pvedaemon[904]: worker 92354 finished
Aug 30 04:34:33 proxmox pvedaemon[904]: starting 1 worker(s)
Aug 30 04:34:33 proxmox pvedaemon[904]: worker 183336 started
Aug 30 04:50:23 proxmox smartd[556]: Device: /dev/sda [SAT], 3 Currently unreadable (pending) sectors
Aug 30 04:56:32 proxmox pvedaemon[183336]: <***> successful auth for user '***'
Aug 30 05:17:01 proxmox CRON[190684]: pam_unix(cron:session): session opened for user ***(uid=0) by (uid=0)
Aug 30 05:17:01 proxmox CRON[190685]: (***) CMD (cd / && run-parts --report /etc/cron.hourly)
Aug 30 05:17:01 proxmox CRON[190684]: pam_unix(cron:session): session closed for user ***
Aug 30 05:20:23 proxmox smartd[556]: Device: /dev/sda [SAT], 3 Currently unreadable (pending) sectors
Aug 30 05:50:23 proxmox smartd[556]: Device: /dev/sda [SAT], 3 Currently unreadable (pending) sectors
Aug 30 05:56:34 proxmox pvedaemon[183336]: <***> successful auth for user '***'
Aug 30 05:58:15 proxmox pveproxy[914]: worker 166608 finished
Aug 30 05:58:15 proxmox pveproxy[914]: starting 1 worker(s)
Aug 30 05:58:15 proxmox pveproxy[914]: worker 197775 started
Aug 30 05:58:19 proxmox pveproxy[197774]: got inotify poll request in wrong process - disabling inotify
Aug 30 05:58:20 proxmox pveproxy[197774]: worker exit
Aug 30 06:17:01 proxmox CRON[201019]: pam_unix(cron:session): session opened for user ***(uid=0) by (uid=0)
Aug 30 06:17:01 proxmox CRON[201020]: (***) CMD (cd / && run-parts --report /etc/cron.hourly)
Aug 30 06:17:01 proxmox CRON[201019]: pam_unix(cron:session): session closed for user ***
Aug 30 06:20:23 proxmox smartd[556]: Device: /dev/sda [SAT], 3 Currently unreadable (pending) sectors
Aug 30 06:25:01 proxmox CRON[202394]: pam_unix(cron:session): session opened for user ***(uid=0) by (uid=0)
Aug 30 06:25:01 proxmox CRON[202395]: (***) CMD (test -x /usr/sbin/anacron || { cd / && run-parts --report /etc/cron.daily; })
Aug 30 06:25:01 proxmox CRON[202394]: pam_unix(cron:session): session closed for user ***
Aug 30 06:25:15 proxmox pveproxy[166640]: worker exit
Aug 30 06:25:15 proxmox pveproxy[914]: worker 166640 finished
Aug 30 06:25:15 proxmox pveproxy[914]: starting 1 worker(s)
Aug 30 06:25:15 proxmox pveproxy[914]: worker 202436 started
Aug 30 06:30:29 proxmox systemd[1]: Starting apt-daily-upgrade.service - Daily apt upgrade and clean activities...
Aug 30 06:30:30 proxmox systemd[1]: apt-daily-upgrade.service: Deactivated successfully.
Aug 30 06:30:30 proxmox systemd[1]: Finished apt-daily-upgrade.service - Daily apt upgrade and clean activities.
Aug 30 06:47:01 proxmox CRON[206230]: pam_unix(cron:session): session opened for user ***(uid=0) by (uid=0)
Aug 30 06:47:01 proxmox CRON[206231]: (***) CMD (test -x /usr/sbin/anacron || { cd / && run-parts --report /etc/cron.weekly; })
Aug 30 06:47:01 proxmox CRON[206230]: pam_unix(cron:session): session closed for user ***
Aug 30 06:50:23 proxmox smartd[556]: Device: /dev/sda [SAT], 3 Currently unreadable (pending) sectors
Aug 30 06:56:35 proxmox pvedaemon[162799]: <***> successful auth for user '***'
Aug 30 07:17:01 proxmox CRON[211386]: pam_unix(cron:session): session opened for user ***(uid=0) by (uid=0)
Aug 30 07:17:01 proxmox CRON[211387]: (***) CMD (cd / && run-parts --report /etc/cron.hourly)
Aug 30 07:17:01 proxmox CRON[211386]: pam_unix(cron:session): session closed for user ***
Aug 30 07:20:23 proxmox smartd[556]: Device: /dev/sda [SAT], 3 Currently unreadable (pending) sectors
Aug 30 07:40:14 proxmox pveproxy[177752]: worker exit
Aug 30 07:40:14 proxmox pveproxy[914]: worker 177752 finished
Aug 30 07:40:14 proxmox pveproxy[914]: starting 1 worker(s)
Aug 30 07:40:14 proxmox pveproxy[914]: worker 215435 started
Aug 30 07:50:23 proxmox smartd[556]: Device: /dev/sda [SAT], 3 Currently unreadable (pending) sectors
Aug 30 07:56:38 proxmox pvedaemon[183336]: <***> successful auth for user '***'
Aug 30 08:12:00 proxmox kernel: perf: interrupt took too long (4986 > 4935), lowering kernel.perf_event_max_sample_rate to 40000
Aug 30 08:17:01 proxmox CRON[221834]: pam_unix(cron:session): session opened for user ***(uid=0) by (uid=0)
Aug 30 08:17:01 proxmox CRON[221835]: (***) CMD (cd / && run-parts --report /etc/cron.hourly)
Aug 30 08:17:01 proxmox CRON[221834]: pam_unix(cron:session): session closed for user ***
Aug 30 08:20:23 proxmox smartd[556]: Device: /dev/sda [SAT], 3 Currently unreadable (pending) sectors
Aug 30 08:50:23 proxmox smartd[556]: Device: /dev/sda [SAT], 3 Currently unreadable (pending) sectors
Aug 30 08:55:15 proxmox pveproxy[197775]: worker exit
Aug 30 08:55:15 proxmox pveproxy[914]: worker 197775 finished
Aug 30 08:55:15 proxmox pveproxy[914]: starting 1 worker(s)
Aug 30 08:55:15 proxmox pveproxy[914]: worker 228463 started
Aug 30 08:56:41 proxmox pvedaemon[162799]: <***> successful auth for user '***'
Aug 30 09:08:29 proxmox systemd[1]: Starting apt-daily.service - Daily apt download activities...
Aug 30 09:08:30 proxmox systemd[1]: apt-daily.service: Deactivated successfully.
Aug 30 09:08:30 proxmox systemd[1]: Finished apt-daily.service - Daily apt download activities.
Aug 30 09:17:01 proxmox CRON[232305]: pam_unix(cron:session): session opened for user ***(uid=0) by (uid=0)
Aug 30 09:17:01 proxmox CRON[232306]: (***) CMD (cd / && run-parts --report /etc/cron.hourly)
Aug 30 09:17:01 proxmox CRON[232305]: pam_unix(cron:session): session closed for user ***
Aug 30 09:20:23 proxmox smartd[556]: Device: /dev/sda [SAT], 3 Currently unreadable (pending) sectors
Aug 30 09:47:14 proxmox pveproxy[202436]: worker exit
Aug 30 09:47:14 proxmox pveproxy[914]: worker 202436 finished
Aug 30 09:47:14 proxmox pveproxy[914]: starting 1 worker(s)
Aug 30 09:47:14 proxmox pveproxy[914]: worker 237614 started
Aug 30 09:50:23 proxmox smartd[556]: Device: /dev/sda [SAT], 3 Currently unreadable (pending) sectors
Aug 30 09:56:42 proxmox pvedaemon[162799]: <***> successful auth for user '***'
Aug 30 10:13:14 proxmox pvedaemon[162451]: worker exit
Aug 30 10:13:14 proxmox pvedaemon[904]: worker 162451 finished
Aug 30 10:13:14 proxmox pvedaemon[904]: starting 1 worker(s)
Aug 30 10:13:14 proxmox pvedaemon[904]: worker 242199 started
Aug 30 10:17:01 proxmox CRON[242872]: pam_unix(cron:session): session opened for user ***(uid=0) by (uid=0)
Aug 30 10:17:01 proxmox CRON[242873]: (***) CMD (cd / && run-parts --report /etc/cron.hourly)
Aug 30 10:17:01 proxmox CRON[242872]: pam_unix(cron:session): session closed for user ***
Aug 30 10:20:23 proxmox smartd[556]: Device: /dev/sda [SAT], 3 Currently unreadable (pending) sectors
Aug 30 10:44:43 proxmox pvedaemon[162799]: worker exit
Aug 30 10:44:43 proxmox pvedaemon[904]: worker 162799 finished
Aug 30 10:44:43 proxmox pvedaemon[904]: starting 1 worker(s)
Aug 30 10:44:43 proxmox pvedaemon[904]: worker 247868 started
Aug 30 10:50:23 proxmox smartd[556]: Device: /dev/sda [SAT], 3 Currently unreadable (pending) sectors
Aug 30 10:56:29 proxmox systemd[1]: Starting man-db.service - Daily man-db regeneration...
Aug 30 10:56:30 proxmox systemd[1]: man-db.service: Deactivated successfully.
Aug 30 10:56:30 proxmox systemd[1]: Finished man-db.service - Daily man-db regeneration.
Aug 30 10:56:42 proxmox pvedaemon[242199]: <***> successful auth for user '***'
Aug 30 11:16:43 proxmox pveproxy[215435]: worker exit
Aug 30 11:16:43 proxmox pveproxy[914]: worker 215435 finished
Aug 30 11:16:43 proxmox pveproxy[914]: starting 1 worker(s)
Aug 30 11:16:43 proxmox pveproxy[914]: worker 253470 started
Aug 30 11:17:01 proxmox CRON[253522]: pam_unix(cron:session): session opened for user ***(uid=0) by (uid=0)
Aug 30 11:17:01 proxmox CRON[253523]: (***) CMD (cd / && run-parts --report /etc/cron.hourly)
Aug 30 11:17:01 proxmox CRON[253522]: pam_unix(cron:session): session closed for user ***
Aug 30 11:20:23 proxmox smartd[556]: Device: /dev/sda [SAT], 3 Currently unreadable (pending) sectors
Aug 30 11:25:14 proxmox systemd-logind[563]: Power key pressed short.
Aug 30 11:25:14 proxmox systemd-logind[563]: Powering off...
Aug 30 11:25:14 proxmox systemd-logind[563]: System is powering down.
How many vCPU’s, RAM, diskspace have you assigned to HA?
Are you running other VM/LXC’s and are those fine?
You could just have tried
ethtool -K eno1 tso off
2, 6GB, 32GB.
No, but once Proxmox becomes unresponsive, HA becomes unresponsive as well.
However, I also have a Synology NAS with DDNS that also sent a message that the connection was lost at 10:45 and reconnected at 11:43.
I will keep monitoring it
Would this be the cause? It seems to repeat.
Is it time to look at new hardware, and get any backups onto somewhere where you can restore from them, and verify they are actually intact?
How is it performing now?
any updates?
I guess its solved then.