slow speed on SMB share 355kb/s

[justnth]

Hi I am quite new to use the Truenas or any NAS

I have build my system as signature
Followed in structions to setup pool, dataset, user, as SMB share, started SMB service
when explore into the network dataset folder, it looks fine, but copying anything would be so slow, 355kb/s

Can anyone help to point me to the right direction please?

Thank you.

 

[artlessknave]

the first thing I would say is that you have chosen hardware that is not recommended. I tried to find the NIC driver and it seems MSI deosn't want anyone to know. this leads me to suspect realtek, although the WIFI (not of any use) is Intel.

that said, while realtel NICs are typically garbage for a server...355kb/s seems excessively slow even for that.
as both the client and server are involved, probably need the specs for the client as well.

 

[Davvo]

You don't want L2ARC with 16GB of RAM.
Please give us more context, and do iperf tests.

 

[Whattteva]

Are you copying a bulk large file (like a movie) or a bunch of really small files? HDD's suck on a lot of small files.

 

[LarsR]

MSI lists the network card as

• 1 x Realtek® 8111H Gigabit LAN controller

in the specc sheet.
And this could very well be the Problem
Truenas either defaults to the wrong realtek driver or the linux support for realtek is just as crappy as it's for bsd and core

 

[justnth]

the first thing I would say is that you have chosen hardware that is not recommended. I tried to find the NIC driver and it seems MSI deosn't want anyone to know. this leads me to suspect realtek, although the WIFI (not of any use) is Intel.

that said, while realtel NICs are typically garbage for a server...355kb/s seems excessively slow even for that.
as both the client and server are involved, probably need the specs for the client as well.

Thanks for the comment, the clinet is windows 10, ryzen 3600, ROG strix b550i, I read somewhere that it could be the SMB services with Microsoft, but I am generally confused here. Would Truenas Scale be a better starting point?

 

[justnth]

Are you copying a bulk large file (like a movie) or a bunch of really small files? HDD's suck on a lot of small files.

one big file to test (only 1gb though), just to test what is going on.

 

[justnth]

MSI lists the network card as

• 1 x Realtek® 8111H Gigabit LAN controller

in the specc sheet.
And this could very well be the Problem
Truenas either defaults to the wrong realtek driver or the linux support for realtek is just as crappy as it's for bsd and core

if the wrong driver was used, how should I correct this?

 

[justnth]

You don't want L2ARC with 16GB of RAM.
Please give us more context, and do iperf tests.

Hi, what do you mean by l2arc with 16gb or ram?

The iperf test shows connection refused. (do I need to set up port forwarding on the router?) Using deco m5 as home wifi system, wired connection from Nas to router

truenas% iperf -c 192.168.68.200
tcp connect failed: Connection refused
------------------------------------------------------------
Client connecting to 192.168.68.200, TCP port 5001
TCP window size: -1.00 Byte (default)
------------------------------------------------------------

 

[justnth]

Hi, what do you mean by l2arc with 16gb or ram?

The iperf test shows connection refused. (do I need to set up port forwarding on the router?) Using deco m5 as home wifi system, wired connection from Nas to router

truenas% iperf -c 192.168.68.200
tcp connect failed: Connection refused
------------------------------------------------------------
Client connecting to 192.168.68.200, TCP port 5001
TCP window size: -1.00 Byte (default)
------------------------------------------------------------

got iperf running properly now, running the server on the nas, and windows to do the test, and it is not working at all. the error is "unable to receive parameters from client: connection reset by peer"

when running iperf -s on the winows machine, ssh to nas and run iperf I got this

------------------------------------------------------------
Client connecting to 192.168.68.126, TCP port 5201
TCP window size: 32.8 KByte (default)
------------------------------------------------------------
[ 1] local 192.168.68.200 port 10243 connected with 192.168.68.126 port 5201
[ ID] Interval Transfer Bandwidth
[ 1] 0.00-20.09 sec 32.8 KBytes 13.4 Kbits/sec

 

[justnth]

further update, I ssh to my pi zero, installed iperf and run the iperf server on this, when testing from the NAS, it has got about 20mbits/sec, does it mean the driver is fine, the problem is to the windows desktop I am using?

 

[jgreco]

Would Truenas Scale be a better starting point?

No. With SCALE you would be trying to support that L2ARC on only 8GB of ARC, making the ARC crisis on your system worse.

if the wrong driver was used, how should I correct this?

There is no "wrong" Realtek driver, the Realtek silicon - particularly the 8111 - is just an awful product. What you do is get rid of it. Go buy an Intel Desktop CT ethernet adapter -- make sure you get a real one, not a knockoff, should be about $35, plug it in, and then move on with your very much faster and better life. Then never buy another Realtek mainboard.

Is my Realtek ethernet really that bad?

