I am fairly new to Unraid so please go easy!

 

I have a pretty basic set up at the moment, running a Supermicro A+ Server 5019D-FTN4 w/ 64Gb RAM. The system is primarily running as a NAS with Docker running a few things, currently reduced to just Pi-hole and Homebridge.

I've been having issues with the server randomly becoming unresponsive and requiring a reset. This initially had been fairly infrequent but recently has increased. I've tried following the advice in other posts to persist logs to flash but my `/boot/logs` directory remains empty after reset. I have attached what I have but it's not very informative.

I'm hoping I can get some help diagnosing this issue and hopefully getting some better diagnostic information 🙏

 

syslog.txt

Edited August 2, 20232 yr by frenetic-enrollment4074

Instead of that wall of text...

 

Attach Diagnostics to your NEXT post in this thread.  Diagnostics includes current syslog and many other things that help make sense of Syslog, your hardware, and configuration,  in a convenient zip file we can download and work with. 

 

Also, try again to set up syslog server. 

Sorry, I was having some weird SSO issue and the new post form was showing the signed out view (i.e. without the attachment option).

I was able to access the persisted syslog - it's absolutely huge so sharing the last 20k lines which include a period during which the system hung. I'm also attaching the diagnostic report generated since the most recent boot.

syslog_tail.txt viper-diagnostics-20230802-1732.zip

Aug  1 23:05:56 Viper kernel: macvlan_broadcast+0x10a/0x150 [macvlan]
Aug  1 23:05:56 Viper kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]

Try switching to ipvlan (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).

Thanks for the response. I can see that setting (with advanced view enabled) but it doesn't appear to be editable?

Docker service must be stopped first.

Thanks, I've done that. I'll keep an eye on it and see if it resolves the issue.

Unfortunately it's still crashing. It feels as though something is chewing up memory until the system crashes but I can't deduce what. Any ideas?

Edit: here's the most recent logs.

syslog_Aug2.txt

Edited August 2, 20232 yr by frenetic-enrollment4074

Unfortunately there's nothing relevant logged, this usually points to a hardware issue, one thing you can try is to boot the server in safe mode with all docker/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.

Thank you for the reply. I've been playing around starting in safe mode, running memtest etc. to try and figure this out. One thing I've noticed is that when running Unraid for a while, the CPU usage seems very high even with docker etc. all disabled. Looking at htop it seems that the 'smartctl_type' and '/webGui/scripts/notify get' seem to be pulling 100%+ I think the former is the S.M.A.R.T. test process which is odd as the Web UI doesn't indicate a test is running. I'm not sure about the latter?

Marking as solved. My RAM was faulty and replacing has solved the issue.