December 12, 20178 yr Hello, Bit of an unRAID newbie here, but have significant computing/IT experience knowledge (electrical engineer). I've built a server for unRAID, based on a Ryxzen 1700X and a Gigabyte GA-AB350-GAMING3 motherboard. I've read about the C-states issue causing crashes at times with Ryzen. I have not experienced that, but I have had a problem with the network interface becoming unresponsive. The server is still accessible via attached KB/monitor, although there isn't much to be done via command line. My first reaction was to try an ifdown/ifup command, but it's apparently no part of unraid. The server cannot pink any IP but its own. The server is the 6.4 RC15 release, because I need to be able to use a distinct IP address per docker, and the 6.3 stable does not support that. Any ideas on how to recover from this withoug rebooting (I don't want to keep rebuilding parity all the time), and perhaps what causes it? Is the RealTek LAN a problem? Thanks in advance.
December 12, 20178 yr You can do “ifconfig eth0 down” followed by “ifconfig eth0 up” or whatever your interface name is.
December 12, 20178 yr @TheRFMan that basically explains some of my issues... it starts like that, then becomes unresponsive from the console itself. Like it's "sleeping". Once C-State is disabled, those issues go away.
Archived
This topic is now archived and is closed to further replies.