Hi there,

 

I've been using Unraid for a while now - and more recently I've found that it goes unresponsive - and I have to do a hard-reboot - which I'm obviously concerned could cause issues with my drives etc.

 

It's running with a AMD Ryzen 5 3600X 6-Core @ 3800 MHz.

 

have no idea what is causing it- I did change my syslog a while ago so it stores the previous version but I can't see anything in the syslog-previous for the day of the error - it only really shows the startup logs (I've attached the latest file from yesterday)

 

Anyone have any ideas how I can try and find out what is wrong?

 

Worth noting I am using IPvlan not MacVLAN and don't have any VMs running (only docker containers).

 

I've made sure that all my Dockers are up to date (some needed an update) after the last crash but seems like I'm just waiting for the inevitable right now;  one thing I did think of is running a script to reboot every day (so at least it's being shut down the right way) but seems better to get to the root cause first..

 

tower-diagnostics-20240609-1649.zip

The syslog in the diagnostics is the RAM version that starts afresh every time the system is booted.  You should enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to a crash.  The mirror to flash option is the easiest to set up (and if used the file is then automatically included in any diagnostics), but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field. 

2 hours ago, itimpi said:

The syslog in the diagnostics is the RAM version that starts afresh every time the system is booted.  You should enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to a crash.  The mirror to flash option is the easiest to set up (and if used the file is then automatically included in any diagnostics), but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field. 

Hmm let me take another look - I am pretty sure that I set this up;  which is what the syslog-previous was (which has the previous day before the crash?);  is this something different?

3 minutes ago, exwebjunkie said:

Hmm let me take another look - I am pretty sure that I set this up; 

Many people enable the server but overlook that to get anything actually recorded they either have to set the "Mirror to Flash" option or put the address of the Unraid server into the "Remote Syslog Server" field.

 

4 hours ago, itimpi said:

Many people enable the server but overlook that to get anything actually recorded they either have to set the "Mirror to Flash" option or put the address of the Unraid server into the "Remote Syslog Server" field.

 

I've taken a look and looks like this is setup correctly already (Mirror syslog to flash) - what are you expecting to see in the diagnostic file that isn't there?  And does the screenshot below look correct?

 

Anyone have any ideas here?

Did you post the persistent syslog?

14 hours ago, JorgeB said:

Did you post the persistent syslog?

I posted my diagnostic file - and the persistent option was already turned on (as per my screenshot above); so unsure why it would not be appearing in the file on this basis?

The syslog-previous included with the diags only covers 10 minutes of uptime, was that when the server crashed?

Have you checked your "Power Supply Idle State" in bios? Some Ryzen CPUs need it set to "typical current idle" for it to be stable in Unraid, i had to set it with my 3900x to get a stable system.

Our dear JorgeB here wrote a good summery of it here: