July 23, 200817 yr I am running 4.3.2 Hardware is: Abit AB9 Pro latest official BIOS Only the intel sata controller is enable, the two extra ones are disabled in BIOS. NICs disabled in BIOS as well. Intel Pro 1000 PT PCI-e 1x NIC Intel Celeron 440 2GB DDR2 6400 2x Seagate 7200.11 1TB 1x Seagate 7200.10 750GB I am getting really crappy speeds when copying with Total Commander to/from my Vista Ultimate SP1 32-bit box. I have done the network tweak registry hacks. All updates. I am getting under 7,000 KB/s sometimes as low as 700 KB/s. I am also getting cannot read file errors, so it won't even copy. root@Tower:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:1B:21:15:3B:BA inet addr:192.168.1.118 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:131690 errors:1244 dropped:0 overruns:0 frame:642 TX packets:281980 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:13049527 (12.4 MiB) TX bytes:379782666 (362.1 MiB) I've attached my syslog. Please, any help would be appreciated!! PS I do want to buy the pro version and install a cache drive etc but I can't do that until I work out these problems!
July 23, 200817 yr Author I am using Cat6 and a GigE switch. the MTU is set to 1500 though. I didn't have this problem with my previous box, which used the same NIC and cable and switch. Anything telling in the syslog or any other logs / tests / command outputs I can run? I can try a new cable and using the onboard NIC too.
July 24, 200817 yr I'm sorry, my rather desperate need for income got in the way, haven't had much time lately to help. Just took a look at your syslog, and it looks fine, except for buggy ACPI (typical for that board), and the networking. The card and driver seem to initialize without a problem, and gigabit speed is negotiated successfully, but the connection drops several times, almost immediately. It then takes 2 tries to find a DHCP server. I agree with Bill, these dropouts, connection difficulties, and all of the errors in your ifconfig report point mostly to cabling. The next possibility might be bad connectors, strong interference sources near the cabling, or finally a bad card at either end of this connection. All of the retries necessary would probably account for your poor transfer performance. Although for completeness you may want to test/check the connection between your Windows machine and the switch, the dropouts and DHCP issues and frame errors point to a problem between the unRAID server and the switch.
Archived
This topic is now archived and is closed to further replies.