Very slow transfer speeds.

rodofrn · Jul 12, 2018

Hello guys, I recently realized that my PC transfer speed to my NAS is 10MB/s, it used to be 100MB/s. I have checked the cable and changed both tip connectors, and the speed remained the same. I have not changed any hardware in a long time. I have a "Supermicro Motherboard Micro ATX DDR3 1600 LGA 1150 Motherboards X10SLL-F-O" and have 2 ethernet cables going into it, in case one fails the other one takes over right? Here is the output of my ifconfig. Let me know any info you need, I will provide it very quickly. Thanks in advance.

Code:

root@freenas:~ # ifconfig
em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
		options=2098<VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC>
		ether 0c:c4:7a:c5:16:49
		hwaddr 0c:c4:7a:c5:16:49
		inet 192.168.0.114 netmask 0xffffff00 broadcast 192.168.0.255
		nd6 options=9<PERFORMNUD,IFDISABLED>
		media: Ethernet autoselect (1000baseT <full-duplex>)
		status: active
igb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
		options=6403bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
		ether 0c:c4:7a:c5:16:48
		hwaddr 0c:c4:7a:c5:16:48
		inet 192.168.0.104 netmask 0xffffff00 broadcast 192.168.0.255
		nd6 options=9<PERFORMNUD,IFDISABLED>
		media: Ethernet autoselect (1000baseT <full-duplex>)
		status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
		options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
		inet6 ::1 prefixlen 128
		inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
		inet 127.0.0.1 netmask 0xff000000
		nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
		groups: lo
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
		ether 02:40:58:77:2e:00
		nd6 options=1<PERFORMNUD>
		groups: bridge
		id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
		maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
		root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
		member: epair6a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
				ifmaxaddr 0 port 11 priority 128 path cost 2000
		member: epair5a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
				ifmaxaddr 0 port 10 priority 128 path cost 2000
		member: epair4a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
				ifmaxaddr 0 port 9 priority 128 path cost 2000
		member: epair3a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
				ifmaxaddr 0 port 8 priority 128 path cost 2000
		member: epair2a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
				ifmaxaddr 0 port 7 priority 128 path cost 2000
		member: epair1a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
				ifmaxaddr 0 port 6 priority 128 path cost 2000
		member: epair0a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
				ifmaxaddr 0 port 5 priority 128 path cost 2000
		member: em0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
				ifmaxaddr 0 port 1 priority 128 path cost 20000
epair0a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
		options=8<VLAN_MTU>
		ether 02:24:50:00:05:0a
		hwaddr 02:24:50:00:05:0a
		nd6 options=1<PERFORMNUD>
		media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
		status: active
		groups: epair
epair1a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
		options=8<VLAN_MTU>
		ether 02:24:50:00:06:0a
		hwaddr 02:24:50:00:06:0a
		nd6 options=1<PERFORMNUD>
		media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
		status: active
		groups: epair
epair2a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
		options=8<VLAN_MTU>
		ether 02:24:50:00:07:0a
		hwaddr 02:24:50:00:07:0a
		nd6 options=1<PERFORMNUD>
		media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
		status: active
		groups: epair
epair3a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
		options=8<VLAN_MTU>
		ether 02:24:50:00:08:0a
		hwaddr 02:24:50:00:08:0a
		nd6 options=1<PERFORMNUD>
		media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
		status: active
		groups: epair
epair4a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
		options=8<VLAN_MTU>
		ether 02:24:50:00:09:0a
		hwaddr 02:24:50:00:09:0a
		nd6 options=1<PERFORMNUD>
		media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
		status: active
		groups: epair
epair5a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
		options=8<VLAN_MTU>
		ether 02:24:50:00:0a:0a
		hwaddr 02:24:50:00:0a:0a
		nd6 options=1<PERFORMNUD>
		media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
		status: active
		groups: epair
epair6a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
		options=8<VLAN_MTU>
		ether 02:24:50:00:0b:0a
		hwaddr 02:24:50:00:0b:0a
		nd6 options=1<PERFORMNUD>
		media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
		status: active
		groups: epair

Elliot Dierksen · Jul 12, 2018

In general I think it is not best practice to have multiple IP addresses on the same network. Does disconnecting one of the NIC ports change anything? For what you are trying to achieve (redundancy, not link aggregation), I would recommend doing a LAG configured in failover mode.

Chris Moore · Jul 12, 2018

rodofrn said:
Let me know any info you need, I will provide it very quickly. Thanks in advance.

You can't do it that way: https://en.wikipedia.org/wiki/Switching_loop
You need a switch that supports Link Aggregation (LAG) and you need to setup a LAG on the NAS.
http://doc.freenas.org/11/network.html#link-aggregations

Chris Moore · Jul 12, 2018

Elliot Dierksen said:
In general I think it is not best practice to have multiple IP addresses on the same network.

You are correct. That absolutely will cause a problem: https://en.wikipedia.org/wiki/Broadcast_radiation

rodofrn · Jul 16, 2018

@Elliot Dierksen Thanks for answering, I disconnected one of the cables and nothing changed, same 10mbps speed.

@Chris Moore Thanks for answering, what should I do then?

I used to be able to reach 100mbps transfer speed, but not anymore.

m0nkey_ · Jul 16, 2018

rodofrn said:
and have 2 ethernet cables going into it, in case one fails the other one takes over right?

Wrong.

You can set-up a simple failover LAGG without any kind of smart/managed switch. Check out @DrKK's post on this: https://forums.freenas.org/index.ph...failover-on-your-x10-or-similar-server.39366/

