Adam-

but...this also doesn't seem good thats with a 1% CPU load!

ive had syslog up and running since October last year trying to figure it out without success... but i am not the best with these things... it could be a hardware issue... but when i rebuilt the server i stripped and cleaned the lot incl. repasting the CPU and cleaning the cooler... it is a 6 year old server though syslog-192.168.1.197.log

unfortunately this drew a blank. I disabled all scripts and woke up to a shut down server. its always a crash shut down as when i reboot, the parity check starts. attaching here my diagnostics file. can anyone take a look through and see if anything obvious? unraid-diagnostics-20240606-1838.zip

i see in the syslog download this as the last entry before the crash: Jun 2 10:48:01 UnRaid crond[1540]: failed parsing crontab for user root: ? * THU * /usr/local/emhttp/plugins/user.scripts/startCustom.php /boot/config/plugins/user.scripts/scripts/Scheduled reboot/script > /dev/null 2>&1 could be this the issue? I've tried disabling the script to see if it helps!

hi folks. I am after a bit of expert guidance. i have my unraid server that has happily been ticking along for the past 6 years. in the past 6 months it suffers random shutdowns not long after startup - sometimes within 15 minutes sometimes it takes an hour or more. i have disassembled it, re-thermal pasted it, and cannot find any basic hardware issues. i am not sure what logs to check and how that would indicate what would be casuing the crash shutdowns. can someone give me a basic set of steps for log viewing such that i can share the results back here that may indicate the cause? Thanks Adam