chadjj

Joining the list of people affected. Updated my BIOS and it broke my Windows 10 gaming VM passing through GTX 1660ti. I am using Asus X370-Pro with Ryzen 7 1700, BIOS v4801, Release date 04/25/2019. Running unRAID, version 6.7.1-rc1. Downgraded to BIOS 4207 and everything is working again.

Hey Everyone, A quick status update on my setup. Since I have updated to PRIME X370-PRO BIOS 0604 with Global C-State disabled I have seen positive results. Current up-time is 17hrs, 10mins which is the longest stretch I have seen. If all continues to go well it seems as though AMD AGESA microcode update and Disabling Global C-State have resolved my unRAID hanging issues. Once I have had some considerable up-time I will try to re-enable Global C-State and evaluate that result. Hope everyone else is seeing similar success. -Chad

Hi Bill, I have a very similar setup however haven't made it past 8 hrs of up time. I have global C-State disabled no over clocking straight stock and system hangs. Also on unRAID 6.3.3. ASUS X370-Pro, Corsair 16GB kit 3000, same one AMD sent out for press release which is a differentiating factor. Ran memtest86 with no errors. I am running several dockers so they may be triggering something different. Plex (official), ruTorrent (binhex-rtorrentvpn), SickRage (binhex-sickrage), CouchPotato (binhex-couchpotato-git), PlexPy (linuxserver) also tried Deluge in the past but not on Ryzen. If your up time is solid may be docker related. This would be a new issue based on past results from everyone. I am looking forward to AGESA this week and will report back results then. -Chad

Excellent. Hopefully I see positive results once my microcode update hits this week. Chad

Just checked the ASUS site and no update on my board yet. Looks like ASRock is ahead of the game. 100 hours of uptime is very positive. Are you planning on adding 1 docker at a time? Chad

Hi Paul, With AGESA being addressed it's at least one less variable to factor. Agreed it may take MB manufacturers a while to get their releases out but by the way the article reads AMD has already provided the code and boards should have an April 11 BIOS update. We will see... Possibly updating unRAIDs Linux Kernel to 4.10.8 or 4.11rc5 would be an interesting test for the LimeTech team. Challenge is their NAS stability philosophy, which makes sense to be on the most reliable release. Experimental or early releases are not really an area of focus but could resolve our Ryzen issues. Prioritizing resources on Ryzen may not be a high priority as well seeing that AMD is in the minority of market share. A post was made earlier about having 2 streams but that would be difficult to manage. Quick link to Linux Kernels https://www.kernel.org/ Chad

Hey Paul, I did some digging today on when we can expect our AGESA CPU update for our boards and that should come around April 11th. I found an article today discussing it. It's in Spanish but Google translate works fine. Earlier you indicated things being related to C-State but this is one more potential issue being resolved. Fingers crossed. https://translate.google.ca/translate?hl=en&sl=es&u=http://www.hd-tecnologia.com/confirmada-nueva-bios-con-agesa-1004-para-los-ryzen-5-ryzen-7-aun-no-tienen-esta-actualizacion/&prev=search Chad

Hi Jim2003, How is your up time a couple days later? Chad

Hey Paul, I was away from the house but at some point server became non responsive again. C-State was disabled, new ASUS Prime x370-PRO BIOS 0515 installed. I checked the console and it was responsive. You could type but nothing happened when you did. Checked the logs nothing was captured. So in my instance disabling C-State did not result in increased up time. unRAID became unresponsive in under 3 hrs. Chad

Hi Paul, I completed the update with 6.3.3 yesterday on my old Intel machine and as usual no issues so far. You are correct that 4.9.19 doesn't seem to have any Ryzen related updates. I will move my drives back into my Ryzen system make the C-State change and will keep you posted if I run into any crashes. I looked to see if there were any other settings related to sleep on my board and didn't notice anything. There is also a BIOS update that came out yesterday so hopefully that cleaned some things up. I'll keep you posted. Thanks, Chad

Hi Paul, Hows your up time now that your no longer testing? Thanks, Chad

Asus released a new BIOS for my Prime x370-Pro so they may have for your board as well. Chad

Hey Guys, I found some good news posted today at the following link. We can look forward to a BIOS update for our motherboard to address the AMD CPU freezing issues early April. https://www.bit-tech.net/news/hardware/2017/03/31/amd-agesa-update-april/1 Chad

Hi Paul, Correct, I am no longer running any VM's in the background and have had the system lock up twice since my last post. Both times frozen at the boot console. With no logs to report. Thanks, Chad

Hi Paul, It took several attempts to get a Win 10 VM working a few days ago. I was actually compiling screenshots to share in the forums on how it would hang at the UEFI and wouldn't load the .iso. I had past Windows 10 .iso's at different dates in time and then pulled down a brand new one from Microsoft and that one worked. I don't know what was different from the other 2? Maybe they were corrupt over time not sure. So yes, I have had Windows 10 working but in trying to diagnose I started paring back all services running on unRAID. Troubleshooting with the fewest services running in the background 1 at a time to pinpoint the cause. Like many of us coming up with few answers. Uptime 12hrs, 55mins. I have not changed anything in the environment since the last lock up but yet to hit 24hrs. Last lockup was at 5:55am so if it happens again at that time I will dig into what happened within that window. PS - To clarify my communication with the LimeTech team, they asked me what RAM I was using as they were using Gskill and had similar issues and were considering RMA'ing the RAM thinking it could be defective. I am making the assumption that it's unlikely we are having similar issues with different RAM and both coincidentally bad so theirs is likely ok as I'm not showing any memtest errors. I would find it very strange that all members of the unRAID community are reporting bad memory. Thanks, Chad