HM90 Proxmox regelmäßig nicht erreichbar

[Peter_SP]

Hallo Leute,

Ich habe einen Minisforum PC mit 32Gb Ram und einem AMD Ryzen 9 4900H und einer 512 Gb ssd. Leider ist alle 1-2 Wochen der PC nicht mehr erreichbar und es hilft nur mehr ihn stromlos zu machen und dann wieder einschalten. Verwende den PC für ioBroker.

Hat einer eine Idee woran das liegen könnte? Heute um 04:34 ist die Kiste wieder abgeschmiert

LG Peter

May 26 23:07:21 proxmox pveproxy[1146]: starting 1 worker(s)
May 26 23:07:21 proxmox pveproxy[1146]: worker 1381776 started
May 26 23:13:57 proxmox pveproxy[1354864]: worker exit
May 26 23:13:57 proxmox pveproxy[1146]: worker 1354864 finished
May 26 23:13:57 proxmox pveproxy[1146]: starting 1 worker(s)
May 26 23:13:57 proxmox pveproxy[1146]: worker 1383719 started
May 26 23:17:01 proxmox CRON[1384689]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
May 26 23:17:01 proxmox CRON[1384690]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
May 26 23:17:01 proxmox CRON[1384689]: pam_unix(cron:session): session closed for user root
May 27 00:00:04 proxmox systemd[1]: Starting dpkg-db-backup.service - Daily dpkg database backup service...
May 27 00:00:04 proxmox systemd[1]: Starting logrotate.service - Rotate log files...
May 27 00:00:04 proxmox systemd[1]: dpkg-db-backup.service: Deactivated successfully.
May 27 00:00:04 proxmox systemd[1]: Finished dpkg-db-backup.service - Daily dpkg database backup service.
May 27 00:00:04 proxmox logrotate[1397503]: error: unifi:7 unknown user 'unifi'
May 27 00:00:04 proxmox logrotate[1397503]: error: found error in /usr/lib/unifi/logs/mongod.log , skipping
May 27 00:00:04 proxmox logrotate[1397503]: error: found error in file unifi, skipping
May 27 00:00:04 proxmox systemd[1]: Reloading pveproxy.service - PVE API Proxy Server...
May 27 00:00:05 proxmox pveproxy[1397517]: send HUP to 1146
May 27 00:00:05 proxmox pveproxy[1146]: received signal HUP
May 27 00:00:05 proxmox pveproxy[1146]: server closing
May 27 00:00:05 proxmox pveproxy[1146]: server shutdown (restart)
May 27 00:00:05 proxmox systemd[1]: Reloaded pveproxy.service - PVE API Proxy Server.
May 27 00:00:05 proxmox systemd[1]: Reloading spiceproxy.service - PVE SPICE Proxy Server...
May 27 00:00:05 proxmox spiceproxy[1397519]: send HUP to 1152
May 27 00:00:05 proxmox spiceproxy[1152]: received signal HUP
May 27 00:00:05 proxmox spiceproxy[1152]: server closing
May 27 00:00:05 proxmox spiceproxy[1152]: server shutdown (restart)
May 27 00:00:05 proxmox systemd[1]: Reloaded spiceproxy.service - PVE SPICE Proxy Server.
May 27 00:00:05 proxmox pvefw-logger[967233]: received terminate request (signal)
May 27 00:00:05 proxmox pvefw-logger[967233]: stopping pvefw logger
May 27 00:00:05 proxmox systemd[1]: Stopping pvefw-logger.service - Proxmox VE firewall logger...
May 27 00:00:06 proxmox spiceproxy[1152]: restarting server
May 27 00:00:06 proxmox spiceproxy[1152]: starting 1 worker(s)
May 27 00:00:06 proxmox spiceproxy[1152]: worker 1397528 started
May 27 00:00:06 proxmox systemd[1]: pvefw-logger.service: Deactivated successfully.
May 27 00:00:06 proxmox systemd[1]: Stopped pvefw-logger.service - Proxmox VE firewall logger.
May 27 00:00:06 proxmox systemd[1]: pvefw-logger.service: Consumed 22.071s CPU time.
May 27 00:00:06 proxmox systemd[1]: Starting pvefw-logger.service - Proxmox VE firewall logger...
May 27 00:00:06 proxmox pvefw-logger[1397531]: starting pvefw logger
May 27 00:00:06 proxmox systemd[1]: Started pvefw-logger.service - Proxmox VE firewall logger.
May 27 00:00:06 proxmox systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE
May 27 00:00:06 proxmox systemd[1]: logrotate.service: Failed with result 'exit-code'.
May 27 00:00:06 proxmox systemd[1]: Failed to start logrotate.service - Rotate log files.
May 27 00:00:06 proxmox pveproxy[1146]: restarting server
May 27 00:00:06 proxmox pveproxy[1146]: starting 3 worker(s)
May 27 00:00:06 proxmox pveproxy[1146]: worker 1397536 started
May 27 00:00:06 proxmox pveproxy[1146]: worker 1397537 started
May 27 00:00:06 proxmox pveproxy[1146]: worker 1397538 started
May 27 00:00:11 proxmox spiceproxy[967230]: worker exit
May 27 00:00:11 proxmox spiceproxy[1152]: worker 967230 finished
May 27 00:00:11 proxmox pveproxy[1381776]: worker exit
May 27 00:00:11 proxmox pveproxy[1378839]: worker exit
May 27 00:00:11 proxmox pveproxy[1383719]: worker exit
May 27 00:00:11 proxmox pveproxy[1146]: worker 1381776 finished
May 27 00:00:11 proxmox pveproxy[1146]: worker 1383719 finished
May 27 00:00:11 proxmox pveproxy[1146]: worker 1378839 finished
May 27 00:02:54 proxmox systemd[1]: Starting fstrim.service - Discard unused blocks on filesystems from /etc/fstab...
May 27 00:05:04 proxmox fstrim[1398385]: /boot/efi: 1010.4 MiB (1059430400 bytes) trimmed on /dev/nvme0n1p2
May 27 00:05:04 proxmox fstrim[1398385]: /: 83.4 GiB (89582972928 bytes) trimmed on /dev/pve/root
May 27 00:05:04 proxmox systemd[1]: fstrim.service: Deactivated successfully.
May 27 00:05:04 proxmox systemd[1]: Finished fstrim.service - Discard unused blocks on filesystems from /etc/fstab.
May 27 00:05:04 proxmox systemd[1]: fstrim.service: Consumed 1.354s CPU time.
May 27 00:17:01 proxmox CRON[1402596]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
May 27 00:17:01 proxmox CRON[1402597]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
May 27 00:17:01 proxmox CRON[1402596]: pam_unix(cron:session): session closed for user root
May 27 00:18:42 proxmox pvedaemon[1374242]: <root@pam> successful auth for user 'root@pam'
May 27 01:05:27 proxmox pvedaemon[1369571]: worker exit
May 27 01:05:28 proxmox pvedaemon[1137]: worker 1369571 finished
May 27 01:05:28 proxmox pvedaemon[1137]: starting 1 worker(s)
May 27 01:05:28 proxmox pvedaemon[1137]: worker 1417014 started
May 27 01:17:01 proxmox CRON[1420429]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
May 27 01:17:01 proxmox CRON[1420430]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
May 27 01:17:01 proxmox CRON[1420429]: pam_unix(cron:session): session closed for user root
May 27 01:30:48 proxmox pveproxy[1397538]: worker exit
May 27 01:30:48 proxmox pveproxy[1146]: worker 1397538 finished
May 27 01:30:48 proxmox pveproxy[1146]: starting 1 worker(s)
May 27 01:30:48 proxmox pveproxy[1146]: worker 1424521 started
May 27 01:31:52 proxmox pvedaemon[1374242]: worker exit
May 27 01:31:52 proxmox pvedaemon[1137]: worker 1374242 finished
May 27 01:31:52 proxmox pvedaemon[1137]: starting 1 worker(s)
May 27 01:31:52 proxmox pvedaemon[1137]: worker 1424865 started
May 27 01:34:46 proxmox pvedaemon[1380294]: worker exit
May 27 01:34:46 proxmox pvedaemon[1137]: worker 1380294 finished
May 27 01:34:46 proxmox pvedaemon[1137]: starting 1 worker(s)
May 27 01:34:46 proxmox pvedaemon[1137]: worker 1425702 started
May 27 01:39:47 proxmox pveproxy[1397537]: worker exit
May 27 01:39:47 proxmox pveproxy[1146]: worker 1397537 finished
May 27 01:39:47 proxmox pveproxy[1146]: starting 1 worker(s)
May 27 01:39:47 proxmox pveproxy[1146]: worker 1427206 started
May 27 01:47:58 proxmox pveproxy[1397536]: worker exit
May 27 01:47:58 proxmox pveproxy[1146]: worker 1397536 finished
May 27 01:47:58 proxmox pveproxy[1146]: starting 1 worker(s)
May 27 01:47:58 proxmox pveproxy[1146]: worker 1429631 started
May 27 02:11:26 proxmox systemd[1]: Starting pve-daily-update.service - Daily PVE download activities...
May 27 02:11:27 proxmox pveupdate[1436639]: <root@pam> starting task UPID:proxmox:0015EBE4:01B7C24D:6653CFAF:aptupdate::root@pam:
May 27 02:11:29 proxmox dbus-daemon[781]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.18' (uid=0 pid=1437047 comm="/usr/bin/gdbus call --system --dest org.freedeskto" label="unconfined")
May 27 02:11:29 proxmox systemd[1]: Starting packagekit.service - PackageKit Daemon...
May 27 02:11:29 proxmox PackageKit[1437050]: daemon start
May 27 02:11:29 proxmox dbus-daemon[781]: [system] Successfully activated service 'org.freedesktop.PackageKit'
May 27 02:11:29 proxmox systemd[1]: Started packagekit.service - PackageKit Daemon.
May 27 02:11:29 proxmox pveupdate[1436644]: update new package list: /var/lib/pve-manager/pkgupdates
May 27 02:11:31 proxmox pveupdate[1436639]: <root@pam> end task UPID:proxmox:0015EBE4:01B7C24D:6653CFAF:aptupdate::root@pam: OK
May 27 02:11:31 proxmox systemd[1]: pve-daily-update.service: Deactivated successfully.
May 27 02:11:31 proxmox systemd[1]: Finished pve-daily-update.service - Daily PVE download activities.
May 27 02:11:31 proxmox systemd[1]: pve-daily-update.service: Consumed 3.038s CPU time.
May 27 02:16:35 proxmox PackageKit[1437050]: daemon quit
May 27 02:16:35 proxmox systemd[1]: packagekit.service: Deactivated successfully.
May 27 02:17:01 proxmox CRON[1438690]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
May 27 02:17:01 proxmox CRON[1438692]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
May 27 02:17:01 proxmox CRON[1438690]: pam_unix(cron:session): session closed for user root
May 27 02:18:54 proxmox pvedaemon[1425702]: <root@pam> successful auth for user 'root@pam'
May 27 03:04:36 proxmox pveproxy[1424521]: worker exit
May 27 03:04:36 proxmox pveproxy[1146]: worker 1424521 finished
May 27 03:04:36 proxmox pveproxy[1146]: starting 1 worker(s)
May 27 03:04:36 proxmox pveproxy[1146]: worker 1452895 started
May 27 03:10:01 proxmox CRON[1454506]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
May 27 03:10:01 proxmox CRON[1454507]: (root) CMD (test -e /run/systemd/system || SERVICE_MODE=1 /sbin/e2scrub_all -A -r)
May 27 03:10:01 proxmox CRON[1454506]: pam_unix(cron:session): session closed for user root
May 27 03:17:01 proxmox CRON[1456587]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
May 27 03:17:01 proxmox CRON[1456589]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
May 27 03:17:01 proxmox CRON[1456587]: pam_unix(cron:session): session closed for user root
May 27 03:20:11 proxmox pveproxy[1427206]: worker exit
May 27 03:20:11 proxmox pveproxy[1146]: worker 1427206 finished
May 27 03:20:11 proxmox pveproxy[1146]: starting 1 worker(s)
May 27 03:20:11 proxmox pveproxy[1146]: worker 1457524 started
May 27 03:28:06 proxmox pveproxy[1429631]: worker exit
May 27 03:28:06 proxmox pveproxy[1146]: worker 1429631 finished
May 27 03:28:06 proxmox pveproxy[1146]: starting 1 worker(s)
May 27 03:28:06 proxmox pveproxy[1146]: worker 1459861 started
May 27 03:43:09 proxmox pvedaemon[1417014]: worker exit
May 27 03:43:09 proxmox pvedaemon[1137]: worker 1417014 finished
May 27 03:43:09 proxmox pvedaemon[1137]: starting 1 worker(s)
May 27 03:43:09 proxmox pvedaemon[1137]: worker 1464349 started
May 27 04:08:46 proxmox pvedaemon[1424865]: worker exit
May 27 04:08:46 proxmox pvedaemon[1137]: worker 1424865 finished
May 27 04:08:46 proxmox pvedaemon[1137]: starting 1 worker(s)
May 27 04:08:46 proxmox pvedaemon[1137]: worker 1471987 started
May 27 04:11:08 proxmox pvedaemon[1425702]: worker exit
May 27 04:11:08 proxmox pvedaemon[1137]: worker 1425702 finished
May 27 04:11:08 proxmox pvedaemon[1137]: starting 1 worker(s)
May 27 04:11:08 proxmox pvedaemon[1137]: worker 1472676 started
May 27 04:17:01 proxmox CRON[1474452]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
May 27 04:17:01 proxmox CRON[1474453]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
May 27 04:17:01 proxmox CRON[1474452]: pam_unix(cron:session): session closed for user root
May 27 04:19:06 proxmox pvedaemon[1471987]: <root@pam> successful auth for user 'root@pam'
May 27 04:34:57 proxmox pveproxy[1452895]: worker exit
May 27 04:34:57 proxmox pveproxy[1146]: worker 1452895 finished
May 27 04:34:57 proxmox pveproxy[1146]: starting 1 worker(s)
May 27 04:34:57 proxmox pveproxy[1146]: worker 1479742 started
-- Reboot --
May 27 04:56:04 proxmox kernel: Linux version 6.8.4-3-pve (build@proxmox) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC PMX 6.8.4-3 (2024-05-02T11:55Z) ()
May 27 04:56:04 proxmox kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.8.4-3-pve root=/dev/mapper/pve-root ro quiet
May 27 04:56:04 proxmox kernel: KERNEL supported cpus:
May 27 04:56:04 proxmox kernel:   Intel GenuineIntel
May 27 04:56:04 proxmox kernel:   AMD AuthenticAMD
May 27 04:56:04 proxmox kernel:   Hygon HygonGenuine

 

[Mason]

Hi, hast du mal die Temperaturen im Auge gehabt? nicht das die CPU/RAM/PLATTEN zu heiß werden und er dann freezt

 

[Peter_SP]

Hi,

Die Temps habe ich noch nicht im Auge gehabt, allerdings steht das teil im Keller wo es kühl ist. CPU Auslastung ist selten über 2%.



LG Peter

 

[floh8]

Pinne dir mal einen älteren kernel oder den LTS.

 

[Peter_SP]

Pinne dir mal einen älteren kernel oder den LTS.

Und wie mach ich das bzw. auf welche Version? Sorry für die blöde Frage, bin Neuling.

LG Peter

 

[floh8]

Schau in die doku oder wiki!

 

[Peter_SP]

Habe vor ca. 3 Wochen Kernel Linux 6.5.13-5-pve angepinnt. Leider friert das System auch damit nach 2 Wochen ein

 

[Dunuin]

Außerdem mal memtest86+ booten und über Nacht laufen lassen. Systeminstabilitäten sind oft defekter RAM (gerade wenn du kein ECC hast, dass da Fehler gefixt werden könnten) oder defektes Netzteil mit Spannungsschwankungen was dann zum Brownout führt.

 

[Peter_SP]

Ok - ich habe auch noch 16 Gb Ram hier liegen - den kann ich ja einbauen auch wenn ich Proxmox mit den 32Gb installiert habe oder?

 

