Hi! I'm trying to get Unraid configured to run Plex, sonarr, radarr, etc. While I have all of that configured and running, the Unraid server itself seemingly crashes for no apparent reason, at random times. "Crash" symptoms: No web UI's accessible, trying to view system output on a monitor leaves a black screen (or if the monitor was already on, a frozen terminal). The machine still appears to be on (fans spinning, RGB on) but you can't do anything other than hard shut down and power up.

 

System Specs:
Ryzen 5 2400G (could the built-in APU be causing problems?)

16 GB RAM @ 2400Mhz

1 8TB HDD (have other drives to migrate, but need this to be stable first)

Gigabyte UD mobo  "B" (ie b450 or whatever was correct for this gen)

Nvidia 1050Ti (with the Nvidia driver plugin installed)

 

 

Some things I've done: 

Mem test - run for 33 hours, no errors found

Installed fix common problems - no errors found

I've tried tailing /var/log/syslog, persisting to a file in my share. This is the entirety of that log, viewed after a crash:

Oct 11 20:04:52 Server kernel: docker0: port 3(vethf4681b0) entered disabled state
Oct 11 20:04:52 Server avahi-daemon[2711]: Withdrawing address record for fe80::4876:3aff:feeb:30d5 on vethf4681b0.
Oct 11 20:04:57 Server kernel: docker0: port 2(veth9911c6f) entered disabled state
Oct 11 20:04:57 Server kernel: veth46164d2: renamed from eth0
Oct 11 20:04:57 Server avahi-daemon[2711]: Interface veth9911c6f.IPv6 no longer relevant for mDNS.
Oct 11 20:04:57 Server avahi-daemon[2711]: Leaving mDNS multicast group on interface veth9911c6f.IPv6 with address fe80::e0aa:a0ff:feef:c8ea.
Oct 11 20:04:57 Server kernel: docker0: port 2(veth9911c6f) entered disabled state
Oct 11 20:04:57 Server kernel: device veth9911c6f left promiscuous mode
Oct 11 20:04:57 Server kernel: docker0: port 2(veth9911c6f) entered disabled state
Oct 11 20:04:57 Server avahi-daemon[2711]: Withdrawing address record for fe80::e0aa:a0ff:feef:c8ea on veth9911c6f.
Oct 11 20:07:13 Server sshd[6004]: Connection closed by 192.168.86.20 port 49901
Oct 11 20:07:13 Server sshd[6004]: Close session: user root from 192.168.86.20 port 49901 id 0
Oct 11 20:07:13 Server sshd[6004]: pam_unix(sshd:session): session closed for user root
Oct 11 20:07:13 Server sshd[6004]: Transferred: sent 9808, received 5112 bytes
Oct 11 20:07:13 Server sshd[6004]: Closing connection to 192.168.86.20 port 49901
Oct 11 20:07:58 Server ntpd[1853]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
Oct 11 20:09:03 Server nmbd[2857]: [2021/10/11 20:09:03.379191,  0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
Oct 11 20:09:03 Server nmbd[2857]:   *****
Oct 11 20:09:03 Server nmbd[2857]:   
Oct 11 20:09:03 Server nmbd[2857]:   Samba name server SERVER is now a local master browser for workgroup WORKGROUP on subnet 192.168.122.1
Oct 11 20:09:03 Server nmbd[2857]:   
Oct 11 20:09:03 Server nmbd[2857]:   *****
Oct 11 20:09:03 Server nmbd[2857]: [2021/10/11 20:09:03.379317,  0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
Oct 11 20:09:03 Server nmbd[2857]:   *****
Oct 11 20:09:03 Server nmbd[2857]:   
Oct 11 20:09:03 Server nmbd[2857]:   Samba name server SERVER is now a local master browser for workgroup WORKGROUP on subnet 172.17.0.1
Oct 11 20:09:03 Server nmbd[2857]:   
Oct 11 20:09:03 Server nmbd[2857]:   *****
Oct 11 20:13:00 Server root: Fix Common Problems Version 2021.08.05
Oct 11 20:13:03 Server root: Fix Common Problems: Other Warning: Background notifications not enabled
Oct 12 03:40:01 Server crond[1874]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null

Played around with a few bios settings, but it's currently as stock as I can get it.

 

I've attached a server diagnostic as well. Any help on this would be greatly appreciated. Loving Unraid, and want to get it stable!

 

server-diagnostics-20211012-0952.zip

Just now, luckee_13 said:

Ryzen

 

Thanks for pointing that out @trurl

 

I've updated my bios, disabled c-states globally, and set the power at idle to typical. I've since had over 24 hours of uptime. I'm going to call this resolved for now. Thanks again