I have lost the network connection to my unRAID movie server. When I type ifconfig eth0 I get:

eth0: error fetching interface information: Device not found

 

I was trying to get my a 3in5 caddy working last night:

http://www.scsi4me.com/snt-sas3051b-3x5-25-bays-to-5-sas-sata-hdd-hot-swap-internal-sas-cage.html

 

After trying to work out if it was my caddy (I have had it for a while but not tried it yet) or my supermicro card that was the problem I found a little switch on the front of the caddy that you need a pen to turn on. After that it fired up and the hard drive in the caddy mounted fine.

 

After shutting down and put the casing back together and rebooting I lost my network connection to the server. It doesn't like up on the network hub. I have tried different cables and ports on the hub to be sure it's not that. The lights on the ethernet port on the server are lit.

 

I'm not sure how to determine wether it's the motherboard or the unRAID software. I.m running 4.7 and the motherboard is a ASRock 880GM-LE. Both having been running pretty good since July last year.

 

I have attached my syslog:

syslog-20120417-191843.txt.zip

Have you tried without caddy or card? How do you get the syslog of the server?

 

The LAN-port seems to be disabled.

The network card is part of the motherboard. I also tried it with the caddy turned off.

 

I turned off the server using 'powerdown', removed the thumbdrive and copied the contents to get the syslog.

Just comparing a log from yesterday when it was working and one from when it wasn't

 

Working:

Apr 17 14:26:47 Tower ifplugd(eth0)[1516]: ifplugd 0.28 initializing.
Apr 17 14:26:47 Tower ifplugd(eth0)[1516]: Using interface eth0/00:25:22:82:2E:F3 with driver <r8169> (version: 2.3LK-NAPI)
Apr 17 14:26:47 Tower ifplugd(eth0)[1516]: Using detection mode: SIOCETHTOOL
Apr 17 14:26:47 Tower ifplugd(eth0)[1516]: Initialization complete, link beat detected.
Apr 17 14:26:47 Tower kernel: r8169: eth0: link up
Apr 17 14:26:47 Tower kernel: r8169: eth0: link up
Apr 17 14:26:47 Tower ifplugd(eth0)[1516]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Apr 17 14:26:47 Tower logger: /etc/rc.d/rc.inet1:  /sbin/ifconfig eth0 192.168.0.200 broadcast 192.168.0.255 netmask 255.255.255.0
Apr 17 14:26:47 Tower logger: /etc/rc.d/rc.inet1:  /sbin/route add default gw 192.168.0.1 metric 1
Apr 17 14:26:47 Tower ntpd[1553]: ntpd [email protected] Wed Jan 14 23:46:25 UTC 2009 (1)
Apr 17 14:26:47 Tower ifplugd(eth0)[1516]: client: Starting NTP daemon:  /usr/sbin/ntpd -g
Apr 17 14:26:47 Tower ntpd[1554]: precision = 1.000 usec
Apr 17 14:26:47 Tower ntpd[1554]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
Apr 17 14:26:47 Tower ntpd[1554]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
Apr 17 14:26:47 Tower ntpd[1554]: Listening on interface #1 lo, 127.0.0.1#123 Enabled
Apr 17 14:26:47 Tower ntpd[1554]: Listening on interface #2 eth0, 192.168.0.200#123 Enabled
Apr 17 14:26:47 Tower ntpd[1554]: kernel time sync status 0040
Apr 17 14:26:47 Tower ntpd[1554]: frequency initialized 23.115 PPM from /etc/ntp/drift
Apr 17 14:26:47 Tower ifplugd(eth0)[1516]: Program executed successfully.
Apr 17 14:26:47 Tower rpc.statd[1568]: Version 1.1.4 Starting
Apr 17 14:26:47 Tower emhttp: unRAID System Management Utility version 4.7

 

Not Working:

Apr 17 18:48:04 Tower ifplugd(eth0)[1512]: ifplugd 0.28 initializing.
Apr 17 18:48:04 Tower ifplugd(eth0)[1512]: Using interface eth0
Apr 17 18:48:04 Tower ifplugd(eth0)[1512]: Initialization complete, link beat not detected.
Apr 17 18:48:04 Tower rpc.statd[1544]: Version 1.1.4 Starting
Apr 17 18:48:04 Tower emhttp: unRAID System Management Utility version 4.7

 

An obvious difference but what does it mean?

What Supermicro card are you talking about? You might wanna take it out temporarily. The Network adapter wasn't disabled in the BIOS by mistake?

 

 

Just comparing a log from yesterday when it was working and one from when it wasn't

 

Working:

