I have an Elitedesk 800 mini.
Have you by any chance have TPM enabled in the BIOS? I disabled TPM alltogether and since then no more reboots/freezes.
(running pve 7.4 and kernel 6.2.11)
Proxmox restarts randomly
- Thread starter GraphiqueXpert
- Start date
I have an Elitedesk 800 mini.
Have you by any chance have TPM enabled in the BIOS? I disabled TPM alltogether and since then no more reboots/freezes.
(running pve 7.4 and kernel 6.2.11)
I have two identical home "servers" running ASRock X570 Pro4, AMD Ryzen 5600G, 2x32GB DDR4 3200 and 10Gb cards.
One of the machines started randomly rebooting about 10 days ago. There is absolutely no correlation between reboots and anything that I could think off. Sometimes it would reboot every ten minutes or so, sometimes the uptime can get as high as 12 hrs.
Tried changing PSU, replacing motherboard, disconnecting all the drives, leaving only the root NVME the same shit happens.
What is funny is that it is stable in memtest, had run it for 12 hrs straight, and when i boot from external USB drive distro like systemrescue.
Don't know what to think more, ordered a new CPU yday. followed the advice of disabling the TPM, did not help. The situation drives me mad TBH.
One of the machines started randomly rebooting about 10 days ago. There is absolutely no correlation between reboots and anything that I could think off. Sometimes it would reboot every ten minutes or so, sometimes the uptime can get as high as 12 hrs.
Tried changing PSU, replacing motherboard, disconnecting all the drives, leaving only the root NVME the same shit happens.
What is funny is that it is stable in memtest, had run it for 12 hrs straight, and when i boot from external USB drive distro like systemrescue.
Don't know what to think more, ordered a new CPU yday. followed the advice of disabling the TPM, did not help. The situation drives me mad TBH.
Last edited:
You could try throwing Windows Server on a spare SSD for a day. If it still crashes, it's hardware.
D
Deleted member 205422
Guest
Did you mean it was getting frozen? Do you actually see
-- Reboot -- in the logs? Anything in dmesg?Actually, my Proxmox ran for about 6 hours, then it shutdown again. For some reason, mine doesn't reboot when it crashes.
Last edited:
I restarted a while back and didn't see the behaviour anymore till a few days ago. I see in the syslog --reboot-- but can't figure out what it causes.
If I look in the syslogs, I see only the following entries just before it reboots
No idea where to go from here
Code:
Nov 09 05:17:01 pve CRON[1415670]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Nov 09 05:17:01 pve CRON[1415671]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Nov 09 05:17:01 pve CRON[1415670]: pam_unix(cron:session): session closed for user root
-- Reboot --No idea where to go from here
D
Deleted member 205422
Guest
I have a cluster with 4 x HP Elitedesk G4 mini and 2 x HP Prodesk G5 mini.
Since the upgrading from kernel 6.2.x to 6.5.x, some hypervisors are randomly crashing. Several times a day. Only experienced this with Elitedesk systems, not with Prodesk systems (yet).
No messages in logging. I cannot see the console, because they are headless (no keyboard, no monitor attached).
BIOS'es are up to date.
I seem to have found a fix by disabling GPU powermanagement by adding kernel parameter "i915.enable_dc=0".
See also https://forum.proxmox.com/threads/p...ues-with-hardware-transcoding-in-plex.132187/
Since the upgrading from kernel 6.2.x to 6.5.x, some hypervisors are randomly crashing. Several times a day. Only experienced this with Elitedesk systems, not with Prodesk systems (yet).
No messages in logging. I cannot see the console, because they are headless (no keyboard, no monitor attached).
BIOS'es are up to date.
I seem to have found a fix by disabling GPU powermanagement by adding kernel parameter "i915.enable_dc=0".
See also https://forum.proxmox.com/threads/p...ues-with-hardware-transcoding-in-plex.132187/
Thanks for this hint. I had it enabled but even with disabled TPM there are still random reboots.
Also the kernel parameter mentioned by @Jacco did not work for me...
Last edited: