Hi, Im new here so please bear with me. I have unraid running with Frigate in a docker and home assistant in a VM. I have ben having problems with the system going unreponsive, sometimes in a s little as 36 hours, just now it had done 5 days, then the system hangs and the VM stops working, The machine as a G2 800 HP Elite with an i5-6500 processor and 32GB ram over 4 slots, So far i did an 8 hour memtest of the ram which it passed 100% I have changed the power supply twice to 2 others i knew where OK. I have flashed the logs to the USB but there is nothing in the logs that I can see, I have removed disks from the machine to see if that makes a difference, so now just running an array of 2 2TB disks and a 256 GB SSD Cache drive, As soon as I reboot it it all comes back up and works until the next time I have uploaded my diagnostic download, doe anyone have any suggestions of where I start looking.Many Thanks Andy

shirleylodge-diagnostics-20260120-1354.zip

10 minutes ago, handyandy63 said:

flashed the logs to the USB

If you mean you have setup Syslog Server, those logs are not included in the diagnostics. Zip them and attach to your NEXT post in this thread.

Sorry hadn't realised hey were not included, here they are

syslog-192.168.1.228.log

Since those logs could cover many days (yours goes back to Jan 4) or even months, they could be very large (though smaller if zipped), so they are not included in diagnostics.

Jan 20 11:00:07 ShirleyLodge monitor_nchan: Stop running nchan processes

Jan 20 13:41:17 ShirleyLodge rc.rsyslogd: Syslog server daemon... Started.

Assuming the last crash happened between those two lines, unfortunately, there's nothing relevant logged, this can also be a hardware issue, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one, including the individual docker containers.

Additionally, look in the BIOS for a "Global C-States" or similar setting and disable that to retest, it's been known to be a problem with some boards, with both Intel and AMD CPUs.

Thanks for the advice, will look at the suggestions, I was hoping I was missing a trick with regards finding the cause but will dig deeper, I need the server running because it controls my heating so for a start I have pulled all but one ram chip and started it up again, I have a sneaking suspicion its a ram issue but they tested ok with Memtest86 but will see what happens