TerraMaster Forum

Would you try to disable the NFS and enable it again? and let me know this work or not. thank you!

Sure I tried, but did not fix the issue.
The only solution thus far, and as explained previously on page 2, is to do under ssh from root account: Hope next versions will fix this for good.
Thanks.

hi macmpi,
We have found the cause of this failure, we will fix it in next update. Thank you very much for your report!

I just want to thank all the users of this product that took the time to troubleshoot the NFS failure. I am a home user, so the bug wasn't on my priority list, and I just kept going back into TOS gui and re enabling NFS. I also have a F2-210 and enabling NFS service under root via SSH shell worked. I also see the weird error about group "nobody"

Starting NFS daemon: rpc.idmapd: conf_set: duplicate tag [Mapping]:, ignoring...
rpc.idmapd: conf_set: duplicate tag [Translation]:, ignoring...
rpc.idmapd: Could not find group "nobody"

Thanks again to all the hard work, especially macmpi.

And the thank you was short lived due to TerraMaster development. I installed the 4.1.27 firmware today and it has fixed the NFS enable on boot service, but its not starting up the nfs shares on the server end. I'm am not very technical in this aspect but after reboot /etc/init.d/nfs
root@TNAS-010790:/home/admin# /etc/init.d/nfs status
nfsd is running
however I cannot connect from my client and the mount -a option shows connection timeout.
running
root@TNAS-010790:/home/admin# /etc/init.d/nfs start
Starting rpcbind: rpcbind: another rpcbind is already running. Aborting
FAIL
Starting NFS statd: Statd service already running!
FAIL
Starting NFS mountd: OK
Starting NFS daemon: rpc.idmapd: Could not find group "nobody"
fixes this issue. So instead of being able to go into root via SSH shell and set NFS to enable, now its always enabled at boot, but still not providing connections to the share without restarting.

How many iterations of firmware until such a simplistic part of linux will be functioning as expected?

So I have tinkered with this quite a bit. I refreshed my whole TNAS back to a clean install of the new 4.1.27 firmware and still have the same issue as mentioned before.
1. NFS daemon is now starting at boot as it should evidenced by the following:

[michael@vmserver ~]$ ssh [email protected] -p 9222
Wellcom to TNAS
root@TNAS-010790:~# /etc/init.d/nfs status
nfsd is running
root@TNAS-010790:~#

2. NFS shares are not available even though daemon is running:

root@TNAS-010790:~# showmount -e
Hosts on TNAS-010790:
root@TNAS-010790:~#

michael@desktop:~$ showmount -e 192.168.1.80
Export list for 192.168.1.80:
michael@desktop:~$

3, Trying to mount a share provides a new error that does not show up much in google. Notice I tried to mount in verbose mode and get a one line response.

michael@desktop:~$ sudo mount -t nfs -v -o nfsvers=3 192.168.1.80:/mnt/md0/Pictures /home/michael/Pictures
[sudo] password for michael:
mount.nfs: access denied by server while mounting (null)

4. Going in to root@TNAS-010790 and running /etc/init.d/reload OR going into the TNAS TOS web page and unchecking the NFS tiick box hitting apply, the reselecting and it apply fix this issue. Now when I do the show mount:

root@TNAS-010790:/etc# showmount -e
Export list for TNAS-010790:
/mnt/md0/Documents *
/mnt/md0/Downloaded_Programs 192.168.*.*,*.home.intranet
/mnt/md0/Video 192.168.*.*,*.home.intranet
/mnt/md0/Pictures 192.168.1.0/24
/mnt/md0/Music 192.168.*.*,*.home.intranet,192.168.1.0/24
root@TNAS-010790:/etc#

michael@desktop:~$ showmount -e 192.168.1.80
Export list for 192.168.1.80:
/mnt/md0/Documents *
/mnt/md0/Downloaded_Programs 192.168.*.*,*.home.intranet
/mnt/md0/Video 192.168.*.*,*.home.intranet
/mnt/md0/Pictures 192.168.1.0/24
/mnt/md0/Music 192.168.*.*,*.home.intranet,192.168.1.0/24
michael@desktop:~$

And running mount will function as aspected:

root@TNAS-010790:/etc# /etc/init.d/nfs reload
Starting rpcbind: rpcbind: another rpcbind is already running. Aborting
FAIL
Starting NFS statd: Statd service already running!
FAIL
Starting NFS mountd: OK
Starting NFS daemon: root@TNAS-010790:/etc#

michael@desktop:~$ sudo mount -t nfs -v -o nfsvers=3 192.168.1.80:/mnt/md0/Documents /home/michael/Documents
mount.nfs: timeout set for Wed Jul 8 16:13:59 2020
mount.nfs: trying text-based options 'nfsvers=3,addr=192.168.1.80'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.1.80 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.1.80 prog 100005 vers 3 prot UDP port 36700
mount.nfs: mount(2): Device or resource busy

Directory shows busy because it was already previously mounted as automount in the fstab file. If I select the directly it now will grant access to the NFS share on the TNAS

What I have found is that when the TNAS device restarts the NFS daemon starts up correctly, however the /etc/exports file is empty and the export data exists at /etc/exports.tmp
Moving exports.tmp to exports and re initiating with exportfs -a does nothing.

Please help. I am very tired and frustrated that the NFS function has not worked as expected, and I should not have to turn off the NFS and turn it back on in the TOS web app config panel evey time I reboot the TNAS device.

As we can't duplicate your issue here, so please send an email to support(a)terra-master.com with the detailed information, we would like to have a remote session for you to check what's going on there.

I confirm the issue persist on 4.1.30
This is very frustrating after so long time report and incremental releases.

Indeed NAS service appears to be started as @michaels2408 mentioned but shares are not accessible to clients.
Only manual/Web Interface restart at each reboot fixes it: that's not what is expected from a NAS server.

macmpi wrote: ↑26 Aug 2020, 21:19 I confirm the issue persist on 4.1.30
This is very frustrating after so long time report and incremental releases.

Indeed NAS service appears to be started as @michaels2408 mentioned but shares are not accessible to clients.
Only manual/Web Interface restart at each reboot fixes it: that's not what is expected from a NAS server.

Please refer to this post viewtopic.php?f=23&t=715, your issue does not happen to him, so I guess this is a comment issue, if you can provide more input, that will be appreciated, for example, what application you have installed on your tnas, and did you delete any app recently? what other settings you did on your tnas device? we are very interested to see how it happened, a remote session is ok for you?

TMroy wrote: ↑27 Aug 2020, 22:03Please refer to this post

Well, it seems people there have issues too.

My setup is very basic.
As you can remember in this thread, I made full stock re-install of 4.1.24, and again had to manually manually tweak setup to enable NFS at boot: Since then I updated to 4.1.30, and discovered that, despite the trick, NFS was not available at boot.
I removed the trick:, and flipped NFS off/on with UI.
After restart, NFS service reports it's running, and several items look correct... but, as before, client can NOT connect.
I have to flip NFS off/on again with UI to have service properly running.
So something is still not started properly at boot.

Something strange to note though: when service works correctly (after UI flip), note the slight output difference: