April 6, 201115 yr Hey all, had a power flicker yesterday that shut the server down for a few seconds (no UPS yet). Fired back up and when I went to Tower in the browser there were a few drives that would not mount. Rebooted and network will not come up, could see it start a parity check. The lights on my router, Dlink DIR-655, on that port was on then I watched it just shut off. I plugged and unplugged the cable and no go. Switched ports to another that is working with my main PC and no go. Changed cables and no go. No lights on my Ethernet port on the motherboard. I do an ifconfig and eth0 shows up but with no IP address. I disabled and re-enabled in the bios and same thing. Attached is my syslog These are the only network lines I could find Apr 4 12:57:06 Tower kernel: eth0: RTL8168d/8111d at 0xf847e000, 00:16:17:d3:33:84, XID 081000c0 IRQ 29 Apr 4 12:57:06 Tower ifplugd(eth0)[1761]: ifplugd 0.28 initializing. Apr 4 12:57:06 Tower kernel: r8169: eth0: link down Apr 4 12:57:06 Tower ifplugd(eth0)[1761]: Using interface eth0/00:16:17:D3:33:84 with driver <r8169> (version: 2.3LK-NAPI) Apr 4 12:57:06 Tower ifplugd(eth0)[1761]: Using detection mode: SIOCETHTOOL Apr 4 12:57:06 Tower ifplugd(eth0)[1761]: Initialization complete, link beat not detected. JetWay JHZ03-GT-LF Motherboard Anyone have any ideas? I've got a new router and a new network card coming tomorrow, I needed to upgrade my router anyways so gonna give that a try. I'm at a loss thanks Josh syslog.txt
February 1, 201412 yr This is an ancient thread, but I'm wondering if you ever figured this out. I'm also getting "r8169 eth0: link down", even though my BIOS can check for updates over the internet just fine.
Archived
This topic is now archived and is closed to further replies.