Ich nutze erst seit wenigen Monaten Proxmox auf einem MiniPC.
- Glovary Mini Quad Core N100, DDR5, x 2.5GbE i226V LAN Fanless
- RAM Crucial DDR5 RAM 32GB 4800MHz SODIMM
- Western Digital Black SN770 int. M.2
Und hatte bis letzten Sonntag keine Probleme weder mit dem hier im Forum immer erwähnten e100 Bug oder sonstwas. Energiesparmodus habe ich deaktiviert … dachte ich zumindest 
Was war passiert?
- HA stürzte Nachts ab → Heizung blieb gesenkt → Frau beim Aufstehen um 7 Uhr angesäuert → Notfall eHeizkörper angeworfen → MiniPC vom Strom getrennt und wieder angeschaltet → alles lief wieder
- Ich ärgere mich etwas, daß ich nicht vorher noch geschaut hatte ob ich überhaupt noch auf Proxmox gekommen wäre
Einige meiner Analyseschritte
Wie auch immer, später nahm ich mir die Zeit mich in Analysebefehlen zu üben, auch Neuland für mich. Ich habe viel mehr probiert als hier geschrieben.
- HA hörte am
15.02.2026 um 2:10 Uhrauf zu arbeiten, laut Aktivitätsprotokoll.
Es gab kein Auffälligkeiten seitens Temperaturen, CPU Last, RAM Auslastung → alles normal
- HA Supervisor Logs
2026-02-15 00:17:40.485 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
2026-02-15 00:41:24.929 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state running
2026-02-15 00:41:24.929 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_failed/dns_server
2026-02-15 00:41:24.951 INFO (MainThread) [supervisor.resolution.checks.base] Run check for pwned/addon
2026-02-15 00:41:24.951 INFO (MainThread) [supervisor.resolution.checks.base] Run check for free_space/system
2026-02-15 00:41:24.952 INFO (MainThread) [supervisor.resolution.checks.base] Run check for disk_lifetime/system
2026-02-15 00:41:24.953 INFO (MainThread) [supervisor.resolution.checks.base] Run check for docker_config/system
2026-02-15 00:41:24.953 INFO (MainThread) [supervisor.resolution.checks.base] Run check for disabled_data_disk/system
2026-02-15 00:41:24.953 INFO (MainThread) [supervisor.resolution.checks.base] Run check for multiple_data_disks/system
2026-02-15 00:41:24.953 INFO (MainThread) [supervisor.resolution.checks.base] Run check for ipv4_connection_problem/system
2026-02-15 00:41:24.953 INFO (MainThread) [supervisor.resolution.checks.base] Run check for security/core
2026-02-15 00:41:24.953 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_ipv6_error/dns_server
2026-02-15 00:41:24.954 INFO (MainThread) [supervisor.resolution.check] System checks complete
2026-02-15 00:41:24.954 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
2026-02-15 00:41:24.991 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
2026-02-15 00:41:24.991 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state running
2026-02-15 00:41:24.991 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
2026-02-15 00:43:22.319 INFO (MainThread) [supervisor.store.git] Update add-on /data/addons/git/a0d7b954 repository from https://github.com/hassio-addons/repository
2026-02-15 00:43:22.319 INFO (MainThread) [supervisor.store.git] Update add-on /data/addons/git/5c53de3b repository from https://github.com/esphome/home-assistant-addon
2026-02-15 00:43:22.322 INFO (MainThread) [supervisor.store.git] Update add-on /data/addons/core repository from https://github.com/home-assistant/addons
2026-02-15 00:43:22.322 INFO (MainThread) [supervisor.store.git] Update add-on /data/addons/git/d5369777 repository from https://github.com/music-assistant/home-assistant-addon
2026-02-15 00:43:22.326 INFO (MainThread) [supervisor.store.git] Update add-on /data/addons/git/b9845f46 repository from https://github.com/wez/govee2mqtt
2026-02-15 00:43:22.328 INFO (MainThread) [supervisor.store.git] Update add-on /data/addons/git/45df7312 repository from https://github.com/zigbee2mqtt/hassio-zigbee2mqtt
2026-02-15 00:43:22.330 INFO (MainThread) [supervisor.store.git] Update add-on /data/addons/git/db21ed7f repository from https://github.com/alexbelgium/hassio-addons
2026-02-15 00:43:22.330 INFO (MainThread) [supervisor.store.git] Update add-on /data/addons/git/37bb974a repository from https://github.com/thomasmauerer/hassio-addons/
2026-02-15 00:43:23.455 WARNING (SyncWorker_5) [supervisor.addons.validate] Add-on 'Grocy' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer.
2026-02-15 00:43:23.456 WARNING (SyncWorker_5) [supervisor.addons.validate] Add-on 'Log Viewer' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer.
2026-02-15 00:43:23.458 WARNING (SyncWorker_5) [supervisor.addons.validate] Add-on 'Traccar' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer.
2026-02-15 00:43:23.481 WARNING (SyncWorker_5) [supervisor.addons.validate] Add-on 'Glances' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer.
2026-02-15 00:43:23.488 WARNING (SyncWorker_5) [supervisor.addons.validate] Add-on 'InfluxDB' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer.
2026-02-15 00:43:23.489 WARNING (SyncWorker_5) [supervisor.addons.validate] Add-on 'Folding@home' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer.
2026-02-15 00:43:23.493 WARNING (SyncWorker_5) [supervisor.addons.validate] Add-on 'Overseerr' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer.
2026-02-15 00:43:23.495 WARNING (SyncWorker_5) [supervisor.addons.validate] Add-on 'MQTT IO' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer.
2026-02-15 00:43:23.501 WARNING (SyncWorker_5) [supervisor.addons.validate] Add-on 'Nginx Proxy Manager' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer.
2026-02-15 00:43:23.532 INFO (MainThread) [supervisor.store] Loading add-ons from store: 200 all - 0 new - 0 remove
2026-02-15 00:47:44.626 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
2026-02-15 01:17:48.736 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token !!!!!!!!!!!!!! Absturzzeit ?
2026-02-15 01:41:24.994 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state running
2026-02-15 01:41:24.994 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_failed/dns_server
2026-02-15 01:41:25.017 INFO (MainThread) [supervisor.resolution.checks.base] Run check for pwned/addon
2026-02-15 01:41:25.018 INFO (MainThread) [supervisor.resolution.checks.base] Run check for free_space/system
2026-02-15 01:41:25.018 INFO (MainThread) [supervisor.resolution.checks.base] Run check for disk_lifetime/system
2026-02-15 01:41:25.019 INFO (MainThread) [supervisor.resolution.checks.base] Run check for docker_config/system
2026-02-15 01:41:25.019 INFO (MainThread) [supervisor.resolution.checks.base] Run check for disabled_data_disk/system
2026-02-15 01:41:25.019 INFO (MainThread) [supervisor.resolution.checks.base] Run check for multiple_data_disks/system
2026-02-15 01:41:25.020 INFO (MainThread) [supervisor.resolution.checks.base] Run check for ipv4_connection_problem/system
2026-02-15 01:41:25.020 INFO (MainThread) [supervisor.resolution.checks.base] Run check for security/core
2026-02-15 01:41:25.020 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_ipv6_error/dns_server
2026-02-15 01:41:25.020 INFO (MainThread) [supervisor.resolution.check] System checks complete
2026-02-15 01:41:25.020 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
2026-02-15 01:41:25.057 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
2026-02-15 01:41:25.057 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state running
2026-02-15 01:41:25.058 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
2026-02-15 01:43:11.535 INFO (MainThread) [supervisor.backups.manager] Found 41 backup files
2026-02-15 01:47:52.866 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
2026-02-15 01:49:56.029 INFO (MainThread) [supervisor.host.info] Updating local host information
2026-02-15 01:49:56.391 INFO (MainThread) [supervisor.host.services] Updating service information
2026-02-15 01:49:56.394 INFO (MainThread) [supervisor.host.network] Updating local network information
2026-02-15 01:49:56.449 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
2026-02-15 01:49:56.452 INFO (MainThread) [supervisor.host.manager] Host information reload completed
Sieht für mich alles normal aus, nichts was auf einen Crash hindeutet.
- Im PVE System Logfiles stand
Feb 15 00:09:14 pve pveproxy... received signal HUP ... restart
...
Feb 15 00:09:14 pve systemd... Reloading spiceproxy...
...
Feb 15 00:09:14 pve pvefw-logger... stopping ... starting ...
Feb 15 00:09:15 ... logrotate finished
Alles normale Wartungssachen → kein Hinweis auf einen Crash
journalctl --list-boots
-2 ... Wed 2026-02-11 15:05:10 CET -> Sun 2026-02-15 01:17:01 CET
-1 ... Sun 2026-02-15 07:00:36 CET -> Sun 2026-02-15 09:57:30 CET
Aus Sicht des Journals Schluss, hm, keine Shutdown/reboot logs
Spricht eher dafür daß Proxmox weg war nicht VM HA
journalctl --since today
Feb 15 00:19:24 pve pvedaemon[1054]: worker 1309896 started
Feb 15 01:17:01 pve CRON[1325264]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Feb 15 01:17:01 pve CRON[1325266]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Feb 15 01:17:01 pve CRON[1325264]: pam_unix(cron:session): session closed for user root
Der Cronjob ist die letzte geloggte Aktivität aber die Ursache? Eher nicht.
Was mich immer noch wundert: Laut HA Aktivitätsprotokoll endete HA um 2:10 Uhr aber letzter Cron Logeintrag um 1:17 Uhr. Zeitzonen Mismatch?
last -x | head -n 10
root pts/0 Sun Feb 15 21:52 - still logged in
root pts/0 Sun Feb 15 20:59 - 21:23 (00:24)
root pts/0 Sun Feb 15 10:19 - 11:18 (00:59)
root pts/0 Sun Feb 15 10:05 - 10:17 (00:11)
root pts/0 Sun Feb 15 09:58 - 09:58 (00:00)
reboot system boot 6.17.9-1-pve Sun Feb 15 09:58 - still running
root pts/0 Sun Feb 15 09:52 - 09:57 (00:04)
reboot system boot 6.17.9-1-pve Sun Feb 15 07:00 - 09:57 (02:56)
shutdown system down 6.17.9-1-pve Sun Feb 15 09:57 - 09:58 (00:01) (Aus Versehen auf Powerknopf)
root pts/0 Sat Feb 14 12:02 - 12:02 (00:00)
Wichtig hier ist was es nicht zeigt → keine Events zwischen 14. und 15. → wäre nur VM; HA eingefroren hätte hier sicher noch etwas gestanden
dmesg -T | grep -i error
[Sun Feb 15 09:58:14 2026] RAS: Correctable Errors collector initialized.
Ziemlich wenig Fehler und der kam weil ich aus Versehen den Powerknopf gedrückt hatte.
journalctl -b -2 --no-pager | egrep -i "oom|out of memory|killed process|panic|reset|nvme|i/o error|ext4|btrfs|zfs|watchdog|mce|machine check|segfault|corrupt|read-only"
Feb 15 07:00:36 pve kernel: NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
Feb 15 07:00:36 pve kernel: Write protecting the kernel read-only data: 38912k
Feb 15 07:00:36 pve kernel: nvme 0000:06:00.0: platform quirk: setting simple suspend
Feb 15 07:00:36 pve kernel: nvme nvme0: pci function 0000:06:00.0
Feb 15 07:00:36 pve kernel: nvme nvme0: allocated 128 MiB host memory buffer (1 segment).
Feb 15 07:00:36 pve kernel: nvme nvme0: 4/0/0 default/read/poll queues
Feb 15 07:00:36 pve kernel: nvme0n1: p1 p2 p3
Feb 15 07:00:36 pve kernel: Btrfs loaded, zoned=yes, fsverity=yes
Feb 15 07:00:36 pve kernel: EXT4-fs (dm-1): orphan cleanup on readonly fs
Feb 15 07:00:36 pve kernel: EXT4-fs (dm-1): mounted filesystem f039c946-1ce7-4c60-8db3-0704928e1daa ro with ordered data mode. Quota mode: none.
Feb 15 07:00:36 pve kernel: EXT4-fs (dm-1): re-mounted f039c946-1ce7-4c60-8db3-0704928e1daa r/w.
Feb 15 07:00:36 pve kernel: zfs: module license 'CDDL' taints kernel.
Feb 15 07:00:36 pve kernel: zfs: module license taints kernel.
Feb 15 07:00:36 pve udevadm[394]: systemd-udev-settle.service is deprecated. Please fix zfs-import-cache.service not to pull it in.
Feb 15 07:00:36 pve lvm[427]: PV /dev/nvme0n1p3 online, VG pve is complete.
Feb 15 07:00:36 pve systemd-fsck[441]: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
Feb 15 07:00:36 pve systemd-fsck[441]: /dev/nvme0n1p2: 13 files, 2244/261628 clusters
Feb 15 07:00:37 pve kernel: ZFS: Loaded module v2.4.0-pve1, ZFS pool version 5000, ZFS filesystem version 5
Feb 15 07:00:37 pve systemd-modules-load[310]: Inserted module 'zfs'
Feb 15 07:00:37 pve kernel: i915 0000:00:02.0: [drm] Registered 3 planes with drm panic
Feb 15 07:00:37 pve systemd[1]: zfs-import-cache.service - Import ZFS pools by cache file was skipped because of an unmet condition check (ConditionFileNotEmpty=/etc/zfs/zpool.cache).
Feb 15 07:00:37 pve systemd[1]: Reached target zfs-import.target - ZFS pool import target.
Feb 15 07:00:37 pve systemd[1]: Starting zfs-mount.service - Mount ZFS filesystems...
Feb 15 07:00:37 pve systemd[1]: Starting zfs-volume-wait.service - Wait for ZFS Volume (zvol) links in /dev...
Feb 15 07:00:37 pve systemd[1]: Finished zfs-mount.service - Mount ZFS filesystems.
Feb 15 07:00:37 pve systemd[1]: Finished zfs-volume-wait.service - Wait for ZFS Volume (zvol) links in /dev.
Feb 15 07:00:37 pve systemd[1]: Reached target zfs-volumes.target - ZFS volumes are ready.
Feb 15 07:00:37 pve systemd[1]: Started e2scrub_all.timer - Periodic ext4 Online Metadata Check for All Filesystems.
Feb 15 07:00:37 pve systemd[1]: Starting e2scrub_reap.service - Remove Stale Online ext4 Metadata Check Snapshots...
Feb 15 07:00:37 pve systemd[1]: Started watchdog-mux.service - Proxmox VE watchdog multiplexer.
Feb 15 07:00:37 pve systemd[1]: Starting zfs-share.service - ZFS file system shares...
Feb 15 07:00:37 pve systemd[1]: Started zfs-zed.service - ZFS Event Daemon (zed).
Feb 15 07:00:38 pve systemd[1]: Finished e2scrub_reap.service - Remove Stale Online ext4 Metadata Check Snapshots.
Feb 15 07:00:38 pve zed[677]: ZFS Event Daemon 2.4.0-pve1 (PID 677)
Feb 15 07:00:38 pve kernel: softdog: initialized. soft_noboot=0 soft_margin=60 sec soft_panic=0 (nowayout=0)
Feb 15 07:00:38 pve watchdog-mux[673]: Watchdog driver 'Software Watchdog', version 0
Feb 15 07:00:38 pve kernel: nvme nvme0: using unchecked data buffer
Feb 15 07:00:38 pve smartd[668]: Device: /dev/nvme0, opened
Feb 15 07:00:38 pve smartd[668]: Device: /dev/nvme0, WD_BLACK SN770 1TB, S/N:24427S403806, FW:731100WD, 1.00 TB
Feb 15 07:00:38 pve systemd[1]: Finished zfs-share.service - ZFS file system shares.
Feb 15 07:00:38 pve systemd[1]: Reached target zfs.target - ZFS startup target.
Feb 15 07:00:38 pve smartd[668]: Device: /dev/nvme0, is SMART capable. Adding to "monitor" list.
Feb 15 07:00:38 pve smartd[668]: Device: /dev/nvme0, state read from /var/lib/smartmontools/smartd.WD_BLACK_SN770_1TB-24427S403806.nvme.state
Feb 15 07:00:38 pve smartd[668]: Monitoring 0 ATA/SATA, 0 SCSI/SAS and 1 NVMe devices
Feb 15 07:00:38 pve smartd[668]: Device: /dev/nvme0, state written to /var/lib/smartmontools/smartd.WD_BLACK_SN770_1TB-24427S403806.nvme.state
Feb 15 07:00:38 pve sensors[703]: nvme-pci-0600
Feb 15 07:00:47 pve systemd[1]: Starting e2scrub_all.service - Online ext4 Metadata Check for All Filesystems...
Feb 15 07:00:47 pve systemd[1]: Finished e2scrub_all.service - Online ext4 Metadata Check for All Filesystems.
Feb 15 07:00:53 pve kernel: usb 3-4: reset full-speed USB device number 2 using xhci_hcd
Hellörig machte
systemd-fsck[441]: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
Weil ich 7 Uhr MiniPC com Strom getrennt hatte oder weil es einen Freeze in der Nacht gab?
Wenn ich so richtig in den Logs nichts finde, was kann dann die Ursache sein?
ChatGPT redet von
CPU → tiefster C-State
PCIe → ASPM
NVMe → niedrigster Power State
NIC → EEE
C-State - was soll das denn sein? (Vergeßt nicht, ich bin Proxmox/MiniPC Anfänger der sich gerade in Logfile Analyse einarbeitet)
Klar Powermanagement kenne ich aber nicht doch ich, hab doch alles abgeschaltet.
Aber ein Blick kann nicht schaden.
Mini-PC heruntergefahren → Monitor/Tatstatur angeschlossen → ab ins BIOS
Ohnee, alles enabled! Wie oft las ich hier im Forum schon von Energiesparmodus und war mir so sicher, ich hab alles deaktiviert.
Ob das wirklich die einzige Ursache war?
Das werde ich die nächsten Wochen sehen.
Kommentare und Hinweise sind wie immer willkommen
Wie geht Ihr vor bei einem Problem?
Welche Befehle verwendet Ihr?
EDITs:
Kleinigkeiten