I am running a Ryzen build.. and I have run into the C-State issue. It's currently disabled in the BIOS, mainly because I haven't had the opportunity to update the thing to the newest one from AsRock, being as how it's constantly in use with Plex and what not. (Gotta love family members, most impatient people I've ever met.) Other than that, I've managed to get about 14-15 days out of the system, before either taking it down to do something like move the actual server or update to the next RC 6.4.x. It's stable otherwise.. here's what I'm running:

 

1 x Mediasonic HF2-SU3S2 4 bay drive enclosure with:
2 x Seagate BarraCude 2TB drives
2 x WD Black 1 TB drives

 

1 x CORSAIR Carbide Series ATX mid tower case with:
1 x CORSAIR RM750X 750W 80+ Gold SLI/Crossfire ready power supply
1 x ASRock Fatal1ty AB350 Gaming K4 motherboard
1 x AMD Ryzen 5 1600 3.2GHz CPU
2 x CORSAIR Vengeance LPX 16GB DDR4 2400 bundles (32GB total)
2 x Seagate IronWolf 4TB drives (1 for parity)
2 x Crucial MX300 2.5" 275GB SATA 3 SSDs (2 x cache)
1 x MSI GeForce GTX 1060 3GT OC 3GB video card (pass-thru to Win10)
1 x Sapphire Radeon HD 4870 1GB video card (from old PC, for unRAID/whatever)
1 x StarTech PEXESAT3221 PCI-E SATA 3 2 int/2 ext SATA card (Driving the enclosure)

Just an added point of reference, under RC14 with a AB350-Gaming 3-CF from Gigabyte MB, disabling C-State in the BIOS has me at 12 days uptime with a variety of dockers/plugins/VM's

 

There has been a MB BIOS update since I set it up, but I have not loaded it yet as it only states it supports additional CPU's and my Ryzen 5 1600 is nothing special.

What is strange is I'm sure AMD is aware of this issue yet there hasn't been a bios update towards it, Asus has just released an new update last week but doesn't fix ram compatibility or any issue I'm aware off.

Just chiming in here:

 

Ryzen 1700
Asrock AB350M Pro4, last boot was when I updated to bios version 3.30

For what it's worth, my PSU is the Corsair RM550x.

 

I have global C-states enabled. Before changing it to "enabled" it was on "auto" by default whatever that means. I don't know if there's another setting for C6 states? and if there is I don't know what the setting is on right now unfortunately.

 

It used to crash within 4-7 days. I'm on 8 days and 17 hours right now which is a new record for me.

Edited December 15, 20178 yr by JohanSF

6 hours ago, JohanSF said:

Just chiming in here:

 

Ryzen 1700
Asrock AB350M Pro4, last boot was when I updated to bios version 3.30

For what it's worth, my PSU is the Corsair RM550x.

 

I have global C-states enabled. Before changing it to "enabled" it was on "auto" by default whatever that means. I don't know if there's another setting for C6 states? and if there is I don't know what the setting is on right now unfortunately.

 

It used to crash within 4-7 days. I'm on 8 days and 17 hours right now which is a new record for me.

Same motherboard, left c-states on auto and have never had a crash

on Asus prime x370 pro with the latest bios(Dec/8/17), when on-board LAN is disabled motherboard freezes at boot, I did a hard reset 3  times but didn't work. Once re-enabled the system worked fine. Anyone with the same motherboard facing the same issue?

On ‎2017‎年‎12‎月‎17‎日 at 5:39 AM, PSYCHOPATHiO said:

on Asus prime x370 pro with the latest bios(Dec/8/17), when on-board LAN is disabled motherboard freezes at boot, I did a hard reset 3  times but didn't work. Once re-enabled the system worked fine. Anyone with the same motherboard facing the same issue?

 

Confirm same, just black screen after BIOS post.

Edited December 18, 20178 yr by Benson

Very interesting regarding the the on-board NIC as I don't experience this issue.  My hardware is listed in my signature.  I didn't check the BIOS, but in unRAID network settings only eth0 and eth1 are shown; connected as bond0 using 802.3ad(4), static IP, default MTU and IPv4 only.  After a BIOS update and when I forget to disable the on-board NIC, it shows up as eth2 and disconnected within network settings.  I still have C-State disabled and using BIOS v3401.   I'm using the following Intel network card:

 

https://www.amazon.com/gp/product/B000BMZHX2/ref=as_li_ss_tl?ie=UTF8&psc=1&linkCode=ll1&tag=orf0f-20&linkId=09736a7076509a2c7dc550e74397b85b

 

 

22 minutes ago, luisv said:

After a BIOS update and when I forget to disable the on-board NIC, it shows up as eth2 and disconnected within network settings.

 

Same issue found, it should be problem of unRAID.

 

I have an add-on Intel LAN (onboard also Intel), seems the add-on have higher piroty, so unRAID will default addon was 1st NIC and onboard will be 2nd NIC.

 

As I use the onboad for gateway NIC, so I need swap both NIC's order.

Problem occur, if I upplug the add-on, then the wrong config will apply to onboard NIC, even I re-plug the add-on will be same.

 

And the trouble was I need fix it by command prompt, because web GUI won't available even local.

Edited December 18, 20178 yr by Benson

10 minutes ago, Benson said:

 

Same issue found, it should be problem of unRAID.

 

I have an add-on Intel LAN (onboard also Intel), seems the add-on have higher piroty, so unRAID will default addon was 1st NIC and onboard will be 2nd NIC.

 

As I use the onboad for gateway NIC, so I need swap both NIC's order.

Problem occur, if I upplug the add-on, then the wrong config will apply to onboard NIC, even I re-plug the add-on will be same.

 

 

Under network settings, interface rules, only 2 are listed... eth0 and eth1.   So unRAID isn't seeing the on-board NIC which is an Intel i211AT chipset . 

Edited December 18, 20178 yr by luisv

8 minutes ago, Benson said:

I have an add-on Intel LAN (onboard also Intel), seems the add-on have higher piroty,

 

When you have multiple ethernet ports in your system, you can use the settings under "Network Rules" to define which interface (=eth0) is used for managing unRAID itself.

As long as your physical interfaces don't change (i.e your are not adding more interfaces or removing interfaces), the eth0 selection is remembered.

Thanks both, I will try "Network rule" setting later.

16 minutes ago, Benson said:

seems the add-on have higher piroty, 

I've noticed the same and caused me some problems but I got used to it. Once you install a network card it will become eth0, so I have to assigned the main nic a dynamic ip if i needed to change network cards or I'll be locked out.

Just check, I change the order was by "Network rules". So once I have hardware change, it will got same problem again.

For my case, this should be no fix currently, because my addon NIC run-in different VLAN and this VLAN haven't DHCP.

 

unRAID should remember the MAC address according the config, if no gateway NIC, it shouldn't change other pre-define NIC setting and their order.

 

 

Edited December 18, 20178 yr by Benson

When unRAID is started the udev process does the discovery of all available hardware and makes assignments according to how hardware "responds". This has the effect that hard disk or interface assignments can change between system reboots. The hard disk assignment is solved by referencing to device names which don't change. Interface assignment is solved by reloading the interface hardware list with a "known" one and let udev rediscover the interfaces. This works as long as hardware doesn't change, but suppose you move to a new motherboard with completely different interfaces, in this case any previous assignments are not applicable anymore.

 

In case you add a new interface to your system and you have already 2 or more existing interfaces, the current eth0 selection should stay as is. When the system is expanded from 1 interface to 2 or more interfaces there is no selection remembered and eth0 selection need to be set after all interfaces are operational.

 

Ps. The default network configuration caters for this expansion, since it is set as a bonding interface which may have up to 4 members.

 

Edited December 18, 20178 yr by bonienl

Hmm, was going to move from my dual e5 2670 system to a single Ryzen 5 1600 (dont need that much cpu power and i want something smaller/quieter/more efficient) but now i am not sure if i should. (I already have the Ryzen hardware from a different build so i was just going to move everything over to it)

 

Wouldnt be doing any gpu passthrough but i do run a few VM's on the server (plex, minecraft server) and 1 docker app.