Lestrad wrote:
> Here's what I get:
> ---------------------
> [root@soa-wandboard /]# mount -t nfs -v -o vers=3 192.168.0.15:/media
> mnt/netnas
> mount.nfs: timeout set for Wed Apr 1 11:49:20 2015
> 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
> [root@soa-wandboard /]# journalclt -n 50
> -bash: journalclt: command not found
> [root@soa-wandboard /]# journalctl -n 50
> -- Logs begin at Thu 1970-01-01 01:00:13 CET, end at Wed 2015-04-01
> 11:47:21 CES
> Apr 01 11:46:32 soa-wandboard systemd[14926]: Stopping Basic System.
> Apr 01 11:46:32 soa-wandboard systemd[14926]: Stopped target Basic
> System.
> Apr 01 11:46:32 soa-wandboard systemd[14926]: Stopping Timers.
> Apr 01 11:46:32 soa-wandboard systemd[14926]: Stopped target Timers.
> Apr 01 11:46:32 soa-wandboard systemd[14926]: Stopping Sockets.
> Apr 01 11:46:32 soa-wandboard systemd[14926]: Stopped target Sockets.
> Apr 01 11:46:32 soa-wandboard systemd[14926]: Stopping Paths.
> Apr 01 11:46:32 soa-wandboard systemd[14926]: Stopped target Paths.
> Apr 01 11:46:32 soa-wandboard systemd[14926]: Received SIGRTMIN+24 from
> PID 1498
> Apr 01 11:46:32 soa-wandboard systemd[14927]:
> pam_unix(systemd-user:session): se
> Apr 01 11:46:32 soa-wandboard systemd[1]: Stopped User Manager for UID
> 0.
> Apr 01 11:46:32 soa-wandboard systemd[1]: Stopping user-0.slice.
> Apr 01 11:46:32 soa-wandboard systemd[1]: Removed slice user-0.slice.
> Apr 01 11:46:58 soa-wandboard sshd[14993]: Accepted password for root
> from 192.1
> Apr 01 11:46:58 soa-wandboard sshd[14993]: pam_unix(sshd:session):
> session opene
> Apr 01 11:46:58 soa-wandboard systemd[1]: Starting user-0.slice.
> Apr 01 11:46:58 soa-wandboard systemd[1]: Created slice user-0.slice.
> Apr 01 11:46:58 soa-wandboard systemd[1]: Failed to reset devices.list
> on /syste
> Apr 01 11:46:58 soa-wandboard systemd-logind[244]: New session c11 of
> user root.
> Apr 01 11:46:58 soa-wandboard systemd[1]: Starting Session c11 of user
> root.
> Apr 01 11:46:58 soa-wandboard systemd[1]: Failed to set
> memory.limit_in_bytes on
> Apr 01 11:46:58 soa-wandboard systemd[1]: Started Session c11 of user
> root.
> Apr 01 11:46:58 soa-wandboard systemd[1]: Starting User Manager for UID
> 0...
> Apr 01 11:46:58 soa-wandboard systemd[1]: Failed to reset devices.list
> on /syste
> Apr 01 11:46:58 soa-wandboard systemd[14995]:
> pam_unix(systemd-user:session): se
> Apr 01 11:46:59 soa-wandboard systemd[14995]: Starting Paths.
> Apr 01 11:46:59 soa-wandboard systemd[14995]: Reached target Paths.
> Apr 01 11:46:59 soa-wandboard systemd[14995]: Starting Timers.
> Apr 01 11:46:59 soa-wandboard systemd[14995]: Reached target Timers.
> Apr 01 11:46:59 soa-wandboard systemd[14995]: Starting Sockets.
> Apr 01 11:46:59 soa-wandboard systemd[14995]: Reached target Sockets.
> Apr 01 11:46:59 soa-wandboard systemd[14995]: Starting Basic System.
> Apr 01 11:46:59 soa-wandboard systemd[14995]: Reached target Basic
> System.
> Apr 01 11:46:59 soa-wandboard systemd[14995]: Starting Default.
> Apr 01 11:46:59 soa-wandboard systemd[14995]: Reached target Default.
> Apr 01 11:46:59 soa-wandboard systemd[14995]: Startup finished in
> 269ms.
> Apr 01 11:46:59 soa-wandboard systemd[1]: Started User Manager for UID
> 0.
> Apr 01 11:47:20 soa-wandboard systemd[1]: Starting NFS status monitor
> for NFSv2/
> Apr 01 11:47:20 soa-wandboard rpc.statd[15007]: Version 1.3.2 starting
> Apr 01 11:47:20 soa-wandboard rpc.statd[15007]: Flags: TI-RPC
> Apr 01 11:47:20 soa-wandboard rpc.statd[15007]: Running as root. chown
> /var/lib
> Apr 01 11:47:20 soa-wandboard rpc.statd[15007]: failed to create RPC
> listeners,
> Apr 01 11:47:20 soa-wandboard systemd[1]: rpc-statd.service: control
> process exi
> Apr 01 11:47:20 soa-wandboard systemd[1]: Failed to start NFS status
> monitor for
> Apr 01 11:47:20 soa-wandboard systemd[1]: Unit rpc-statd.service entered
> failed
> Apr 01 11:47:20 soa-wandboard systemd[1]: rpc-statd.service failed.
> Apr 01 11:47:20 soa-wandboard rpc.statd[15009]: Version 1.3.2 starting
> Apr 01 11:47:20 soa-wandboard rpc.statd[15009]: Flags: TI-RPC
> Apr 01 11:47:21 soa-wandboard rpc.statd[15009]: Running as root. chown
> /var/lib
> Apr 01 11:47:21 soa-wandboard rpc.statd[15009]: failed to create RPC
> listeners,
> lines 29-51/51 (END)
>
> -----------------------------------
Well there's no evidence of what happened there, but I notice
rpc-statd.service failed. You need to check your NFS configuration from
the Wandboard as root:
1. What versions does the NFS server work with?
Code:
--------------------
rpcinfo -u 192.168.0.15 nfs
--------------------
2. Are the exported NFS shares visible on the Wandboard?
Code:
--------------------
showmount -e 192.168.0.15
--------------------
3. The NFS export file on your NAS. That's "/etc/exports" on a standard
Linux install, but might be somewhere else on your NAS. If you can get
to the command line of your NAS as root, use the find command file to
locate it ,and then list it with a cat command, e.g.
Code:
--------------------
find / -name exports -type f
--------------------
------------------------------------------------------------------------
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
