Yea, the Win10 is on wired, and it was the iperf server.
I didn’t find any instructions… 
. So if you have any guide, I could try it
It puzzles me though, that when i use smbclient I get ok transferspeeds
Ok so let’s not complicate things. Lets not go for NFS. Surely the smbclient differences are strange as they should use the same kernel modules. I suggest:
- Check for any smb.conf files and post their content
find /home/osmc -type f -name "smb.conf" -exec paste-log "{}" \; sudo find /etc -type f -name "smb.conf" -exec paste-log "{}" \;
- Start with a fresh install as my feeling is in the meantime many things are overlapping. After fresh install start with fstab mounts directly.
+1 for this idea. I’m also thinking that so many things have been tried that it’s just easier to start over.
Thanks. It came up with 3 hits. I don’t think I have edited any of these files. The content is:
https://paste.osmc.tv/ipevurudig
https://paste.osmc.tv/tikovuqobu
https://paste.osmc.tv/asirahutuw
I will do a clean install, and post results.
ok, keep us posted. I wonder did you install the Samba Server on purpose?
Yes I did. For ease of access from my Windows machine. Not really needed though.
I can skip installing it on the fresh install.
Well it shouldn’t harm (I have it installed on mine) but for new install I suggest you try the fstab mounts performance as the first step before installing additional stuff
I did a fresh install, edited fstab to mount, but unfortunately it is the same performance 
osmc@vero:~$ dd if=/mnt/movies-d/test.file of=/dev/null bs=1M count=3072
115+1 records in
115+1 records out
121505600 bytes (122 MB) copied, 102.228 s, 1.2 MB/s
I then installed iperf, and ran an iperf test, that is still good, avg 166Mbit/sec: https://paste.osmc.tv/fupesesepa
Any ideas? 
It would be interesting to see what happens if you try this on the Vero:
dd if=/dev/zero of=/dev/null bs=1M count=3072
I’d expect to see a large difference.
Well first important info you are not alone anymore. I test and got also 3 times faster transfer with smbclient than fstab. But the bad news sofar no idea why.
smb: \> get test.file
getting file \test.file of size 681867016 as test.file (7080.1 KiloBytes/sec) (average 6734.2 KiloBytes/sec)
osmc@osmc-vero4k:~$ dd if=/mnt/server.my.hk/test.file of=/home/osmc/test.file bs=1M count=3072650+1 records in
650+1 records out
681867016 bytes (682 MB, 650 MiB) copied, 249.569 s, 2.7 MB/s
Ok it seems to be a wireless issue. On wired I get similar results between fstab and smbclient
osmc@osmc-vero4k:~$ dd if=/mnt/server.my.hk/test.file of=/home/osmc/test.file bs=1M count=3072
650+1 records in
650+1 records out
681867016 bytes (682 MB, 650 MiB) copied, 69.5786 s, 9.8 MB/s
smb: \> get test.file
getting file \test.file of size 681867016 as test.file (9394.9 KiloBytes/sec) (average 9394.9 KiloBytes/sec)bmillham:
I tried the command, and it shows a large difference:
osmc@vero:~$ dd if=/dev/zero of=/dev/null bs=1M count=3072
3072+0 records in
3072+0 records out
3221225472 bytes (3.2 GB) copied, 0.692904 s, 4.6 GB/s
I then tried to connect the Vero wired instead, and wired seems to have same performance when mounted and when using smbclient, same results as you fzinken:
osmc@vero:~$ dd if=/mnt/movies-d/test.file of=/dev/null bs=1M count=3072
121505600 bytes (122 MB) copied, 11.2324 s, 10.8 MB/s
osmc@vero:~$ smbclient //192.168.1.40/movies-d --user=vero -m SMB3
smb: \> get test.file /dev/null
getting file \test.file of size 121505600 as /dev/null (10625.8 KiloBytes/sec) (average 10625.8 KiloBytes/sec)Well now we have same results but still not any better know the issue as this is really strange.
I think will review with @sam_nazarko after the problems of the stretch upgrade are solved
Allright, thanks for your help so far 
Contact me if you need me to test something.
Hi @Beastie ,
@sam_nazarko now has build a Kernel which at least for me fixes the issue. You can install it from the staging repro (see below and remember to change back afterwards). Would be great if you can test and report if your problem is solved.
To test this update:
- Login via the command line
- Edit the file
/etc/apt/sources.list - Add the following line:
deb http://apt.osmc.tv stretch-devel main - Run the following commands to update:
sudo apt-get update && sudo apt-get dist-upgrade && reboot - Your system should have have received the update.
Please see if the issue is resolved.
I also recommend you edit /etc/apt/sources.list again and remove the line that you added after updating. This will return you to the normal update channel.
Hey, thanks for reply!
I updated, and now running version 2017.12-1
Before updating i did the test, and results were:
osmc@vero:~$ dd if=/mnt/movies-d/test.file of=/dev/null bs=1M count=3072
115+1 records in
115+1 records out
121505600 bytes (122 MB) copied, 108.111 s, 1.1 MB/s
After updating i did the same test, and results:
osmc@vero:~$ dd if=/mnt/movies-d/test.file of=/dev/null bs=1M count=3072
115+1 records in
115+1 records out
121505600 bytes (122 MB) copied, 55.4584 s, 2.2 MB/s
So it basically doubled in speed, but still not enough for 4k streaming.
Another thing i want to mention, is that after a reboot, it does not automatically connect to wifi, after the update.
Haven’t seen this issue. If it persists try to remove all settings under /var/lib/connman/wifi_* and reconfigure your wireless
That looks very low, but what is your wireless speed (per iperf3)?
That’s really strange. What is smbclient giving you now? also 2.2MB/s?
I am now getting 8-9MB/s in dd and smbclient with a iperf of 90Mbit
BTW, I figured out that recently the performance of the Kodi buildin SMB client is very good. Maybe try in Settings → Filemanager with smb:// and time the transfer of the 122M file.