I recently built a new server, but its become unresponsive a number of times over the last week. First time was a day after I got it up and running. It ran a week fine, then over the last 36 hours it has become unresponsive 4 times. Ive looked at the logs and don't see anything to me that looks like the cause. 

 

Things I think might be of note. 

• I moved my unraid install from my old server, it was running fine prior
• I see the signs of a failed disk, but I know I have a WD RED that was DOA still in the server. Ive been trying to get preclear done on the others before RMA. 
• There are two hard reboots in the syslog file. 1st time I think is on Jan  6 23:42:50, but there wasn't much of a gap, and I am way out of my comfort zone with these logs. The 2nd time was Jan  7 09:22:02. Fairly confidant on that because of the gap of logs.  

 

Any help would be appreciated, 

 

ozunraid-diagnostics-20240107-1011.zip syslog-192.168.21.90.log

Edited January 7, 20242 yr by southloven

Adding to this, I realized I had fallen behind on unraid updates, and it looks like it may have been that that is causing my issue.  

 

I found where JorgeB is recommending switching to ipvlan, but I also noticed after I uploaded this that there was a related fix common issues that sent me to https://docs.unraid.net/unraid-os/release-notes/6.12.4/#fix-for-macvlan-call-traces with fix options that appied to me (Ubiquity user) in the 6.12.4 update. 

There are macvlan call traces, you can switch to ipvlan or if you really need macvlan disable bridging for eth0.

After swapping around every hardware component, and having a few false hopes of finding a resolution, I eliminated everything except the processor. 

 

RMAed the Processor, and it has been running for a week without a crash.  It had gotten so bad it was crashing every 1-2 days and I was seeing errors in the logs that were not causing crashes. Logs have been clean for the last 7 days also. Glad to have a reliable server up and running again.