TerraMaster Forum

Any update on this please?
Would be nice if such NFS startup config issues are consolidated here, and not spread over various threads, as users will loose tracks and not get notified.

Thanks for feedback on this blocking problem (is worse now than it used to be, as we had a working workaround before...)

macmpi wrote: ↑03 Sep 2020, 21:30 Any update on this please?
Would be nice if such NFS startup config issues are consolidated here, and not spread over various threads, as users will loose tracks and not get notified.

For your information, we did many testings in this week, TNAS NFS service works properly after every startup.

TMroy wrote: ↑04 Sep 2020, 18:38 For your information, we did many testings in this week, TNAS NFS service works properly after every startup.

Thanks for update. I guess that was 4.1.30 on both x86 and ARM, ext4 and btrfs?
Do you mean we are left with no other option than yet-again trying to re-install the whole TOS from scratch (and redo any NAS config), as I already did for 4.1.24 (with no more success at that time)?

Please fix this problem. I have it on F4-210 4.2.06_2011031755 and
all previous versions. Others have it too despite your "it doesn't happen here!"

You have a problem please fix it. These software issues spoil the hardware.

Looking at /var/log/messages I see the following message whenever I try to access a NFS share:
"TNAS daemon.warn rpc.mountd[3027]: refused mount request from 192.168.1.2 for /mnt/md0/gWork (/mnt/md0/gWork): unmatched host"

But if I restart the NFS service I get connected and this is in /var/log/messages:
"TNAS daemon.notice rpc.mountd[30139]: authenticated mount request from 192.168.1.2:708 for /mnt/md0/gVideo (/mnt/md0/gWork)"

Does this help?

Since the mentioned issue could not be duplicated here, could you please let us check it remotely? Please send an email to support(at)terra-master.com to confirm it.

I (again) took the plunge, and reinstalled 4.2.06 from scratch after restoring my F2-210 NAS to defaults.
Guess what?... NFS service would still NOT start properly at boot.
If I manually disable and then re-enable, then service starts properly and NFS shares can be mounted on my client machines.

So we are still at same discouraging failing status.

The NFS service would not be enabled automatically the first time after reinstallation. It will be enabled automatically after manually enable it.

TMSupport wrote: ↑01 Dec 2020, 18:22 It will be enabled automatically after manually enable it.

Sorry but no: I've powered OFF, then ON, or restarted my NAS several times since install & setup: NFS service is still not functioning automatically at startup.

You can try to clear the browser cache.