[Dunuin]

Ja, dann halt entsprechend weniger VMs starten.

 

[floh8]

Du müsstest jetzt mal im systemlog nach fehlermeldungen suchen.

 

[Tuxtom007]

Tag,

ich nutze auch deb HM90 mit 64GB Ram - das Teil macht den selben Ärger.

Ich hab schon etliche Tips aus diversen Foren probiert, BIOS-Settings angepasst usw.

Mein Verdacht ist das es Problem mit großen SSD's/HD's gibt - wobei aus einem anderen Forum jemand das nicht bestätigen konnte.

Bei mir läuft der HM90 solange stabil, wie ich SSD's mit 1 TB und darunter nutze, sobald eine in dem Fall zusätzliche SSD mit 2 TB verbaut ist, macht der Ärger und steigt ca. 1mal pro Woche komplett aus. Es finden sich auch keine Meldungen in den Logs.

 

[Falk R.]

Ich habe schon paar mal von Problemen mit HM90 gehört, manche haben von Minisforum einen Ersatz bekommen. Aber wenn das mit den Disks reproduzierbar ist, auf jeden Fall den Hersteller fragen.

 

[Tuxtom007]

Mein HM90 ist über zwei Jahre alt und die Problem erst in letzter Zeit aufgetreten.

Komischerweise läuft der mit Proxmox problemlos durch, wenn keinerlei LXC's / VM's drauf sind.