Elliot Dierksen · Jul 16, 2018

What are you using to test the speed? If it is CIFS, you should (temporarily) set up FTP or something else to see if it is unique to CIFS. Have you tested from a different workstation? If not, can you?

rodofrn · Jul 17, 2018

OK so, I no longer have 2 cables going into the machine, only 1.

Elliot Dierksen said:
What are you using to test the speed?

I am simply going into the workstation and transferring a file over CIFS.

Elliot Dierksen said:
you should (temporarily) set up FTP or something else to see if it is unique to CIFS.

I did, it is the same speed. :/

Elliot Dierksen said:
ave you tested from a different workstation? If not, can you?

Just went to my gf mac, and voila, 100mbps.

What is wrong with my workstation? I reinstalled the EXACT (found MB model, website to check NIC details, download NIC drivers) drivers for the onboard NIC. Same speed. I don't think its the cable?!!? What else can I do?

Thanks all for keeping up with this post!

Elliot Dierksen · Jul 17, 2018

Is it a managed or un-managed switch? If it is the former, are speed and duplex both set to auto? Same question on the NIC in your workstation. I have nothing to base this on but gut feel, but I wonder if one side or the other has duplex forced to full.

kdragon75 · Jul 17, 2018

Did you test or swap the cable to be sure? 1gb uses more actual wires than 100mb. Also check the link speed on your workstation.

Elliot Dierksen · Jul 17, 2018

kdragon75 said:
Did you test or swap the cable to be sure? 1gb uses more actual wires than 100mb. Also check the link speed on your workstation.

Good point. If the Mac in question is wired, try switching cables and switch ports. If the problem follows the port/cable, that gives you a direction. Same thing if the problem follows the workstation. Again, my gut leans towards something with duplex forced to full.

[Network guy rant]
Short of a bridging loop, forcing duplex is usually the WORST thing you can to do a network. What a lot of people don't realize is that when a device has duplex forced, that means it does not respond to a duplex negotiation request. If no response is received to a duplex negotiation request, that device is required to assume half duplex. That means that any time both sides start to talk, the half duplex side will abort. This causes absolutely abysmal performance. You can actually tell very easily in a managed switch by looking at the interface stats. The full duplex side will see lots of runts (packets too short) and CRC errors. The half duplex side will see TONS of collisions, and particularly late collisions. I have a mental block as to whether it is 2 or 3 maximum repeaters in a segment (hubs for those of you that aren't old like me), but there is a maximum for that and a maximum cable length. Because of these limits, there is a maximum amount of time that any device on a network should be able to see that a device has the wire and they should not talk. A late collision is a collision that occurs after this time has expired and every device should know that the wire is occupied. Late collisions are ALWAYS bad! Phew, sorry. Guess I got a little carried away.
[/Network guy rant]

rodofrn · Jul 17, 2018

Elliot Dierksen said:
Is it a managed or un-managed switch?

It is a managed switch.

Elliot Dierksen said:
are speed and duplex both set to auto?

They are set to auto on the switch.

Elliot Dierksen said:
Same question on the NIC in your workstation.

They are set to auto on the NIC.

No idea on what this could be... :(

Elliot Dierksen · Jul 17, 2018

rodofrn said:
It is a managed switch.

Are there any flow control settings on either the NIC or the switch port?

rodofrn · Jul 17, 2018

Elliot Dierksen said:
but I wonder if one side or the other has duplex forced to full.

Now that you ask...it does say this on the monitoring page. My workstation is "PORT 1".

rodofrn · Jul 17, 2018

Elliot Dierksen said:
Are there any flow control settings on either the NIC or the switch port?

They are both "OFF".

rodofrn · Jul 17, 2018

kdragon75 said:
Did you test or swap the cable to be sure? 1gb uses more actual wires than 100mb. Also check the link speed on your workstation.

I am about to swap cables. The link speed says 100Mbps.

rodofrn · Jul 17, 2018

CASE CLOSED.

The cable was hanging from the port in the switch. Meaning it wasn't all the way connected properly.

I am going to hide and cry under my bed now.

Thanks all for keeping up with my stupidity.

Take care! @Elliot Dierksen @kdragon75 @Chris Moore

Elliot Dierksen · Jul 17, 2018

rodofrn said:
The cable was hanging from the port in the switch. Meaning it wasn't all the way connected properly.

Glad you found the answer. I forget where I heard it but I always keep in mind that "Inside every big problem is a little problem dying to get out".

Important Announcement for the TrueNAS Community.

Very slow transfer speeds.

rodofrn

Contributor

Elliot Dierksen

Guru

Chris Moore

Hall of Famer

Chris Moore

Hall of Famer

rodofrn

Contributor

m0nkey_

MVP

Elliot Dierksen

Guru

rodofrn

Contributor

Elliot Dierksen

Guru

kdragon75

Wizard

Elliot Dierksen

Guru

rodofrn

Contributor

Elliot Dierksen

Guru

rodofrn

Contributor

rodofrn

Contributor

rodofrn

Contributor

rodofrn

Contributor

Elliot Dierksen

Guru

Similar threads

Important Announcement for the TrueNAS Community.

Very slow transfer speeds.

Contributor

Guru

Hall of Famer

Hall of Famer

Contributor

MVP

Guru

Contributor

Guru

Wizard

Guru

Contributor

Guru

Contributor

Contributor

Contributor

Contributor

Guru

Important Announcement for the TrueNAS Community.

Related topics on forums.truenas.com for thread: "Very slow transfer speeds."

Similar threads