Oreonipples Posted February 8, 2018 Share Posted February 8, 2018 (edited) Long story short I replaced a cache drive that went into read only mode not sure why I think it filled 100% and unraid killed all dockers, burned up a flash drive stupidly by inserting a internal usb header into the wrong port on the board and replaced it. Got everything up and running overnight 100% recreated configs and dockers and rebuilt plex library all worked great and then the server was unreachable today. Restart the server, its still unreachable no ip, reboot everything modem router and all switches, take switch out of loop, new Ethernet cable no luck. So I move the flash drive to different port, recreate flash drive, recreate new flash drive I bought, set manual ip, no luck. Tried not copying configs just simple basic unraid same issue. Now when I ifconfig eth0 it says no device found, this was not an issue before just no ip, a few times it got a internet ip but was not view able in the router nor accessible via http://tower/. Verified bios settings, all normal, turned off VT-D as I read something in the logs about imouu causing instability and I have no setting for imouu and still no change. So I pulled diags and am lost beyond it cant obtain ip address, and doesnt see the onboard nic. I ordered a new intel Pro\1000 as Im betting my onboard nic died but curious if im just dumb. Hardware Motherboard: Asus Sabertooth x58 Nic: Realtek 8110sc CPU: I7 960 Ram: 18gb ddr3 1600 Drives: 6 WD RED 8tb Cache: Sandisk 960gb ultra 2, Sandisk 240gb ultra 3 Nic:realtek 8110sc PSU: Corsair 850 USB Drive: multiple flash drives tried and ports all usb 2.0 as this board wont boot off 3.0 Thanks for any insight tower-smart-20180207-0110.zip tower-diagnostics-20180208-0054.zip Turns out it was a failed ethernet port, something tells me my usb header fried it, intel 2 port 1000 fired right up with an Ip and im up and running! FYI a Dlink 830T does not have a working driver in Unraid 6.4.1. Thanks Johnnie for your support. Edited February 11, 2018 by Oreonipples Whoops forgot diags... Quote Link to comment
JorgeB Posted February 8, 2018 Share Posted February 8, 2018 You posted a SMART report instead of the diags. Quote Link to comment
Oreonipples Posted February 8, 2018 Author Share Posted February 8, 2018 (edited) Updated with diagnostic zip. Additional installed a Dlink 830t and the issue persist, I did disable the onboard nic in bios, tried static again no luck. Ip address it obtains is 169.254.79.167 Edited February 8, 2018 by Oreonipples Quote Link to comment
JorgeB Posted February 8, 2018 Share Posted February 8, 2018 There's only one NIC detected and unRAID has no driver for it: 07:01.0 Ethernet controller [0200]: I-O Data Device, Inc. Device [10fc:8167] (rev 10) Subsystem: Young Micro Systems Device [1053:820d] The onboard NIC should work, though Intel > Realtek Quote Link to comment
Oreonipples Posted February 9, 2018 Author Share Posted February 9, 2018 So new flash drive, unraid 6.4.0 instead of 6.4.1 still with new dlink installed and onboard disabled. Trying onboard only again now. tower-diagnostics-20180208-1610.zip Quote Link to comment
Oreonipples Posted February 9, 2018 Author Share Posted February 9, 2018 This is the log with new flash drive, unraid 6.4.0 with only on board realtek. My intel nic should arrive tomorrow but this server was working for nearly 7 months and this configuration worked for 12 hours before networking seemed to die so Im afraid its something bigger. tower-diagnostics-20180208-1618.zip Quote Link to comment
JorgeB Posted February 9, 2018 Share Posted February 9, 2018 The onboard NIC is detected but it can't get an IP address and it's spamming the log with link down/up messages, so probably failing: Feb 8 16:17:41 Tower dhcpcd[1631]: br0: carrier lost Feb 8 16:17:41 Tower kernel: r8169 0000:07:01.0 eth0: link down Feb 8 16:17:41 Tower kernel: r8169 0000:07:01.0 eth0: link down Feb 8 16:17:41 Tower kernel: r8169 0000:07:01.0 eth0: link down Feb 8 16:17:41 Tower kernel: r8169 0000:07:01.0 eth0: link down Feb 8 16:17:41 Tower kernel: r8169 0000:07:01.0 eth0: link down Feb 8 16:17:41 Tower kernel: r8169 0000:07:01.0 eth0: link down Feb 8 16:17:41 Tower kernel: r8169 0000:07:01.0 eth0: link down Feb 8 16:17:41 Tower kernel: r8169 0000:07:01.0 eth0: link down Feb 8 16:17:42 Tower kernel: r8169 0000:07:01.0 eth0: link down Feb 8 16:17:42 Tower kernel: r8169 0000:07:01.0 eth0: link down Feb 8 16:17:42 Tower kernel: r8169 0000:07:01.0 eth0: link down Feb 8 16:17:42 Tower kernel: r8169 0000:07:01.0 eth0: link down Feb 8 16:17:42 Tower kernel: r8169 0000:07:01.0 eth0: link down Feb 8 16:17:42 Tower kernel: r8169 0000:07:01.0 eth0: link down Feb 8 16:17:42 Tower kernel: r8169 0000:07:01.0 eth0: link down Feb 8 16:17:42 Tower kernel: r8169 0000:07:01.0 eth0: link down Feb 8 16:17:42 Tower kernel: r8169 0000:07:01.0 eth0: link down Feb 8 16:17:42 Tower kernel: r8169 0000:07:01.0 eth0: link down Feb 8 16:17:42 Tower kernel: r8169 0000:07:01.0 eth0: link down Feb 8 16:17:42 Tower kernel: r8169 0000:07:01.0 eth0: link down Feb 8 16:17:42 Tower kernel: r8169 0000:07:01.0 eth0: link down Feb 8 16:17:42 Tower kernel: r8169 0000:07:01.0 eth0: link down Feb 8 16:17:42 Tower kernel: r8169 0000:07:01.0 eth0: link down Feb 8 16:17:42 Tower kernel: r8169 0000:07:01.0 eth0: link down Feb 8 16:17:42 Tower kernel: r8169 0000:07:01.0 eth0: link down Feb 8 16:17:42 Tower kernel: r8169 0000:07:01.0 eth0: link down Feb 8 16:17:42 Tower kernel: r8169 0000:07:01.0 eth0: link down .... Feb 8 16:17:58 Tower kernel: r8169 0000:07:01.0 eth0: link up Feb 8 16:17:58 Tower kernel: r8169 0000:07:01.0 eth0: link up Feb 8 16:17:58 Tower kernel: r8169 0000:07:01.0 eth0: link up Feb 8 16:17:58 Tower kernel: r8169 0000:07:01.0 eth0: link up Feb 8 16:17:58 Tower kernel: r8169 0000:07:01.0 eth0: link up Feb 8 16:17:58 Tower kernel: r8169 0000:07:01.0 eth0: link up Feb 8 16:17:59 Tower kernel: r8169 0000:07:01.0 eth0: link up Feb 8 16:17:59 Tower kernel: r8169 0000:07:01.0 eth0: link up Feb 8 16:17:59 Tower kernel: r8169 0000:07:01.0 eth0: link up Feb 8 16:17:59 Tower kernel: r8169 0000:07:01.0 eth0: link up Feb 8 16:18:03 Tower kernel: net_ratelimit: 507 callbacks suppressed Feb 8 16:18:03 Tower kernel: r8169 0000:07:01.0 eth0: link up Feb 8 16:18:03 Tower kernel: r8169 0000:07:01.0 eth0: link up Feb 8 16:18:03 Tower kernel: r8169 0000:07:01.0 eth0: link up Feb 8 16:18:03 Tower kernel: r8169 0000:07:01.0 eth0: link up Feb 8 16:18:03 Tower kernel: r8169 0000:07:01.0 eth0: link up Feb 8 16:18:04 Tower kernel: r8169 0000:07:01.0 eth0: link up Feb 8 16:18:04 Tower kernel: r8169 0000:07:01.0 eth0: link up Feb 8 16:18:04 Tower kernel: r8169 0000:07:01.0 eth0: link up Feb 8 16:18:04 Tower kernel: r8169 0000:07:01.0 eth0: link up Feb 8 16:18:04 Tower kernel: r8169 0000:07:01.0 eth0: link up Feb 8 16:18:08 Tower kernel: net_ratelimit: 500 callbacks suppressed Feb 8 16:18:08 Tower kernel: r8169 0000:07:01.0 eth0: link up Feb 8 16:18:08 Tower kernel: r8169 0000:07:01.0 eth0: link up Feb 8 16:18:08 Tower kernel: r8169 0000:07:01.0 eth0: link up Feb 8 16:18:08 Tower kernel: r8169 0000:07:01.0 eth0: link up Feb 8 16:18:09 Tower kernel: r8169 0000:07:01.0 eth0: link up Feb 8 16:18:09 Tower kernel: r8169 0000:07:01.0 eth0: link up Feb 8 16:18:09 Tower kernel: r8169 0000:07:01.0 eth0: link up Feb 8 16:18:09 Tower kernel: r8169 0000:07:01.0 eth0: link up Feb 8 16:18:09 Tower kernel: r8169 0000:07:01.0 eth0: link up Feb 8 16:18:09 Tower kernel: r8169 0000:07:01.0 eth0: link up Feb 8 16:18:13 Tower kernel: net_ratelimit: 497 callbacks suppressed Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.