February 16, 20251 yr Hi All. Be gentle. Old timer here frustrated trying to decide if I should give up on the idea of using my Ryzen Board for my Unraid Server. I had been using an older Intel Board and moved recently to using a newer Ryzen board. At the same time I moved up to the latest version 7.0.0 I have had issues since the first day which started with what seemed to be the server falling off the network. I'm unsure if this was actually the original issue as I didnt have a local Monitor or keyboard on the server. I have noticed since that the output to the monitor is lost as well as caps lock on/off has no effect (no indication of life on the keyboard). The bios was updated prior to utilising for use with Unraid. I have also looked at P-States in the bios and believe I set this up using someone elses post. Attached is a diagnostics file from my server. Syslog has also been enabled, but shows nothing meaningful in my eyes with the last event logged seeming to be different each time. I have also tried rolling back, but saw no change. Other testing: * Run in safe mode, no gui - Crash * MemTest - Passed with no issues Feb 12 23:01:36 Tower webGUI: Successful login user root from 192.168.1.215 Feb 13 03:37:16 Tower kernel: md: sync done. time=31175sec Feb 13 03:37:16 Tower kernel: md: recovery thread: exit status: 0 <---------- I reboot the server here Feb 13 22:00:14 Tower unassigned.devices: Mounting 'Auto Mount' Devices... Feb 13 22:00:14 Tower emhttpd: Starting services... Feb 13 22:00:31 Tower unassigned.devices: Waiting 5 secs before mounting Remote Shares... Feb 13 22:00:35 Tower rc.docker: homebridge: started succesfully! Feb 13 22:02:12 Tower webGUI: Successful login user root from 192.168.1.215 <-------- I notice it's crashed again so reboot Feb 14 17:04:36 Tower unassigned.devices: Mounting 'Auto Mount' Devices... Feb 14 17:04:36 Tower emhttpd: Starting services... Feb 14 17:04:36 Tower emhttpd: shcmd (50): /etc/rc.d/rc.samba restart Later... Feb 14 18:44:21 Tower root: ACPI action left is not defined Feb 14 18:53:59 Tower webgui: Successful login user root from 192.168.1.107 Feb 14 21:20:56 Tower monitor_nchan: Stop running nchan processes <-------- I notice it's crashed again so reboot Feb 15 08:24:48 Tower rc.rsyslogd: Syslog server daemon... Started. My next step would be to put the boot usb back in the original board again, minus the hard disks attached and see if it stays up, if so then connecting the raid drives to this board again and giving up on the idea of using this Ryzen board.. But I thought I'd post here first to see if anyone has any ideas? Thanks Grant (old guy from down under - NZ) tower-diagnostics-20250214-1812.zip Edited February 16, 20251 yr by grantt
February 16, 20251 yr you may need to install the amd reset plugin due to a known issue called the amd reset bug. https://github.com/ich777/unraid-amd-vendor-reset
February 16, 20251 yr Make sure this has been taken care of: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173
February 16, 20251 yr My first Unraid server was built with a repurposed 1500X. I had intermittent freezes just as you are seeing. First gen Ryzen CPUs had issues running in Linux, later generations are much less prone to this lockup issue. I was able to resolve it by following the FAQ I'll link below. Two things to check for in your BIOS settings: Power Supply Idle Control = Typical Idle Current Set DRAM speed to 1866 (currently it looks as you have 2400) The Power Supply Idle Control prevents the power supply from idling too low when there is not much demand on it. Unfortunately, that isn't enough power to keep the CPU running. If you set to Typical Idle Current, you can also set the C-States back to auto, and allow the CPU to handle power management. Seems you have mismatched sets of DRAM. Usually not ideal, but this shouldn't be an issue in this case. The limiting factor isn't the DRAM, but rather the Infinity Fabric of the CPU (AMD's name for the Ryzen's internal memory controller and bus). See the chart in the FAQ. Your configuration most likely requires it to be set to 1866 (1st Gen, 4 DIMM, and I'll assume Dual Rank for Kingston). You may be able to bump it up to 2133 if 1866 resolves the issue, but honestly there is little to be gained by doing so. It is a server, not a top end gaming rig. Edited February 16, 20251 yr by ConnerVT typo
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.