I've recently built a machine to host a Unraid server. I did not do my research since I was not sure I was going with Unraid, just knew my old Windows share box was getting slow and glitchy. I am using a Ryzen 5 1600 on a Gigabyte B350 gaming MB with 16GB. Disks are 4 Seagate Ironwolf 4TB with 2 Sandisk 240GB SSD disks for cache. Currently has a 970gfx card just for local monitor. Probably will be going away once system is stable.

 

HD's are connected all to the MB. SSD's on the Raid capable (but currently set to normal) ports, HD's on the remaining 4 ports. Static IP assigned. Active dockers had been binhex's Plex pass, Sonarr and Sabnzbd+ as these are the main functions for this box aside from the NAS functionality. Probably run a couple Linux VM's for work related tasks.

 

I installed and setup the 6.3.5 release and saw when running the common issues plugin that I needed 6.4 to properly support Ryzen. So I went ahead and installed 6.4.0-rc13 day before yesterday. Looked OK for a few hours and got about 1.5TB moved over. Left running overnight, seemed OK. After coming back home today around 6PM, machine was locked up, no response from the console, nothing. Console was only showing the default login message from initial bootup, no messages on screen.

 

Logged into the forums and saw rc14 was out so went ahead and updated it. Also enabled the extra logging in common issues plugin. About 2 hours later, while not using the NAS at all, I heard the machine reboot.

 

Not smart enough to know what to look for in the logs yet. Help?

tower-diagnostics-20171123-2027.zip

FCPsyslog_tail.txt

Edited November 24, 20178 yr by Genom

Did you try this- https://forums.lime-technology.com/topic/61129-ryzen-freezes/?tab=comments#comment-599763

Not sure if its still necessary with RC14 or not.

7 minutes ago, wgstarks said:

Did you try this- https://forums.lime-technology.com/topic/61129-ryzen-freezes/?tab=comments#comment-599763

Not sure if its still necessary with RC14 or not.

 

I saw the post, but I do not know how to add the command to the syslinux. I tried just adding it with a , at the end of the append line, but it did not work. If anybody can post a sample of what it should look like, I would be grateful.

scroll down and you'll see this example. or just click the link.

Booting now. Will re-enable the logger and see how it goes. Thank you.

Lots of issues with Ryzen and Linux (glad I don't have one).  Windows and Ryzen too from what I read. Hopefully AMD will start to get some of the bugs out soon.

It's not too bad. I turned off c states and my ryzen machine has been really stable. New platforms come with some bumps.

Sent from my SM-G955U using Tapatalk

9 hours ago, wgstarks said:

Lots of issues with Ryzen and Linux (glad I don't have one).  Windows and Ryzen too from what I read. Hopefully AMD will start to get some of the bugs out soon.

 

 No, that's not true. There are a few issues that remain and a lot that have been fixed. It seems that people who don't use Ryzen have more negative things to say about it that those who do, which is a shame.

Well, after adding the line to the startup, and disabling C states, system has been up 48 hours, it's longest so far, while having the wanted dockers enabled and running, as well as setting up a couple Centos VM's for work related things that have been up and down a few times (on purpose) with no issues.

 

Once I hit a week uptime  I will test removing the append line and see if that changes anything for me and post an update.

 

Unless rc15 is out by then. I am a sucker for updating.