LinuxMCE Forums

General => Users => Topic started by: G.I.R. on August 17, 2016, 03:24:36 pm

Title: Raspberry Pi v3 as media director - slow nfs speed [solved]
Post by: G.I.R. on August 17, 2016, 03:24:36 pm
Hy,

i had some time and tried to use a new RPiB 3 as a media director.
the installation went fine and the md boots flawlessly.
But whenever i try to watch some media or listen to some music the only thing i can see or hear is a short fraction of the media and then it ends.

i have found this error in /var/log/syslog on the md:
Code: [Select]
Aug 17 14:43:12 moon97 kernel: [19352.261755] nfs: server 192.168.80.1 not responding, timed out
I did some speedtest with iperf and that looks good:
Code: [Select]
root@moon97:~# iperf -c 192.168.80.1
------------------------------------------------------------
Client connecting to 192.168.80.1, TCP port 5001
TCP window size: 43.8 KByte (default)
------------------------------------------------------------
[  3] local 192.168.80.4 port 42484 connected with 192.168.80.1 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-10.0 sec   112 MBytes  94.3 Mbits/sec

so i tried to copy a file with scp from the router to the md and got 10.0MB/s.

and now it becomes really strange.
if i mount the nfs shares in this way:

Code: [Select]
root@moon97:~# mount -v -t nfs 192.168.80.1:/home/ /test/                                                         
mount.nfs: timeout set for Wed Aug 17 14:44:36 2016
mount.nfs: trying text-based options 'vers=4,addr=192.168.80.1,clientaddr=192.168.80.4'

the speed of copying a file is really really slow.

if i do it like that:
Code: [Select]
root@moon97:~# mount -v -t nfs 192.168.80.1:/home/public/data/videos/2.00\ TB\ \(sda1\)\ WDC_WD30EFRX-68\ \[58\]/TV/Family_Guy/ /test/
mount.nfs: timeout set for Wed Aug 17 14:46:19 2016
mount.nfs: trying text-based options 'vers=4,addr=192.168.80.1,clientaddr=192.168.80.4'
mount.nfs: mount(2): No such file or directory
mount.nfs: trying text-based options 'addr=192.168.80.1'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.80.1 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.80.1 prog 100005 vers 3 prot UDP port 52139

the speed is normal and i can copy a 100mb file in a few seconds.

the zotac zbox which is my standard md in that room has no problems dealing with any media.
i also switched the network cable without success.

Does anybody has a hint what i am doing wrong or what i can do better?
Maybe it is time to call an exorcist?  :)

LinuxMCE Version: 2.0.0.47.201607240235+899786ab
LMCE 14.04


update:

shame on me and really sorry for bothering!!!

Quote
I usually attribute this to bad cabling or switches.

The Problem was a router called TL-WDR3600.
I thought that the switch of this router would be no problem cause the zotac box had no network problems with that configuration and the possible weak point would be the cable but ...
Now i am using a D-Link switch and everything works great.

Again SORRY and thanks for this perfect mediadirector!

have to write a list for myself:
try turning it off and on again
change the hardware
listen to people
...
Title: Re: Raspberry Pi v3 as media director - slow nfs speed
Post by: phenigma on August 22, 2016, 01:42:12 am
I usually attribute this to bad cabling or switches.  I can say that I have absolutely no problems accessing/playing media with my RPi3s.

J.
Title: Re: Raspberry Pi v3 as media director - slow nfs speed
Post by: G.I.R. on August 22, 2016, 07:32:50 pm
Thank You for Your response!

Do You use the diskless MD or the disked one?

I have some time tomorrow, i can and will try a few things ... :)

Title: Re: Raspberry Pi v3 as media director - slow nfs speed
Post by: phenigma on August 22, 2016, 10:45:49 pm
I have used both, I created the methods to boot the rpi's.  The currently recommended method is diskless style booting and that will always be the preferred method, now that it is available again.  That being said the updated files to use the diskless boot are not yet in the repository.

J.