steve-g wrote:
> 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,
Ok, as I suspected SOA can have a problem when the option for a NFS
version 3 connections is specified. On the Wandboard you can check what
version of NFS connections your NFS server will accept with this
command:
Code:
--------------------
rpcinfo -u 192.168.0.198 nfs
--------------------
Post your output here. This is mine:
Code:
--------------------
}
[root@soa-rpi ~ # rpcinfo -u 192.168.0.20 nfs
program 100003 version 2 ready and waiting
program 100003 version 3 ready and waiting
program 100003 version 4 ready and waiting
--------------------
You can see my NFS server will work with a version 4 client, which is
what SOA defaults to. If the NFS server on your NAS only works up to
version 3, then SOA needs a bit of tweaking. I'll have to dig out my
notes to remember what additional steps I took to get his to work in the
past.
As to your SAMBA comment and the hi-res files re-buffering problem. I
think I already suggested that adding some options to the CIFS mount
might help with that. It really should be doable by entering the correct
data on the SOA storage page, assuming your SAMAB server config is
right. Also I forgot to ask, but can you remind me if your Wandboard is
using a wired or wireless network connection.
------------------------------------------------------------------------
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
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix
