Krisbee wrote:
> 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.
Thanks Krisbee
This seems to be the relevant bit of journalctl:
Code:
--------------------
Apr 01 10:25:35 soa-wandboard systemd[1]: Starting RPC Port Mapper.
Apr 01 10:25:35 soa-wandboard systemd[1]: Reached target RPC Port Mapper.
Apr 01 10:25:35 soa-wandboard systemd[1]: Starting Host and Network Name
Lookups.
Apr 01 10:25:35 soa-wandboard systemd[1]: Reached target Host and Network
Name Lookups.
Apr 01 10:25:35 soa-wandboard systemd[1]: Starting NFS status monitor for
NFSv2/3 locking....
Apr 01 10:25:35 soa-wandboard rpc.statd[538]: Version 1.3.2 starting
Apr 01 10:25:35 soa-wandboard rpc.statd[538]: Flags: TI-RPC
Apr 01 10:25:35 soa-wandboard rpc.statd[538]: Failed to read
/var/lib/nfs/state: Success
Apr 01 10:25:35 soa-wandboard rpc.statd[538]: Initializing NSM state
Apr 01 10:25:35 soa-wandboard rpc.statd[538]: Running as root. chown
/var/lib/nfs to choose different user
Apr 01 10:25:35 soa-wandboard rpc.statd[538]: failed to create RPC listeners,
exiting
Apr 01 10:25:35 soa-wandboard systemd[1]: rpc-statd.service: control process
exited, code=exited status=1
Apr 01 10:25:35 soa-wandboard systemd[1]: Failed to start NFS status monitor
for NFSv2/3 locking..
Apr 01 10:25:35 soa-wandboard systemd[1]: Unit rpc-statd.service entered
failed state.
Apr 01 10:25:35 soa-wandboard systemd[1]: rpc-statd.service failed.
Apr 01 10:25:35 soa-wandboard rpc.statd[540]: Version 1.3.2 starting
Apr 01 10:25:35 soa-wandboard rpc.statd[540]: Flags: TI-RPC
Apr 01 10:25:35 soa-wandboard rpc.statd[540]: Running as root. chown
/var/lib/nfs to choose different user
Apr 01 10:25:35 soa-wandboard rpc.statd[540]: failed to create RPC listeners,
exiting
--------------------
the output from the mount command:
Code:
--------------------
[root@soa-wandboard ~]# mount -t nfs -o vers=3 192.168.0.198:/c/media
/mnt/disk1
Job for rpc-statd.service failed. See "systemctl status rpc-statd.service"
and "journalctl -xe" for details.
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: an incorrect mount option was specified
--------------------
I can get to a command line on the readynas if that will help
I can get a SAMBA (cifs) mount working - it just won't work with hi-res
files without constant rebuffering - it has been suggested that an nfs
mount MIGHT cure this - hence the attempts to get nfs working.
------------------------------------------------------------------------
steve-g's Profile: http://forums.slimdevices.com/member.php?userid=52057
View this thread: http://forums.slimdevices.com/showthread.php?t=101624
_______________________________________________
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix
