You are not logged in.
Hi,
I'm using an Arch Linux laptop client (static IP=192.168.0.81) with a Raspberry Pi NFS server (static IP=192.168.0.69) and I am trying to mount a remote partition on the Pi to use as a NAS.
When I set it up earlier, it worked fine without issues. Then I rebooted my client laptop (not the Pi), and since then I have not been able to mount the drive. Since then I have tried rebooting both multiple times but to no avail.
laptop:
laptop $ ping 192.168.0.69
PING 192.168.0.69 (192.168.0.69) 56(84) bytes of data.
64 bytes from 192.168.0.69: icmp_seq=1 ttl=64 time=23.7 ms
laptop $ showmount -e 192.168.0.69
Export list for 192.168.0.69:
/srv/nfs 192.168.0.81
laptop $ sudo mount 196.168.0.69:/srv/nfs /mnt/nas -v
mount.nfs: timeout set for Sun Apr 19 20:48:19 2026
mount.nfs: trying text-based options 'vers=4.2,addr=196.168.0.69,clientaddr=192.168.0.81'
mount.nfs: mount(2): Connection timed out
mount.nfs: Connection timed out for 196.168.0.69:/srv/nfs on /mnt/nasI have the following /etc/exports file, but otherwise stock config:
/srv/nfs 192.168.0.81(rw,sync,no_root_squash)The server shows as active with exit code 0:
raspberrypi $ sudo systemctl status nfs-server.service
● nfs-server.service - NFS server and services
Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; preset: enabled)
Drop-In: /run/systemd/generator/nfs-server.service.d
└─order-with-mounts.conf
Active: active (exited) since Sun 2026-04-19 20:54:32 BST; 2min 22s ago
Invocation: 8f50ce87801f41b597f6ef7fba821116
Docs: man:rpc.nfsd(8)
man:exportfs(8)
Process: 1182 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS)
Process: 1184 ExecStart=/bin/sh -c /usr/sbin/nfsdctl autostart || /usr/sbin/rpc.nfsd (code=exited, status=0/SUCCESS)
Main PID: 1184 (code=exited, status=0/SUCCESS)
CPU: 45ms
Apr 19 20:54:32 danrasp systemd[1]: Starting nfs-server.service - NFS server and services...
Apr 19 20:54:32 danrasp sh[1185]: nfsdctl: lockd configuration failure
Apr 19 20:54:32 danrasp systemd[1]: Finished nfs-server.service - NFS server and services.The required ports appear to be open on the server
raspberrypi $ rpcinfo -p
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 38627 status
100024 1 tcp 54879 status
100005 1 udp 39929 mountd
100005 1 tcp 57453 mountd
100005 2 udp 33987 mountd
100005 2 tcp 55853 mountd
100005 3 udp 48863 mountd
100005 3 tcp 57089 mountd
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100227 3 tcp 2049 nfs_acl
100003 3 udp 2049 nfs
100227 3 udp 2049 nfs_acl
100021 1 udp 36073 nlockmgr
100021 3 udp 36073 nlockmgr
100021 4 udp 36073 nlockmgr
100021 1 tcp 37685 nlockmgr
100021 3 tcp 37685 nlockmgr
100021 4 tcp 37685 nlockmgrKernel modules are on the client and the client service is up
laptop $ lsmod | grep nfs
nfsv4 1351680 2
dns_resolver 16384 1 nfsv4
nfs 716800 3 nfsv4
lockd 192512 1 nfs
nfs_localio 40960 1 nfs
sunrpc 897024 11 nfs_localio,nfsv4,auth_rpcgss,lockd,rpcsec_gss_krb5,nfs
netfs 626688 1 nfs
laptop $ $ systemctl status nfs-client.target
● nfs-client.target - NFS client services
Loaded: loaded (/usr/lib/systemd/system/nfs-client.target; enabled; preset: disabled)
Active: active since Sun 2026-04-19 21:00:16 BST; 8min ago
Invocation: e6cca001366a477ebad33d4c99dd234b
Apr 19 21:00:16 DAN-LNX systemd[1]: Reached target NFS client services.I'm a bit stumped at what the problem could be. Any advice on debugging would be greatly appreciated!
Offline
First make sure that the NFS server is actually listening on your server:
ss -l -t -n -p | grep 2049because the "showmount" command only contacts the RPC server (via port 111).
Offline