One of the longest running issues faced here in the forums may be people who come to these forums, wanting to recycle an old PC into a NAS. In general, this is a bad idea because typical PC hardware isn't optimized towards the task. However...

www.truenas.com

it has got about 20mbits/sec, does it mean the driver is fine, the problem is to the windows desktop I am using?

A Pi is unlikely to ever get gigabit ethernet performance. You aren't getting a meaningful test here.

 

[artlessknave]

if the wrong driver was used, how should I correct this?

its not a case of wrong driver, its a case of wrong hardware. realtek NICs are crap. realtek drivers are crap.

 

[Davvo]

Hi, what do you mean by l2arc with 16gb or ram?

In your signature you wrote the existance of a cache drive (L2ARC) as well as having 16GB of RAM.
L2ARC is to be used with at least 64GB.

 

[Whattteva]

further update, I ssh to my pi zero, installed iperf and run the iperf server on this, when testing from the NAS, it has got about 20mbits/sec, does it mean the driver is fine, the problem is to the windows desktop I am using?

20 Mbps is still uber slow when you're supposed to be getting 1000Mbps. It's only 2% of Gigabit bandwidth.
Even if you'd actually meant 20 MB/s, that's still only about 1/5 the speed you're supposed to be getting for Gigabit ethernet.

 

[artlessknave]

20 Mbps is still uber slow

not for a pi zero

 

[justnth]

got an updated iperf test results, seems that my desktop wired connection is broken

Setting up the NAS as server, listening on port 5001 (wired connection to router with static local IP)
My desktop pc got windows 10
iperf3 for windows did not work, iperf2.1.8 got about 1.94Mbits/s, on wired connections
iperf2.1.8 for windows got this (wired connection):
TCP window size: 64.0 KByte (default)
------------------------------------------------------------
[ 1] local 192.168.68.200 port 5001 connected with router IP port 9672
[ ID] Interval Transfer Bandwidth
[ 1] 0.00-11.37 sec 2.63 MBytes 1.94 Mbits/sec
[ 2] local 192.168.68.200 port 5001 connected with router IP port 9680
[ ID] Interval Transfer Bandwidth
[ 2] 0.00-0.20 sec 48.8 KBytes 1.99 Mbits/sec
[ 3] local 192.168.68.200 port 5001 connected with router IP port 9681
[ ID] Interval Transfer Bandwidth
[ 3] 0.00-2.06 sec 488 KBytes 1.94 Mbits/sec
[ 4] local 192.168.68.200 port 5001 connected with router IP port 9682
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-20.66 sec 4.77 MBytes 1.94 Mbits/sec
[ 5] local 192.168.68.200 port 5001 connected with router IP port 9687
[ ID] Interval Transfer Bandwidth
[ 5] 0.00-198.18 sec 45.8 MBytes 1.94 Mbits/sec



iperf2.1.8 got about for wifi connections
root@truenas[~]# iperf -s
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 64.0 KByte (default)
------------------------------------------------------------
[ 1] local 192.168.68.200 port 5001 connected with 192.168.68.101 port 3620
[ ID] Interval Transfer Bandwidth
[ 1] 0.00-10.01 sec 473 MBytes 397 Mbits/sec
[ 2] local 192.168.68.200 port 5001 connected with 192.168.68.101 port 3621
[ ID] Interval Transfer Bandwidth
[ 2] 0.00-10.01 sec 508 MBytes 426 Mbits/sec
[ 3] local 192.168.68.200 port 5001 connected with 192.168.68.101 port 3628
[ ID] Interval Transfer Bandwidth
[ 3] 0.00-0.01 sec 48.8 KBytes 69.9 Mbits/sec
[ 4] local 192.168.68.200 port 5001 connected with 192.168.68.101 port 3629
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-0.02 sec 488 KBytes 200 Mbits/sec
[ 5] local 192.168.68.200 port 5001 connected with 192.168.68.101 port 3630
[ ID] Interval Transfer Bandwidth
[ 5] 0.00-0.14 sec 4.77 MBytes 283 Mbits/sec
[ 6] local 192.168.68.200 port 5001 connected with 192.168.68.101 port 3631
[ ID] Interval Transfer Bandwidth
[ 6] 0.00-2.65 sec 47.7 MBytes 151 Mbits/sec
[ 7] local 192.168.68.200 port 5001 connected with 192.168.68.101 port 3632
[ ID] Interval Transfer Bandwidth
[ 7] 0.00-10.60 sec 477 MBytes 377 Mbits/sec



