I fired up my Proxmox server and it complained that the nfs was not there.
Ran systemctl status nfs-server on the Zimaboard and low and behold:
○ nfs-server.service - NFS server and services
Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; :5:185mdisabled; preset: :5:185mdisabled)
Drop-In: /run/systemd/generator/nfs-server.service.d
└─order-with-mounts.conf
Active: inactive (dead)
Docs: man:rpc.nfsd(8)
man:exportfs(8)
Looks like something broke NFS:
gbdecker@ZimaBoard2:/var/lib/casaos_data/.media/Fast-Storage ➜ $ ls -l /usr/sbin/nfsdctl
ls: cannot access ‘/usr/sbin/nfsdctl’: No such file or directory
gbdecker@ZimaBoard2:/var/lib/casaos_data/.media/Fast-Storage ➜ $
Going to try and go back to 1.6.1 
Thanks for your feedback. For security reasons, we disabled the nfs service. You can run the following three commands, then restart the machine, and the nfs service will be activated
sudo systemctl enable nfs-server.service
sudo systemctl enable nfs-blkmap.service
sudo systemctl enable nfs-client.target
Still getting active (exited), it seem nfsdctl is the missing piece.
○ nfs-server.service - NFS server and services
Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; :5:185mdisabled; preset: :5:185mdisabled)
Drop-In: /run/systemd/generator/nfs-server.service.d
● nfs-server.service - NFS server and services
Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; :5:185mdisabled; preset: :5:185mdisabled)
Drop-In: /run/systemd/generator/nfs-server.service.d
└─order-with-mounts.conf
Active: active (exited) since Fri 2026-07-03 05:50:44 CDT; 5s ago
Invocation: 61364802f03148fab115e596395c2b0a
Docs: man:rpc.nfsd(8)
● nfs-server.service - NFS server and services
Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; :5:185mdisabled; preset: :5:185mdisabled)
Drop-In: /run/systemd/generator/nfs-server.service.d
● nfs-server.service - NFS server and services
Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; :5:185mdisabled; preset: :5:185mdisabled)
Drop-In: /run/systemd/generator/nfs-server.service.d
└─order-with-mounts.conf
Active: active (exited) since Fri 2026-07-03 05:51:56 CDT; 2s ago
Invocation: 0b3bbbf32e0b47e49e3b5a94644e1d6e
Docs: man:rpc.nfsd(8)
man:exportfs(8)
Process: 5602 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS)
Process: 5614 ExecStart=/bin/sh -c /usr/sbin/nfsdctl autostart || /usr/sbin/rpc.nfsd (code=exited, status=0/SUCCESS)
Main PID: 5614 (code=exited, status=0/SUCCESS)
Mem peak: 2.3M
CPU: 18ms
Jul 03 05:51:56 ZimaBoard2 systemd[1]: Starting NFS server and services…
Jul 03 05:51:56 ZimaBoard2 sh[5623]: /bin/sh: line 1: /usr/sbin/nfsdctl: No such file or directory
Jul 03 05:51:56 ZimaBoard2 systemd[1]: Finished NFS server and services.
Just an update, I reverted back to 1.6.1 and NFS is back up and running, and my Proxmox server is happy about that. Life is good.
Hi, the nfsdctl error does not affect the start of the nfs service. In fact, the nfs service starts normally
Interesting, it didn’t seem to be the case for me. But, it’s a moot point now since I have gone back to 1.6.1
Hi, if you need to use the newer version again in the future, please refer to the following commands to handle the NFS service. We have rechecked the related steps, and the previously provided commands need some adjustments for the current environment:
sudo systemctl enable nfs-server.service
sudo systemctl enable nfs-blkmap.service
sudo systemctl enable nfs-client.target
We sincerely apologize for any inconvenience caused and appreciate your understanding.
Thanks Dina, I will save this message should I want to try again at a later time. You have not caused me any trouble. Sometimes I wonder off thinking I’m capable of handling beta software, when I should just stick with the stable version. I am enjoying my Zimaboard2 as a NAS very much. I do play around with dockers once in a while, but nothing found that is useful long term. Thanks again! 
Just verfying with you Dina that I did a fresh install of 1.6.1 yesterday and then upgraded to 1.6.2 just now and then sending the systemctl commands above and a reboot and all is working as it should. Thanks for all your help.