Creating a bug report/issue
I have searched the existing open and closed issues
Required Information
DietPi version | cat /boot/dietpi/.version
G_DIETPI_VERSION_CORE=10
G_DIETPI_VERSION_SUB=0
G_DIETPI_VERSION_RC=1
G_GITBRANCH=‘master’
G_GITOWNER=‘MichaIng’
Distro version | echo $G_DISTRO_NAME $G_RASPBIAN
Kernel version | uname --all
Linux homeserver 6.18.7-current-rockchip64 #1 SMP PREEMPT Fri Jan 23 10:21:37 UTC 2026 aarch64 GNU/Linux
Architecture | dpkg --print-architecture
SBC model | echo $G_HW_MODEL_NAME or (EG: RPi3)
Power supply used | (EG: 5V 1A RAVpower)
SD card used | (EG: SanDisk ultra)
Additional Information (if applicable)
Software title | (EG: Nextcloud)
Was the software title installed freshly or updated/migrated?
Can this issue be replicated on a fresh installation of DietPi?
Bug report ID | echo $G_HW_UUID
274176ed-1e76-4da1-abf4-f929c0c78bb8
Steps to reproduce
install nfs-server
start it
look into `systemctl status nfs-server`
Expected behaviour
nfs-server goes into state `active (running)`, clients can connect
Actual behaviour
clients can’t connect, nfs-server is in state `active (exited)`
Extra details
systemctl status shows `sh[31752]: nfsdctl: lockd configuration failure`
Jappe
27 January 2026 01:30
2
I have the same message in log but I can connect
Server:
root@DietPi:~# journalctl -u nfs-server.service
Jan 27 01:22:59 DietPi systemd[1]: Starting nfs-server.service - NFS server and services...
Jan 27 01:22:59 DietPi exportfs[1615]: exportfs: can't open /etc/exports for reading
Jan 27 01:22:59 DietPi sh[1618]: nfsdctl: lockd configuration failure
Jan 27 01:22:59 DietPi systemd[1]: Finished nfs-server.service - NFS server and services.
Jan 27 01:23:00 DietPi systemd[1]: Stopping nfs-server.service - NFS server and services...
Jan 27 01:23:00 DietPi systemd[1]: nfs-server.service: Deactivated successfully.
Jan 27 01:23:00 DietPi systemd[1]: Stopped nfs-server.service - NFS server and services.
Jan 27 01:23:01 DietPi systemd[1]: Starting nfs-server.service - NFS server and services...
Jan 27 01:23:02 DietPi sh[1922]: nfsdctl: lockd configuration failure
Jan 27 01:23:02 DietPi systemd[1]: Finished nfs-server.service - NFS server and services.
root@DietPi:~# 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 Tue 2026-01-27 01:23:02 UTC; 8min ago
Invocation: f1a6417d69814e3f8fc7d6ade7dbdf65
Docs: man:rpc.nfsd(8)
man:exportfs(8)
Process: 1919 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS)
Process: 1920 ExecStart=/bin/sh -c /usr/sbin/nfsdctl autostart || /usr/sbin/rpc.nfsd (code=exited, status=0/SUCCESS)
Main PID: 1920 (code=exited, status=0/SUCCESS)
Mem peak: 1.7M
CPU: 55ms
Jan 27 01:23:01 DietPi systemd[1]: Starting nfs-server.service - NFS server and services...
Jan 27 01:23:02 DietPi sh[1922]: nfsdctl: lockd configuration failure
Jan 27 01:23:02 DietPi systemd[1]: Finished nfs-server.service - NFS server and services.
Client:
root@RPi4:~# dietpi-drive_manager
[ INFO ] DietPi-Drive_Manager | Detecting drives, please wait...
[ INFO ] DietPi-Drive_Manager | - Detected mounted physical drive: /dev/sda2 > /
[ INFO ] DietPi-Drive_Manager | - Detected mounted physical drive: /dev/sda1 > /boot/firmware
[ INFO ] DietPi-Drive_Manager | - Detected mounted physical drive: /dev/sdb > /mnt/raid
[ INFO ] DietPi-Drive_Manager | - Detected unmounted drive: /dev/sdc
[ OK ] DietPi-Drive_Manager | mv .fstab /etc/fstab
[ OK ] DietPi-Drive_Manager | systemctl daemon-reload
[ INFO ] DietPi-Drive_Manager | Checking for required APT packages: e2fsprogs
[ INFO ] DietPi-Drive_Manager | Checking for required APT packages: nfs-common netbase
[ OK ] DietPi-Drive_Manager | Desired setting in /boot/dietpi/.installed was already set: aSOFTWARE_INSTALL_STATE[110]=2
[ INFO ] DietPi-Drive_Manager | Scanning for NFS exports by: 192.168.178.32
NB: If the server cannot be reached correctly, this may take up to 90 seconds before it times out.
[ OK ] DietPi-Drive_Manager | mkdir /mnt/nfs_client
[ INFO ] DietPi-Drive_Manager | Detecting drives, please wait...
[ INFO ] DietPi-Drive_Manager | - Detected mounted physical drive: /dev/sda2 > /
[ INFO ] DietPi-Drive_Manager | - Detected mounted physical drive: /dev/sda1 > /boot/firmware
[ INFO ] DietPi-Drive_Manager | - Detected mounted physical drive: /dev/sdb > /mnt/raid
[ INFO ] DietPi-Drive_Manager | - Detected mounted network drive: 192.168.178.32:/mnt/dietpi_userdata > /mnt/nfs_client
[ INFO ] DietPi-Drive_Manager | - Detected unmounted drive: /dev/sdc
[ OK ] DietPi-Drive_Manager | mv .fstab /etc/fstab
[ OK ] DietPi-Drive_Manager | systemctl daemon-reload
root@RPi4:~# ls /mnt/nfs_client/
insgesamt 28
drwxrwxr-x 2 dietpi dietpi 4096 2. Nov 23:33 downloads
drwxrwxr-x 2 dietpi dietpi 4096 2. Nov 23:33 Music
drwxrwxr-x 2 dietpi dietpi 4096 2. Nov 23:33 Pictures
drwxr-xr-x 3 _apt systemd-network 4096 25. Jan 16:47 postgresql
drwxr-xr-x 4 988 988 4096 25. Jan 16:50 synapse
drwxr-xr-x 5 987 987 4096 27. Jan 02:23 uptime-kuma
drwxrwxr-x 2 dietpi dietpi
Can you share from the server
journalctl -u nfs-server
Jappe
27 January 2026 02:40
3
pkoevesdi:
Actual behaviour
clients can’t connect, nfs-server is in state active (exited)
Ah wait, this is expected since it’s a one shot service, this is not malfunction.
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStartPre=-/usr/sbin/exportfs -r
ExecStart=/bin/sh -c '/usr/sbin/nfsdctl autostart || /usr/sbin/rpc.nfsd'
ExecStop=/bin/sh -c '/usr/sbin/nfsdctl threads 0 || /usr/sbin/rpc.nfsd 0'
ExecStopPost=/usr/sbin/exportfs -au
ExecStopPost=/usr/sbin/exportfs -f
ExecReload=-/usr/sbin/exportfs -r
So the service is not the reason why your clients can not connect.
On you client, what gives you showmount command?
On the server, check if the server is running:
cat /proc/fs/nfsd/threads
ps -ef | grep '\[nfsd\]'
cat /proc/fs/nfsd/versions
And is the export active:
exportfs -v
anf if it’s listening
ss -lntup | grep 2049
Thank you so far too enlighten this a bit. All looks good, nfs is running and listening. Sorry for reporting in the wrong direction.
I’ll look at the clients later today.
Still the coincidence with the update of dietpi remains…
Ok, so now the clients connect again. I can’t explain, what happened, but after working for years, they stopped working at the update of dietpi to version 10. Now, two days later, they work again, I didn’t change anything on the system. Whatever, topic can be closed and thanks for looking at it.
1 Like