My pi zero running pihole on it.
iperf got
TCP window size: 64.0 KByte (default)
------------------------------------------------------------
[ 1] local 192.168.68.200 port 5001 connected with 192.168.68.118 port 45574
[ ID] Interval Transfer Bandwidth
[ 1] 0.00-10.13 sec 41.4 MBytes 34.3 Mbits/sec
[ 2] local 192.168.68.200 port 5001 connected with 192.168.68.118 port 45602
[ ID] Interval Transfer Bandwidth
[ 2] 0.00-0.04 sec 48.8 KBytes 9.13 Mbits/sec
[ 3] local 192.168.68.200 port 5001 connected with 192.168.68.118 port 45610
[ ID] Interval Transfer Bandwidth
[ 3] 0.00-0.14 sec 488 KBytes 29.0 Mbits/sec
[ 4] local 192.168.68.200 port 5001 connected with 192.168.68.118 port 45616
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-1.23 sec 4.77 MBytes 32.5 Mbits/sec
[ 5] local 192.168.68.200 port 5001 connected with 192.168.68.118 port 45626
[ ID] Interval Transfer Bandwidth
[ 5] 0.00-11.75 sec 47.7 MBytes 34.0 Mbits/sec

 

[justnth]

No. With SCALE you would be trying to support that L2ARC on only 8GB of ARC, making the ARC crisis on your system worse.



There is no "wrong" Realtek driver, the Realtek silicon - particularly the 8111 - is just an awful product. What you do is get rid of it. Go buy an Intel Desktop CT ethernet adapter -- make sure you get a real one, not a knockoff, should be about $35, plug it in, and then move on with your very much faster and better life. Then never buy another Realtek mainboard.

Is my Realtek ethernet really that bad?

One of the longest running issues faced here in the forums may be people who come to these forums, wanting to recycle an old PC into a NAS. In general, this is a bad idea because typical PC hardware isn't optimized towards the task. However...

www.truenas.com

A Pi is unlikely to ever get gigabit ethernet performance. You aren't getting a meaningful test here.

in that case would wifi work better? the msi mb also has a wifi chip built in, I think that was intel
Intel® Dual Band Wireless-AC 3168 module

 

[Davvo]

in that case would wifi work better? the msi mb also has a wifi chip built in, I think that was intel
Intel® Dual Band Wireless-AC 3168 module

TrueNAS doesn't support wifi.

 

[justnth]

No. With SCALE you would be trying to support that L2ARC on only 8GB of ARC, making the ARC crisis on your system worse.



There is no "wrong" Realtek driver, the Realtek silicon - particularly the 8111 - is just an awful product. What you do is get rid of it. Go buy an Intel Desktop CT ethernet adapter -- make sure you get a real one, not a knockoff, should be about $35, plug it in, and then move on with your very much faster and better life. Then never buy another Realtek mainboard.

Is my Realtek ethernet really that bad?

One of the longest running issues faced here in the forums may be people who come to these forums, wanting to recycle an old PC into a NAS. In general, this is a bad idea because typical PC hardware isn't optimized towards the task. However...

www.truenas.com

A Pi is unlikely to ever get gigabit ethernet performance. You aren't getting a meaningful test here.

Here is what I got with wifi
the wire connection seems to break it by connect to the nas with external ip addresses, is there a way to modify that?

iperf2.1.8 got about 300-400Mbits/s for wifi connections, only 1.9-2 Mbits/s for wired connections ( e.g. [ 1] local 192.168.68.200 port 5001 connected with router IP port 9672)

for wifi connections though
root@truenas[~]# iperf -s
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 64.0 KByte (default)
------------------------------------------------------------
[ 1] local 192.168.68.200 port 5001 connected with 192.168.68.101 port 3620
[ ID] Interval Transfer Bandwidth
[ 1] 0.00-10.01 sec 473 MBytes 397 Mbits/sec
[ 2] local 192.168.68.200 port 5001 connected with 192.168.68.101 port 3621
[ ID] Interval Transfer Bandwidth
[ 2] 0.00-10.01 sec 508 MBytes 426 Mbits/sec
[ 3] local 192.168.68.200 port 5001 connected with 192.168.68.101 port 3628
[ ID] Interval Transfer Bandwidth
[ 3] 0.00-0.01 sec 48.8 KBytes 69.9 Mbits/sec
[ 4] local 192.168.68.200 port 5001 connected with 192.168.68.101 port 3629
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-0.02 sec 488 KBytes 200 Mbits/sec
[ 5] local 192.168.68.200 port 5001 connected with 192.168.68.101 port 3630
[ ID] Interval Transfer Bandwidth
[ 5] 0.00-0.14 sec 4.77 MBytes 283 Mbits/sec
[ 6] local 192.168.68.200 port 5001 connected with 192.168.68.101 port 3631
[ ID] Interval Transfer Bandwidth
[ 6] 0.00-2.65 sec 47.7 MBytes 151 Mbits/sec
[ 7] local 192.168.68.200 port 5001 connected with 192.168.68.101 port 3632
[ ID] Interval Transfer Bandwidth
[ 7] 0.00-10.60 sec 477 MBytes 377 Mbits/sec