Hello UnRAID community,

I recently made the switch from OMV to UnRAID, hoping for a smooth experience with my server setup. However, I've encountered some frustrating stability issues and could really use some guidance.

Here's a rundown of my situation:

I migrated my existing server, equipped with an Asrock Q1900 ITX motherboard (Intel® Quad-Core Processor J1900, 16GB RAM), to UnRAID in December. Initially, everything seemed to be working fine.

After about a month, I encountered an issue with one of the memory slots on the motherboard, prompting me to upgrade.

I upgraded to an SZBOX N100 motherboard (https://www.amazon.com/Motherboard-Generation-Processor-Accessories-No/dp/B0CRB567PS?th=1). The system ran smoothly for a few days before starting to freeze randomly, with intervals ranging from 30 minutes to 4-5 hours.

A full Memtest revealed errors in my new Corsair 16GB DDR5 SODIMM memory stick. I replaced it with a new Kingston 16GB module and conducted several hours of Memtest without any errors.

However, even after replacing the faulty memory the problem was still present.
As a next step I've reinstalled UnRAID with a fresh flash drive, installed the license and the system worked fine for few days. I've managed to install some docker apps (there was no docker apps and plugins after the reinstall). But then after a restart, some docker apps that I had installed disappeared, while previously installed ones reappeared, and the problem with stability was present again. 

I attempted to troubleshoot by stopping all docker apps and even refrained from starting the array, but the freezing issue persisted, occurring within 30 to 120 minutes after startup.

Strangely, after a restart, the server initially performs well for a short period before the problem resurfaces. No error messages are displayed after the restart.

I'm at a loss for what could be causing these stability issues and would greatly appreciate any insights or advice from the community. Has anyone encountered similar issues with UnRAID? Any suggestions on how to further diagnose and resolve these problems would be immensely helpful.

Thank you in advance for your assistance.

xtrm-cube-diagnostics-20240222-1914.zip

Enable the syslog server and post that after a crash.

Here are the new diagnostics, generated after the syslog server was enabled

xtrm-cube-diagnostics-20240222-2011.zip

There's no syslog previous, persistent syslog only comes with the diags if you have enabled the mirror to flash drive option and reboot at least once.

Yesterday after starting the syslog and setting to copy on the flash card the server worked fine for couple hours, but this morning it was unaccessible again. Here is a diagnostic file after restarting it. :

 

xtrm-cube-diagnostics-20240223-0917.zip

Previous syslog only covers 1 minute uptime, is that the correct session?

I was a log generated immediately after the start, now I've generated another and I verified that I have a syslog-previous.txt in the logs/ folder.

xtrm-cube-diagnostics-20240223-1214.zip

Also, I've just checked the syslog-previous.txt in the previous report "xtrm-cube-diagnostics-20240223-0917" and it covers data from Feb 22 22:03:01 to Feb 22 22:43:49 the time the server stopped responding. As I told you previously the server is very unstable and the sessions are short

Unraid driver is crashing, this is almost always a hardware problem, start by running memtest, or since memtest is only definitive when an error is found, see if you can get a different DIMM to test with.

I'll perform another memtest and get back to you

@JorgeBThank you for your support. Again the problem was with the ram stick, it passed the first pass on memtest86 but shown 13 errors on the second pass. Replaced it and after 4 hours memtest86 now the server is working for 15 hours.