Hello, 

 

Recently, after two years of running fine, my Unraid server randomly reboots several times a day. 

 

I changed out the USB to a new one.

 

I updated BIOS, and updated Unraid to latest version. 

 

I have an AMD Ryzen 7 5800x, and I've tried all the usual Ryzen fixes, like disabling C States and setting Power Supply Idle Control to Typical. 

 

I've disabled XMP and also ran memtest86 for 24 hours/12 passes. 

 

I removed all plugins, changed Docker from macvlan to ipvlan , and eventually disabled Docker altogether. 

 

I booted into a live Ubuntu on a new flash drive, ran some stress tests and never had any crashes or reboots. 

 

There is nothing in the logs when it happens, the last message is Docker telling me it started successfully. This is a snippet from one of the reboots. 

 

Dec 30 08:06:28 Tower kernel: docker0: port 8(vethb4630b7) entered disabled state
Dec 30 08:06:28 Tower kernel: device vethb4630b7 entered promiscuous mode
Dec 30 08:06:33 Tower kernel: eth0: renamed from veth3086ddd
Dec 30 08:06:33 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethb4630b7: link becomes ready
Dec 30 08:06:33 Tower kernel: docker0: port 8(vethb4630b7) entered blocking state
Dec 30 08:06:33 Tower kernel: docker0: port 8(vethb4630b7) entered forwarding state
Dec 30 08:06:35 Tower rc.docker: ombi: started succesfully!

Dec 30 09:06:05 Tower unassigned.devices: Mounting 'Auto Mount' Devices...
Dec 30 09:06:05 Tower emhttpd: Starting services...
Dec 30 09:06:05 Tower emhttpd: shcmd (2679): /etc/rc.d/rc.samba restart
Dec 30 09:06:05 Tower wsdd2[7260]: 'Terminated' signal received.
Dec 30 09:06:05 Tower winbindd[7271]: [2024/12/30 09:06:05.630010,  0] ../../source3/winbindd/winbindd_dual.c:1964(winbindd_sig_term_handler)
Dec 30 09:06:05 Tower winbindd[7271]:   Got sig[15] terminate (is_parent=1)
Dec 30 09:06:05 Tower wsdd2[7260]: terminating.
Dec 30 09:06:06 Tower rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="24921" x-info="https://www.rsyslog.com"] start
Dec 30 09:06:07 Tower root: Starting Samba:  /usr/sbin/smbd -D
Dec 30 09:06:07 Tower root:                  /usr/sbin/nmbd -D
Dec 30 09:06:07 Tower root:                  /usr/sbin/wsdd2 -d -4 -6
 

I'll get the full Diag zip once I am able to reboot it.

 

Does anyone have any ideas/suggestions? 

 

Edited December 31, 20241 yr by ddumas

Attached is the diagnostic zip 

tower-diagnostics-20241230-1947.zip

Power Supply?  Cat playing with the reset button on the server?

I am leaning towards the PSU, I just find it weird that it would only be a problem in Unraid, everything works fine when in Ubuntu, even with a prolonged stress test 

Server rebooting by itself is almost always a hardware issue, also make sure this has been taken care of:

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173