Da ist keinerlei Fehlermeldungen im Log habe und ich meine wichtiten VM's längst auf einen anderen Rechner ausgelagert habe, ist der HM90 eh abgeschrieben. der wird ausgeschlachtet und entsorgt.

 

[Mason]

Was wohl bei anderen geholfen hat ist die C-States des Prozessors komplett zu deaktivieren. Bei meinem Hunsn teste ich das grad, da der auch immer wieder mit CPU Softbug kam und eingefroren ist.

 

[Falk R.]

Mein HM90 ist über zwei Jahre alt und die Problem erst in letzter Zeit aufgetreten.

Komischerweise läuft der mit Proxmox problemlos durch, wenn keinerlei LXC's / VM's drauf sind.

Da ist keinerlei Fehlermeldungen im Log habe und ich meine wichtiten VM's längst auf einen anderen Rechner ausgelagert habe, ist der HM90 eh abgeschrieben. der wird ausgeschlachtet und entsorgt.

Welchen Kernel nutzt du derzeit?

 

[Tuxtom007]

Kann ich dir nicht sagen, weit wie gesagt, das Teil ist offline.
Hatte letzte eine Fallback auf 6.5.13-5-pve gemacht, weil mit dem aktuellen Probleme bei aktuellen Ubunut-LXC gab

 

