nandrico Posted September 25, 2015 Share Posted September 25, 2015 System info... onboard lan Atheros AR8161L http://h20564.www2.hp.com/hpsc/doc/public/display?docId=c03635878 The system works for 20 sec then the network can no longer communicate. I have tried different switches. If I reboot system with a windows 10 drive the ethernet works fine. Plug unraid in and it only works for a few sec after boot. Initially it seemed to work long enough to register with a basic license. If I just login in locally via root and attempt to ping the local router it works until I attempt to pull up the system via the browser from another machine. Once I connect the local machine loses connection. I tested it and allowed the local machine to ping for a few min. Once the browser session is initiated the network stops working. What am I doing wrong? Thanks Link to comment
itimpi Posted September 25, 2015 Share Posted September 25, 2015 After the problem has occurred and you have logged in via root, type the command diagnostics This will create a diagnostics ZIP file in the logs folder on the flash drive that you can then post here so that we can see if we can spot an issue. Link to comment
nandrico Posted September 25, 2015 Author Share Posted September 25, 2015 See attached... Thanks tower-diagnostics-20150925-0939.zip Link to comment
itimpi Posted September 25, 2015 Share Posted September 25, 2015 See attached... Has the problem actually occurred before you took that diagnostics file? The syslog in it is less than 30 seconds long so it seems possible you may have created it before the problem happened? The syslog shows the Ethernet coming up and does not indicate a problem. Link to comment
nandrico Posted September 25, 2015 Author Share Posted September 25, 2015 You're right. I didn't let it fail. I just redid another diag after it failed - see attached... Thanks tower-diagnostics-20150925-1004.zip Link to comment
itimpi Posted September 25, 2015 Share Posted September 25, 2015 I cannot see any network errors in that syslog. It appears the network came up find on 192.168.1.60 and there is no subsequent errors shown in the syslog. One slightly strange thing (although probably not related) is that device sdb, sdc, sdd and sde are all reporting "No medium found" errors. Any idea what those devices might relate to? At the point where the network appears to have failed what is the output of the 'ifconfig' command? Also what happens if you try the command: ping 192.168.1.1 Link to comment
nandrico Posted September 25, 2015 Author Share Posted September 25, 2015 It's the weirdest thing. It will ping until I initiate a browser connection from another machine. Then it goes into I can't see anything mode. I took pictures of the screen... https://goo.gl/photos/vRkqZHMYXQqmznG46 Link to comment
nandrico Posted September 25, 2015 Author Share Posted September 25, 2015 Unraid must not like this onboard ethernet. I rebooted with a win 10 hd see attached for dev mgr. The system is rock solid same network and no disconnect. It almost seems like the unraid driver can't negotiate Link to comment
itimpi Posted September 25, 2015 Share Posted September 25, 2015 It is possible I guess. From what I have seen most people seem to use Realtek (typically on the motherboard) or Intel for their Ethernet connections. Having said that unRAID is recognising the card and getting an IP address for it so what should be the relevant drivers are present. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.