The first problem I'm having is that my Intel NIC isn't connecting at Gigabit speeds, only 100Mb.  It's connected to a GB switch, and other machines on that switch show GB connections, so I don't think that's the problem.

 

Settings for eth0:

Supported ports: [ TP ]

Supported link modes: 10baseT/Half 10baseT/Full

100baseT/Half 100baseT/Full

1000baseT/Full

Supports auto-negotiation: Yes

Advertised link modes: 10baseT/Half 10baseT/Full

100baseT/Half 100baseT/Full

1000baseT/Full

Advertised pause frame use: No

Advertised auto-negotiation: Yes

Speed: 100Mb/s

Duplex: Full

Port: Twisted Pair

PHYAD: 1

Transceiver: internal

Auto-negotiation: on

MDI-X: on

Supports Wake-on: pumbg

Wake-on: g

Current message level: 0x00000007 (7)

Link detected: yes

 

syslog attached.

 

The second question is how to I enable the onboard NIC to work simultaneously with the Intel NIC?  I believe the capability was added with one of the beta releases of unRAID, but I think there is some hoop jumping required to make this work properly.  I currently have the onboard NIC turned off in the BIOS, so as to try to avoid any issues with the Intel card, but I just wired the house for Gigabit Ethernet, and have the ability to run 2 network cables to the unRAID box, and would like to take advantage of this capability, if possible.  Is there a guide somewhere on how to do this? 

 

Obviously, i need to fix the first issue before moving on to the 'upgrade' but figured I'd try to figure out how to do it, since it might be just as easy to 'fix' everything at one time.

 

My go script...

 

#!/bin/bash
# custom install of updated samba package
installpkg /boot/packages/samba-3.6.8-i486-1.txz
# Start the Management Utility
/usr/local/sbin/emhttp &
echo nameserver 192.168.1.254 >/etc/resolv.conf
echo 192.168.1.150 media >>/etc/hosts

 

Thanks.

syslog.zip

Since you wired the house, I would suspect either:

1. You used a cable not rated for 1000Mb/s.  (You need cat5e, or cat6.  Cat5 alone is not enough)

2. You wired it incorrectly.  There are two different wiring schemes. One for telephone use, the other for LAN use.  My personal crimping tool has the "telephone" scheme on its lid.  Following it would result in a cable that would not wire the pairs correctly.  (is it would work poorly, if at all)  It is really easy to get it wrong.  Even with LAN use there are two different color-coding schemes (A and B)  Again, easy to make a mistake.

3. You have a bad cable with one or more conductor open. (100 MB/s lan only uses 2 pairs.  1000Mb/s uses all 4 pairs.

4. You have a defective port on either the router or LAN card.

 

Since the ports auto-negotiate, there is nothing you can do to force the higher speed that would make the connection in a reliable way.

 

Joe L.

 

That is sad to hear.  I bought 50' pre-crimped cat6 cables from monoprice, so i didn't actually have to manually do any connections.  I would expect them to work fine, and they are the same brand/type/everything as the cables I'm using to connect the rest of the machines to the switch that are working at GB speeds.

 

is there any way to actually test these cables for GB speeds?  I don't want to pull them back thru the walls to get the server end close to the switch, if I can help it, but it's not *that* hard to do if I have to.

 

anything else that might be going wrong here?  I just find it difficult to believe it's the cables, but it's certainly not impossible.

Okay, I switched from one cable to the other, and GB lit up, and the report shows I'm not running GB speed on the server.  So, it must be a bad cable, as you said. 

 

I'll RMA the cable, and get a new one run to the server.

 

Now, I just need to figure out how to setup dual Ethernet connections on unRAID.