steve-g wrote:
> If still fails - this is the verbose output:
>
> >
Code:
--------------------
> >
> [root@soa-wandboard ~]# mount -t nfs -v 192.168.0.198:/c/media /mnt/disk1
> mount.nfs: timeout set for Tue Mar 31 18:53:07 2015
> mount.nfs: trying text-based options
'vers=4.2,addr=192.168.0.198,clientaddr=192.168.0.8'
> mount.nfs: mount(2): Invalid argument
> mount.nfs: an incorrect mount option was specified
>
--------------------
> >
>
> The wandboard address is 192.168.0.8
OK, possible version clash of nfs versions on wandboard ( vers4) and
ReadyNAs (vers 3 ?). You could try to add a "vers=3" option to the
mount command, but SOA might not handle this correcty, e.g:
Code:
--------------------
mount -t nfs -v -o vers=3 192.168.0.198:/c/media /mnt/disk1
--------------------
Cut paste the last few line of "journalctl -f" here.
I can only tell you I don't have a problem with NFS mounts on my Rpi.
Did I ask if you had the latest SOA image installed on your Wandbaord?
Unfortunately, I suspect you cannot get to a command line on your
ReadyNAS to look at the NFS server settings to try to resolve this. If
you are prepared to change back to using SAMBA, I cannot see why this
wouldn't work. I'd be happy to run through SAMBA mounts with you.
------------------------------------------------------------------------
Krisbee's Profile: http://forums.slimdevices.com/member.php?userid=59080
View this thread: http://forums.slimdevices.com/showthread.php?t=101624
_______________________________________________
unix mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/unix