Apr 17 14:26:47 Tower ifplugd(eth0)[1516]: ifplugd 0.28 initializing.
Apr 17 14:26:47 Tower ifplugd(eth0)[1516]: Using interface eth0/00:25:22:82:2E:F3 with driver <r8169> (version: 2.3LK-NAPI)
Apr 17 14:26:47 Tower ifplugd(eth0)[1516]: Using detection mode: SIOCETHTOOL
Apr 17 14:26:47 Tower ifplugd(eth0)[1516]: Initialization complete, link beat detected.
Apr 17 14:26:47 Tower kernel: r8169: eth0: link up
Apr 17 14:26:47 Tower kernel: r8169: eth0: link up
Apr 17 14:26:47 Tower ifplugd(eth0)[1516]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Apr 17 14:26:47 Tower logger: /etc/rc.d/rc.inet1:  /sbin/ifconfig eth0 192.168.0.200 broadcast 192.168.0.255 netmask 255.255.255.0
Apr 17 14:26:47 Tower logger: /etc/rc.d/rc.inet1:  /sbin/route add default gw 192.168.0.1 metric 1
Apr 17 14:26:47 Tower ntpd[1553]: ntpd [email protected] Wed Jan 14 23:46:25 UTC 2009 (1)
Apr 17 14:26:47 Tower ifplugd(eth0)[1516]: client: Starting NTP daemon:  /usr/sbin/ntpd -g
Apr 17 14:26:47 Tower ntpd[1554]: precision = 1.000 usec
Apr 17 14:26:47 Tower ntpd[1554]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
Apr 17 14:26:47 Tower ntpd[1554]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
Apr 17 14:26:47 Tower ntpd[1554]: Listening on interface #1 lo, 127.0.0.1#123 Enabled
Apr 17 14:26:47 Tower ntpd[1554]: Listening on interface #2 eth0, 192.168.0.200#123 Enabled
Apr 17 14:26:47 Tower ntpd[1554]: kernel time sync status 0040
Apr 17 14:26:47 Tower ntpd[1554]: frequency initialized 23.115 PPM from /etc/ntp/drift
Apr 17 14:26:47 Tower ifplugd(eth0)[1516]: Program executed successfully.
Apr 17 14:26:47 Tower rpc.statd[1568]: Version 1.1.4 Starting
Apr 17 14:26:47 Tower emhttp: unRAID System Management Utility version 4.7

 

Not Working:

Apr 17 18:48:04 Tower ifplugd(eth0)[1512]: ifplugd 0.28 initializing.
Apr 17 18:48:04 Tower ifplugd(eth0)[1512]: Using interface eth0
Apr 17 18:48:04 Tower ifplugd(eth0)[1512]: Initialization complete, link beat not detected.
Apr 17 18:48:04 Tower rpc.statd[1544]: Version 1.1.4 Starting
Apr 17 18:48:04 Tower emhttp: unRAID System Management Utility version 4.7

 

An obvious difference but what does it mean?

 

The LAN-port isn't working or detected. Were there any hardware changes or BIOS changes?

 

Is the network cable ok and inserted properly?

Cable and hub are fine as I checked my other server on them.

 

This morning I tried swapping my flashdrives around between both servers and I am convinced it's not an unraid issue now as the movie server (unraid OS) that wouldn't connect, connects fine on another.

 

I went to the BIOS screen and finally found the ethernet settings and it looked like this garbled mess so there is something definitely wrong with the motherboard imo. Any idea on what I should do next? Return it? Try and update it?:

 

 

try doing a factory reset to defaults in the BIOS and go from there.

 

 

I have a feeling you are going to have to return the board though.

Cable and hub are fine as I checked my other server on them.

 

This morning I tried swapping my flashdrives around between both servers and I am convinced it's not an unraid issue now as the movie server (unraid OS) that wouldn't connect, connects fine on another.

 

I went to the BIOS screen and finally found the ethernet settings and it looked like this garbled mess so there is something definitely wrong with the motherboard imo. Any idea on what I should do next? Return it? Try and update it?:

 

 

I'd go and try it with no add-on cards, see what happens and perhaps setting BIOS-defaults. But first try without any add-on cards. I don't know if it wise to try updating the BIOS. Otherwise try to return the board, for a server you want a stable and solid base.

Tried resetting to default still didn't work. I'm gonna return the board, thanks for the help guys.

Sorry to hear. Can always happen. Hope the new board will last longer.

Did you ever try booting again without the supermicro card?  There could be a hardware conflict. If that is the case, a replacement board of the same model would probably have the same issues.

Did you ever try booting again without the supermicro card?  There could be a hardware conflict. If that is the case, a replacement board of the same model would probably have the same issues.

 

Tbh no I didn't.

It has worked fine with the supermirco card since October why would it change?