Teknowiz

Well seems I finally manged to stabilize the system by changing following settings using Tips and Tweaks addon: Disable NIC Flow Control? Yes Disable NIC Offload?Yes Normal CPU Scaling Governor: Performance Previously I had NIC related settings at default and Normal CPU Scaling Governor set to on demand but now with those settings system becomes unresponsive randomly. Not sure which of the 3 settings is actually causing the issue as disabling C states in bios and just disabling NIC related settings or setting docker lan network type to ipvlan don't seem to fix the problem. Also odd system ran for long time with those settings without issues and with latest build of Unraid it becomes unstable. At lest system seems to be functional again without needing new hardware.

System still unstable with no useful info on logs even when stored in flash. Recreated install form scratch on fresh USB without even backing up config and still crashes. Tried new power supply same result. Disconnected LSI HBA card and all hard drives and still crashes. Ran CPU stress test from Ubuntu live CD for 24+ hours at 100% CPU load without single crash. Ran Memtest86+ for 3+ days without any errors being detected. Still no cluse what issue could be as all feasible hardware issues seem to be ruled out at this point. Contemplating taking out the 2 NVME drives next to see if that helps. Any suggestions what else to try. My only other alternative is get new intel cpu and board at this point.

Already tried running with bare minimum in safe mode with no docker or vm service enabled and still crashes. Odd thing is no crash or errors while running memtest or in ubuntu while doing CPU stress test. I would think hardware issue would cause crash in any boot environment. More logs attached from more crashes over nigh but this time there seems to be some errors that I don't recognize. I wonder if its my HBA card or a corrupted file system that could be causing the issue.

Flash syslog seems to have logged data but nothing sticks out to me as source of the instability.

Got this so far on remote syslog server up to system becoming non responsive again. Don't seem to have much to go on it other than samba errors..

Mirror option was already enabled but didn't seem to capture crash details on diagnostics log unless it gets stored somewhere else on the flash. It crashed again also after enabling remote syslog but remote log entries showed nothing out of ordinary prior to crash, just bunch of kernel messages regarding usb connect disconnect events for the mouse.

I enabled remote syslog and started logging to my desktop, will see if it records anything on the next crash/hang. I wish Unraid would store logs on flash so it would survive the reboot.

Did 3 more passes of Mem test and all past. Ran CPU stress test for 4 hours from ubuntu live CD with 100% CPU load and all passed. Restarted the system after testing to Unraid in safe mode and with Docker and VMs all disabled and system hung again after short time of parity check. Not sure what else to test hardware wise anymore. Attached is another diagnostics log in case anyone is able to identify the source of the stability.

Thanks, will try that. Also potentially planning to boot into like a Linux live CD and run some CPU diagnostics.

Well it looks like Plex docker was not source of the issue. Instead of hourly freeze or reboot now it seems to last 6-8 hours and then still hangs or reboots. Getting frustrated with this issue with logs not showing any source of the problem and constant crashes causing lot of parity data issues but not able to complete parity check to repair before another crash. Any ideas on enabling any other logging or troubleshooting. I have tried memtest and it passed, tried disabling DOCP memory profile so it lowers the RAM speed back to stock, disabled C-STATE completely in Bios but issue still persists. I even removed the new parity drive installed last week but still had same issue.

I may have narrowed the issue down to Plex server official docker being the issue or possibly it combined with AMD igpu transcoding. Disabled the Plex container and server was up 12+ hours which is longer than I had managed before since start of the issue. Will see if other Plex containers are more stable or temporarily keep Plex disabled to see if system is back to full stability.

My issue seems possibly Plex related, had installed official Plex docker right before issue started. Disabled that container and system has been stable for 12+ hours. If you have Plex see if disabling it helps.

I am facing the same issue on a Ryzen system, I wonder if its related to recent release of Unraid.

And now another reboot on its own even without array being started.

Updated diagnostics files below. System crashed few hours after starting array. Hopefully syslog files will be useful. Seems another user facing similar issue with similar cpu. https://forums.unraid.net/topic/145280-system-becomes-unresponsive-after-a-few-hours/