[Peter_SP]

Habe bei meinem HM 90 jetzt neuen RAM verbaut. Nach 9 tagen ist die Kiste gestern wieder eingefroren . Nutze Linux 6.5.13-5-pve
Bin langsam echt am überlegen ob ich nicht einfach einen NUC hole. Könnte ich die SSD aus dem HM 90 nehmen und in einen Intel NUC einbauen und die Kiste würde wieder laufen oder wäre eine Neuinstallation besser?

 

[Peter_SP]

anbei noch der System Log. Um 18:27 ist der Server eingefroren

Jul 10 08:03:19 proxmox pveproxy[3506655]: worker exit

Jul 10 08:03:19 proxmox pveproxy[1141]: worker 3506655 finished

Jul 10 08:03:19 proxmox pveproxy[1141]: starting 1 worker(s)

Jul 10 08:03:19 proxmox pveproxy[1141]: worker 3531047 started

Jul 10 08:10:46 proxmox pveproxy[3507930]: worker exit

Jul 10 08:10:46 proxmox pveproxy[1141]: worker 3507930 finished

Jul 10 08:10:46 proxmox pveproxy[1141]: starting 1 worker(s)

Jul 10 08:10:46 proxmox pveproxy[1141]: worker 3532892 started

Jul 10 08:17:01 proxmox CRON[3534634]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)

Jul 10 08:17:01 proxmox CRON[3534635]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)

Jul 10 08:17:01 proxmox CRON[3534634]: pam_unix(cron:session): session closed for user root

Jul 10 08:32:55 proxmox pvedaemon[1132]: worker 3491632 finished

Jul 10 08:32:55 proxmox pvedaemon[1132]: starting 1 worker(s)

Jul 10 08:32:55 proxmox pvedaemon[1132]: worker 3538554 started

Jul 10 08:32:58 proxmox pvedaemon[3538551]: worker exit

Jul 10 08:36:05 proxmox systemd[1]: Starting man-db.service - Daily man-db regeneration...

Jul 10 08:36:05 proxmox systemd[1]: man-db.service: Deactivated successfully.

Jul 10 08:36:05 proxmox systemd[1]: Finished man-db.service - Daily man-db regeneration.

Jul 10 09:17:01 proxmox CRON[3549405]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)

Jul 10 09:17:01 proxmox CRON[3549406]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)

Jul 10 09:17:01 proxmox CRON[3549405]: pam_unix(cron:session): session closed for user root

Jul 10 09:28:48 proxmox pvedaemon[3510151]: <root@pam> successful auth for user 'root@pam'

Jul 10 09:30:52 proxmox pveproxy[3528609]: worker exit

Jul 10 09:30:52 proxmox pveproxy[1141]: worker 3528609 finished

Jul 10 09:30:52 proxmox pveproxy[1141]: starting 1 worker(s)

Jul 10 09:30:52 proxmox pveproxy[1141]: worker 3552833 started

Jul 10 09:42:58 proxmox pveproxy[3531047]: worker exit

Jul 10 09:42:58 proxmox pveproxy[1141]: worker 3531047 finished

Jul 10 09:42:58 proxmox pveproxy[1141]: starting 1 worker(s)

Jul 10 09:42:58 proxmox pveproxy[1141]: worker 3555830 started

Jul 10 09:43:59 proxmox pveproxy[3532892]: worker exit

Jul 10 09:43:59 proxmox pveproxy[1141]: worker 3532892 finished

Jul 10 09:43:59 proxmox pveproxy[1141]: starting 1 worker(s)

Jul 10 09:43:59 proxmox pveproxy[1141]: worker 3556065 started

Jul 10 09:59:12 proxmox pvedaemon[3510151]: worker exit

Jul 10 09:59:12 proxmox pvedaemon[1132]: worker 3510151 finished

Jul 10 09:59:12 proxmox pvedaemon[1132]: starting 1 worker(s)

Jul 10 09:59:12 proxmox pvedaemon[1132]: worker 3559784 started

Jul 10 10:17:01 proxmox CRON[3564168]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)

Jul 10 10:17:01 proxmox CRON[3564169]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)

Jul 10 10:17:01 proxmox CRON[3564168]: pam_unix(cron:session): session closed for user root

Jul 10 10:27:14 proxmox systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories...

Jul 10 10:27:14 proxmox systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.

Jul 10 10:27:14 proxmox systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories.

Jul 10 10:27:14 proxmox systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully.

Jul 10 10:37:33 proxmox pvedaemon[3520158]: worker exit

Jul 10 10:37:33 proxmox pvedaemon[1132]: worker 3520158 finished

Jul 10 10:37:33 proxmox pvedaemon[1132]: starting 1 worker(s)

Jul 10 10:37:33 proxmox pvedaemon[1132]: worker 3569234 started

Jul 10 11:06:07 proxmox pveproxy[3552833]: worker exit

Jul 10 11:06:07 proxmox pveproxy[1141]: worker 3552833 finished

Jul 10 11:06:07 proxmox pveproxy[1141]: starting 1 worker(s)

Jul 10 11:06:07 proxmox pveproxy[1141]: worker 3576240 started

Jul 10 11:17:01 proxmox CRON[3578892]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)

Jul 10 11:17:02 proxmox CRON[3578893]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)

Jul 10 11:17:02 proxmox CRON[3578892]: pam_unix(cron:session): session closed for user root

Jul 10 11:20:32 proxmox pveproxy[3555830]: worker exit

Jul 10 11:20:32 proxmox pveproxy[1141]: worker 3555830 finished

Jul 10 11:20:32 proxmox pveproxy[1141]: starting 1 worker(s)

Jul 10 11:20:32 proxmox pveproxy[1141]: worker 3579747 started

Jul 10 11:20:47 proxmox pveproxy[3556065]: worker exit

Jul 10 11:20:47 proxmox pveproxy[1141]: worker 3556065 finished

Jul 10 11:20:47 proxmox pveproxy[1141]: starting 1 worker(s)

Jul 10 11:20:47 proxmox pveproxy[1141]: worker 3579823 started

Jul 10 11:29:04 proxmox pvedaemon[3569234]: <root@pam> successful auth for user 'root@pam'

Jul 10 11:47:04 proxmox pvedaemon[3538554]: worker exit

Jul 10 11:47:04 proxmox pvedaemon[1132]: worker 3538554 finished

Jul 10 11:47:04 proxmox pvedaemon[1132]: starting 1 worker(s)

Jul 10 11:47:04 proxmox pvedaemon[1132]: worker 3586287 started

Jul 10 12:17:01 proxmox CRON[3593692]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)

Jul 10 12:17:01 proxmox CRON[3593693]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)

Jul 10 12:17:01 proxmox CRON[3593692]: pam_unix(cron:session): session closed for user root

Jul 10 12:46:48 proxmox pveproxy[3579823]: worker exit

Jul 10 12:46:48 proxmox pveproxy[1141]: worker 3579823 finished

Jul 10 12:46:48 proxmox pveproxy[1141]: starting 1 worker(s)

Jul 10 12:46:48 proxmox pveproxy[1141]: worker 3601024 started

Jul 10 12:51:10 proxmox pveproxy[3576240]: worker exit

Jul 10 12:51:10 proxmox pveproxy[1141]: worker 3576240 finished

Jul 10 12:51:10 proxmox pveproxy[1141]: starting 1 worker(s)

Jul 10 12:51:10 proxmox pveproxy[1141]: worker 3602082 started

Jul 10 13:00:26 proxmox pveproxy[3579747]: worker exit

Jul 10 13:00:26 proxmox pveproxy[1141]: worker 3579747 finished

Jul 10 13:00:26 proxmox pveproxy[1141]: starting 1 worker(s)

Jul 10 13:00:26 proxmox pveproxy[1141]: worker 3604372 started

Jul 10 13:11:46 proxmox pvedaemon[3559784]: worker exit

Jul 10 13:11:46 proxmox pvedaemon[1132]: worker 3559784 finished

Jul 10 13:11:46 proxmox pvedaemon[1132]: starting 1 worker(s)

Jul 10 13:11:46 proxmox pvedaemon[1132]: worker 3607180 started

Jul 10 13:17:01 proxmox CRON[3608451]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)

Jul 10 13:17:01 proxmox CRON[3608452]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)

Jul 10 13:17:01 proxmox CRON[3608451]: pam_unix(cron:session): session closed for user root

Jul 10 13:29:19 proxmox pvedaemon[3569234]: <root@pam> successful auth for user 'root@pam'

Jul 10 13:51:27 proxmox pvedaemon[3569234]: worker exit

Jul 10 13:51:27 proxmox pvedaemon[1132]: worker 3569234 finished

Jul 10 13:51:27 proxmox pvedaemon[1132]: starting 1 worker(s)

Jul 10 13:51:27 proxmox pvedaemon[1132]: worker 3616906 started

Jul 10 14:17:01 proxmox CRON[3623194]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)

Jul 10 14:17:01 proxmox CRON[3623195]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)

Jul 10 14:17:01 proxmox CRON[3623194]: pam_unix(cron:session): session closed for user root

Jul 10 14:19:46 proxmox pveproxy[3601024]: worker exit

Jul 10 14:19:46 proxmox pveproxy[1141]: worker 3601024 finished

Jul 10 14:19:46 proxmox pveproxy[1141]: starting 1 worker(s)

Jul 10 14:19:46 proxmox pveproxy[1141]: worker 3623885 started

Jul 10 14:29:02 proxmox pveproxy[3602082]: worker exit

Jul 10 14:29:02 proxmox pveproxy[1141]: worker 3602082 finished

Jul 10 14:29:02 proxmox pveproxy[1141]: starting 1 worker(s)

Jul 10 14:29:02 proxmox pveproxy[1141]: worker 3626133 started

Jul 10 14:37:17 proxmox pveproxy[3604372]: worker exit

Jul 10 14:37:17 proxmox pveproxy[1141]: worker 3604372 finished

Jul 10 14:37:17 proxmox pveproxy[1141]: starting 1 worker(s)

Jul 10 14:37:17 proxmox pveproxy[1141]: worker 3628192 started

Jul 10 15:03:47 proxmox pvedaemon[3586287]: worker exit

Jul 10 15:03:47 proxmox pvedaemon[1132]: worker 3586287 finished

Jul 10 15:03:47 proxmox pvedaemon[1132]: starting 1 worker(s)

Jul 10 15:03:47 proxmox pvedaemon[1132]: worker 3634688 started

Jul 10 15:17:01 proxmox CRON[3637937]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)

Jul 10 15:17:01 proxmox CRON[3637938]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)

Jul 10 15:17:01 proxmox CRON[3637937]: pam_unix(cron:session): session closed for user root

Jul 10 15:29:33 proxmox pvedaemon[3616906]: <root@pam> successful auth for user 'root@pam'

Jul 10 16:03:32 proxmox pveproxy[3626133]: worker exit

Jul 10 16:03:32 proxmox pveproxy[1141]: worker 3626133 finished

Jul 10 16:03:32 proxmox pveproxy[1141]: starting 1 worker(s)

Jul 10 16:03:32 proxmox pveproxy[1141]: worker 3649354 started

Jul 10 16:03:48 proxmox pveproxy[3623885]: worker exit

Jul 10 16:03:48 proxmox pveproxy[1141]: worker 3623885 finished

Jul 10 16:03:48 proxmox pveproxy[1141]: starting 1 worker(s)

Jul 10 16:03:48 proxmox pveproxy[1141]: worker 3649435 started

Jul 10 16:08:26 proxmox pveproxy[3628192]: worker exit

Jul 10 16:08:26 proxmox pveproxy[1141]: worker 3628192 finished

Jul 10 16:08:26 proxmox pveproxy[1141]: starting 1 worker(s)

Jul 10 16:08:26 proxmox pveproxy[1141]: worker 3650584 started

Jul 10 16:09:03 proxmox pvestatd[1105]: auth key pair too old, rotating..

Jul 10 16:17:01 proxmox CRON[3652665]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)

Jul 10 16:17:01 proxmox CRON[3652666]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)

Jul 10 16:17:01 proxmox CRON[3652665]: pam_unix(cron:session): session closed for user root

Jul 10 16:26:42 proxmox pvedaemon[3607180]: worker exit

Jul 10 16:26:42 proxmox pvedaemon[1132]: worker 3607180 finished

Jul 10 16:26:42 proxmox pvedaemon[1132]: starting 1 worker(s)

Jul 10 16:26:42 proxmox pvedaemon[1132]: worker 3655063 started

Jul 10 16:48:35 proxmox pvedaemon[3616906]: worker exit

Jul 10 16:48:35 proxmox pvedaemon[1132]: worker 3616906 finished

Jul 10 16:48:35 proxmox pvedaemon[1132]: starting 1 worker(s)

Jul 10 16:48:35 proxmox pvedaemon[1132]: worker 3660446 started

Jul 10 17:17:01 proxmox CRON[3667399]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)

Jul 10 17:17:01 proxmox CRON[3667400]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)

Jul 10 17:17:01 proxmox CRON[3667399]: pam_unix(cron:session): session closed for user root

Jul 10 17:29:49 proxmox pvedaemon[3660446]: <root@pam> successful auth for user 'root@pam'

Jul 10 17:39:21 proxmox pveproxy[3649435]: worker exit

Jul 10 17:39:21 proxmox pveproxy[1141]: worker 3649435 finished

Jul 10 17:39:21 proxmox pveproxy[1141]: starting 1 worker(s)

Jul 10 17:39:21 proxmox pveproxy[1141]: worker 3672888 started

Jul 10 17:39:21 proxmox pveproxy[3650584]: worker exit

Jul 10 17:39:21 proxmox pveproxy[1141]: worker 3650584 finished

Jul 10 17:39:21 proxmox pveproxy[1141]: starting 1 worker(s)

Jul 10 17:39:21 proxmox pveproxy[1141]: worker 3672892 started

Jul 10 17:45:15 proxmox pveproxy[3649354]: worker exit

Jul 10 17:45:16 proxmox pveproxy[1141]: worker 3649354 finished

Jul 10 17:45:16 proxmox pveproxy[1141]: starting 1 worker(s)

Jul 10 17:45:16 proxmox pveproxy[1141]: worker 3674347 started

Jul 10 18:17:01 proxmox CRON[3682113]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)

Jul 10 18:17:01 proxmox CRON[3682114]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)

Jul 10 18:17:01 proxmox CRON[3682113]: pam_unix(cron:session): session closed for user root

Jul 10 18:27:12 proxmox pvedaemon[3634688]: worker exit

Jul 10 18:27:12 proxmox pvedaemon[1132]: worker 3634688 finished

Jul 10 18:27:12 proxmox pvedaemon[1132]: starting 1 worker(s)

Jul 10 18:27:12 proxmox pvedaemon[1132]: worker 3684608 started

-- Reboot --

Jul 10 19:00:16 proxmox kernel: Linux version 6.5.13-5-pve (build@proxmox) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC PMX 6.5.13-5 (2024-04-05T11:03Z) ()

 

[Tuxtom007]

Ich hab meinen HM90 entsorgt, das Teil ging mir zu lange auf die Nerven.

Die wichtigen VM's und LXC's laufen auf einem zweiten Proxmoxserver ( gebrauchter Fujitsu ) und von dem werde ich mir noch ein oder zwei mit mehr RAM , stärkerer CPU nachkaufen und die nutzen.
Der macht seit Beginn an keinerlei Probleme