May 13, 201214 yr A cross-over cable is not required with Gig-E. This I did not know, cheers Even with "traditional" fast ethernet (100Mb/s) connections a cross-over cable isn't needed when MDI-X is supported, which is quite common in ethernet chips nowadays.
May 13, 201214 yr Author I connected my W7 PC directly to the Server, and this time I was able to connected. I transfer a 747 MB file, and I got 2 errors and 1 frame. NIC info (from ethtool) 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: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Supports Wake-on: umbg Wake-on: g Current message level: 0x00000007 (7) Link detected: yes NIC driver info (from ethtool -i) driver: e1000 version: 7.3.21-k8-NAPI firmware-version: N/A bus-info: 0000:02:05.0 Ethernet config info (from ifconfig) eth0 Link encap:Ethernet HWaddr 90:e2:ba:11:a3:ac inet addr:169.254.200.186 Bcast:169.254.255.255 Mask:255.255.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:563275 errors:2 dropped:0 overruns:0 frame:1 TX packets:108273 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:816077528 (778.2 MiB) TX bytes:210224655 (200.4 MiB) I then proceeded to transfer the same file from my Server to my W7 PC, and I observed the same errors were present and no there weren't any new ones. I then proceede to use the mobo ethernet port and transfer the file from and to W7 and Server and vice versa and this is what I've got: NIC info (from ethtool) Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Link partner advertised pause frame use: Symmetric Receive-only Link partner advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) Link detected: yes NIC driver info (from ethtool -i) driver: r8169 version: 2.3LK-NAPI firmware-version: N/A bus-info: 0000:02:00.0 Ethernet config info (from ifconfig) eth0 Link encap:Ethernet HWaddr 00:e0:4d:c6:d2:e0 inet addr:192.168.1.12 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:75603 errors:0 dropped:0 overruns:0 frame:0 TX packets:560764 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:5935142 (5.6 MiB) TX bytes:826781459 (788.4 MiB) Interrupt:42 Base address:0x4000 I transfer another file 700 MB, and I didn't get any error by using the mobo ethernet port. NIC info (from ethtool) Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Link partner advertised pause frame use: Symmetric Receive-only Link partner advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) Link detected: yes NIC driver info (from ethtool -i) driver: r8169 version: 2.3LK-NAPI firmware-version: N/A bus-info: 0000:02:00.0 Ethernet config info (from ifconfig) eth0 Link encap:Ethernet HWaddr 00:e0:4d:c6:d2:e0 inet addr:192.168.1.12 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1216676 errors:0 dropped:0 overruns:0 frame:0 TX packets:1311321 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1590129877 (1.4 GiB) TX bytes:1620421740 (1.5 GiB) Interrupt:42 Base address:0x4000 I think I am going to leave the mobo ethernet port on for now, and see what happens. The reason why I was using the mobo ethernet port was due to the activity LED lights are solide orange and the other is blinking yellow, which is indicative of not using the gigabit speed. However, as you can see about the speed is connected at 1000Mb/s, and the LED activity lights on the Netgear 8 port gigabit router are solid green and blinking green, which is indicating the connection is gigabit. However, if my server is off, and I turn it back on, the mobo ethernet activity LED lights are both green, but as soon it goes into the unraid OS, the mobo ethernet port LED activity lights go orange and yellow. This is the reason why I bought the Netgear Pro PCI NIC, because when it is in use it shows both LED activity LED light green. One solid and the other blinking. So, I am leaning toward may be buying a different mobo. Testing it out and see what happens. Anyone have any more suggestions? The system log is from the mobo ethernet port. syslog-2012-05-13.txt
May 13, 201214 yr From your story it seems the Netgear NIC has some trouble, while the buitl-in port on the MB works fine. If anything you want to replace, it is the Netgear NIC, but why not stick to the MB?
May 13, 201214 yr From your story it seems the Netgear NIC has some trouble, while the buitl-in port on the MB works fine. If anything you want to replace, it is the Netgear NIC, but why not stick to the MB? I agree, don't worry about the lights on the MB LAN connector... worry instead about what ethtool reports.. (and it shows 1000Mb/s connections) Joe L.
May 13, 201214 yr Author I'm sorry it isn't a Netgear NIC, it is a brand new Interl Pro/1000 NIC, which I bought trying to see if the errors and dropped packets would get fixed, but after spending money on replacing cables, and a new Netgeat gigabit 8 port switch, it appears the issues hasn't been fixed. I just ran another ethernet info from unmenu before going to bed, and the mobo ethernet port shows dropped packets, and I wasn't even using the server at all. Here's what I've got: NIC info (from ethtool) Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Link partner advertised pause frame use: Symmetric Receive-only Link partner advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) Link detected: yes NIC driver info (from ethtool -i) driver: r8169 version: 2.3LK-NAPI firmware-version: N/A bus-info: 0000:02:00.0 Ethernet config info (from ifconfig) eth0 Link encap:Ethernet HWaddr 00:e0:4d:c6:d2:e0 inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1195 errors:0 dropped:5 overruns:0 frame:0 TX packets:778 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:122259 (119.3 KiB) TX bytes:396913 (387.6 KiB) Interrupt:42 Base address:0xc000
May 13, 201214 yr The 'dropped' received packets is likely *not* your ethernet connection but the application on top not able to cope with the incoming information. Are you running some apps in the background (eg. couchpotato or sickbeard or similar) which exchange data actively?
May 13, 201214 yr Author The 'dropped' received packets is likely *not* your ethernet connection but the application on top not able to cope with the incoming information. Are you running some apps in the background (eg. couchpotato or sickbeard or similar) which exchange data actively? I am running 5b14, and these are the addons, that I've installed via unmenu: -bwm-ng -iperf-2.0.5 -monthly_parity_check -pciutils-2.2.10 -clean powerdown All of the above addons are set to re-install when booted.
May 14, 201214 yr The 'dropped' received packets is likely *not* your ethernet connection but the application on top not able to cope with the incoming information. Are you running some apps in the background (eg. couchpotato or sickbeard or similar) which exchange data actively? I am running 5b14, and these are the addons, that I've installed via unmenu: -bwm-ng -iperf-2.0.5 -monthly_parity_check -pciutils-2.2.10 -clean powerdown All of the above addons are set to re-install when booted. Have you done any test copies with all addons disabled and/or a clean flash? You could also try upgrading to -rc3 with no addons and see what happens.
May 14, 201214 yr The 'dropped' received packets is likely *not* your ethernet connection but the application on top not able to cope with the incoming information. Are you running some apps in the background (eg. couchpotato or sickbeard or similar) which exchange data actively? I am running 5b14, and these are the addons, that I've installed via unmenu: -bwm-ng -iperf-2.0.5 -monthly_parity_check -pciutils-2.2.10 -clean powerdown All of the above addons are set to re-install when booted. Have you done any test copies with all addons disabled and/or a clean flash? You could also try upgrading to -rc3 with no addons and see what happens. Your quoting puzzles me
May 14, 201214 yr Author I was trying to reply from my phone, but for some reason or another I couldn't scroll down to type what I wanted, and I apparently hit post. Anyway, I just got off work right now, and I am going to bed. I just worked 14.5 hours, and working another 14 hours later today. I won't have time to run a clean install until tomorrow. I wanted to ask, when I do a clean install do I've got to run the "trust my array" script? Or do I just bring up the array like I normally do now, just making sure all of the drives are in the correct order?
May 14, 201214 yr You should be able to just put the drives back into the correct order but once everything is up and running do a parity check to ensure everything looks good.
May 14, 201214 yr Author Sounds good. I was also wondering if the wireless connection would interfere and cause the wired connection to have errors or lose packets? Im thinking of maybe trying a different router if the clean install doesnt work. I updated the routers FW and I had to flash it back to an older FW because it kept losing wireless connection. Also it cannot find my wired devices like it used to. I've had to entered them manually.
May 16, 201214 yr Author I completed a parity check, which showed no errors prior to doing a clean install. I am performing a parity check right now with a clean installed of RC3, and so far I've got no errors or dropped packets in the ethernet info from unmenu. I am currently ripping some more of my movie collection 1 BD, and 10 DVD's. I will transfer them after the parity check is complete and see if I get any error or dropped packets. NIC info (from ethtool) Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Link partner advertised pause frame use: Symmetric Receive-only Link partner advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) Link detected: yes NIC driver info (from ethtool -i) driver: r8169 version: 2.3LK-NAPI firmware-version: N/A bus-info: 0000:02:00.0 Ethernet config info (from ifconfig) eth0 Link encap:Ethernet HWaddr 00:e0:4d:c6:d2:e0 inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4873 errors:0 dropped:0 overruns:0 frame:0 TX packets:4819 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1930238 (1.8 MiB) TX bytes:1324694 (1.2 MiB) Interrupt:42 Base address:0x2000
May 16, 201214 yr Author Well, I guess it was too good to be true . Parity check has about 1 hour left to complete. I went ahead and check the ethernet info, and found 27 dropped packets. I'll post the system log after the parity check is completed. However, I think something is wrong with the mobo's ethernet port because every time I boot the server, on the system log I see that the "link is down" all the time. I didn't used to see this when I was using the intel pro pci nic. The only thing I see that both mobo's ethernet port and intel nic share is that they get a new lease from my router daily. Is this normal? I'm to the point of either buying a new router to test it out and see if it is the router causing this issue? Or buying a new mobo? or both? NIC info (from ethtool) Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Link partner advertised pause frame use: Symmetric Receive-only Link partner advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) Link detected: yes NIC driver info (from ethtool -i) driver: r8169 version: 2.3LK-NAPI firmware-version: N/A bus-info: 0000:02:00.0 Ethernet config info (from ifconfig) eth0 Link encap:Ethernet HWaddr 00:e0:4d:c6:d2:e0 inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:9153 errors:0 dropped:27 overruns:0 frame:0 TX packets:6050 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2256812 (2.1 MiB) TX bytes:1709642 (1.6 MiB) Interrupt:42 Base address:0x2000
May 17, 201214 yr Author Well, after spending some extra money for new cat6 cables, and switching my 8 port gigabit Trendnet switch for a netgear 8 port gigabit switch, testing all the lines, and buying a new intel pro pci nic, I am still getting dropped packets and at times errors. So, I guess I'll just have to live with it, but I wanted to ask what's the worse that can happen? Will this corrupt any of the files that I transfer to the server and vice verse?
May 19, 201214 yr Author I have removed the WNDR3700 router completely. I just installed the UVERSE ATT 12 mbps internet for $30.00 dollars, instead of using the Comcast 20 mbps, which was costing me $65.00 dollars. I am using the RG/modem/router that was provided by att, and I connected my Netgear 8 port gigabit router to it, and all of my devices are connected to it. So, far it has been almost 2 hours, and the connection to the unraid server has no error or dropped packets. I was thinking that my WNDR3700 router was the culprit, and I am hoping this is it NIC info (from ethtool) 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: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Supports Wake-on: umbg Wake-on: g Current message level: 0x00000007 (7) Link detected: yes NIC driver info (from ethtool -i) driver: e1000 version: 7.3.21-k8-NAPI firmware-version: N/A bus-info: 0000:02:05.0 Ethernet config info (from ifconfig) eth0 Link encap:Ethernet HWaddr 90:e2:ba:11:a3:ac inet addr:192.168.1.69 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:64475 errors:0 dropped:0 overruns:0 frame:0 TX packets:48848 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:45130905 (43.0 MiB) TX bytes:302372072 (288.3 MiB)
May 20, 201214 yr I have removed the WNDR3700 router completely. I just installed the UVERSE ATT 12 mbps internet for $30.00 dollars, instead of using the Comcast 20 mbps, which was costing me $65.00 dollars. I am using the RG/modem/router that was provided by att, and I connected my Netgear 8 port gigabit router to it, and all of my devices are connected to it. So, far it has been almost 2 hours, and the connection to the unraid server has no error or dropped packets. I was thinking that my WNDR3700 router was the culprit, and I am hoping this is it Let us know if the problem goes away :-) Looking good though!
May 20, 201214 yr Author It has been a little over a day, and I haven't had any types of errors or dropped packets. I am declaring it SOLVED. It appears the culprit was my WNDR3700 router. NIC info (from ethtool) 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: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Supports Wake-on: umbg Wake-on: g Current message level: 0x00000007 (7) Link detected: yes NIC driver info (from ethtool -i) driver: e1000 version: 7.3.21-k8-NAPI firmware-version: N/A bus-info: 0000:02:05.0 Ethernet config info (from ifconfig) eth0 Link encap:Ethernet HWaddr 90:e2:ba:11:a3:ac inet addr:192.168.1.69 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:165389 errors:0 dropped:0 overruns:0 frame:0 TX packets:56595 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:51571167 (49.1 MiB) TX bytes:303094672 (289.0 MiB)
Archived
This topic is now archived and is closed to further replies.