NFS service issues at NAS startup
Re: NFS service issues at NAS startup
any update on this issue?
Suggestion on a workaround?
Thanks
Suggestion on a workaround?
Thanks
TerraMaster F2-210 under TOS 4.2.43, RAID1, Btrfs, serving Mac, Linux & Windows clients
Re: NFS service issues at NAS startup
According to the results here, NFS service should be re-enabled after TNAS is rebooted to allow the clients to be connected. Sorry for all the troubles.
To contact our team, please send email to following addresses, remember to replace (at) with @
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Re: NFS service issues at NAS startup
Thanks for feedback.
So, this qualifies as a bug, right?
(can't think this could be a feature for a server: all those services should be available at boot if previously activated).
Hope this will be in good standing on priority list for fixes in an soon-to-be release.
Would you have any expected timeline for this fix please?
Thanks.
So, this qualifies as a bug, right?
(can't think this could be a feature for a server: all those services should be available at boot if previously activated).
Hope this will be in good standing on priority list for fixes in an soon-to-be release.
Would you have any expected timeline for this fix please?
Thanks.
TerraMaster F2-210 under TOS 4.2.43, RAID1, Btrfs, serving Mac, Linux & Windows clients
Re: NFS service issues at NAS startup
Hi macmpi,
You got the point wrong here. Normally NFS NAS server will not reconnect to NFS client after reboot, as the server couldn't remember the connection, and server is to be connected, not to connect with client. So you need to find a NFS client software which owns feature to reconnect with the server
automatically after server reboot. I hope you can get my point now.
You got the point wrong here. Normally NFS NAS server will not reconnect to NFS client after reboot, as the server couldn't remember the connection, and server is to be connected, not to connect with client. So you need to find a NFS client software which owns feature to reconnect with the server
automatically after server reboot. I hope you can get my point now.
To contact our team, please send email to following addresses, remember to replace (at) with @:
Support team: support(at)terra-master.com (for technical support only)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Support team: support(at)terra-master.com (for technical support only)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Re: NFS service issues at NAS startup
Hi TMRoy,
I think you got the symptom wrong!
There is no way a client can NFS connect to TNAS if TNAS does NOT run the service after boot!
So what needs to be fixed is that TNAS launches the NFS service at reboot (if previously enabled of course), as it does for all other file service (SMB, AFP)
So the issue is 100% on TNAS side.
I hope this is well understood.
Thanks.
I think you got the symptom wrong!
There is no way a client can NFS connect to TNAS if TNAS does NOT run the service after boot!
So what needs to be fixed is that TNAS launches the NFS service at reboot (if previously enabled of course), as it does for all other file service (SMB, AFP)
So the issue is 100% on TNAS side.
I hope this is well understood.
Thanks.
TerraMaster F2-210 under TOS 4.2.43, RAID1, Btrfs, serving Mac, Linux & Windows clients
Re: NFS service issues at NAS startup
on TNAS:
Code: Select all
ls -la /etc/rc.d/
total 8
drwxr-xr-x 2 root root 4096 Mar 19 08:29 .
drwxr-xr-x 59 root root 4096 Apr 22 16:01 ..
lrwxrwxrwx 1 root root 24 Mar 19 08:29 K00rtk-supplicant -> ../init.d/rtk-supplicant
lrwxrwxrwx 1 root root 17 Mar 19 08:29 K00xeninit -> ../init.d/xeninit
lrwxrwxrwx 1 root root 13 Mar 19 08:29 K100shutdn -> ../init.d/rcK
lrwxrwxrwx 1 root root 15 Mar 19 08:29 K10rsync -> ../init.d/rsync
lrwxrwxrwx 1 root root 14 Mar 19 08:29 K50sshd -> ../init.d/sshd
lrwxrwxrwx 1 root root 17 Mar 19 08:29 K90network -> ../init.d/network
lrwxrwxrwx 1 root root 20 Mar 19 08:29 K90sysfixtime -> ../init.d/sysfixtime
lrwxrwxrwx 1 root root 14 Mar 19 08:29 K98boot -> ../init.d/boot
lrwxrwxrwx 1 root root 13 Mar 19 08:29 K99shutdn -> ../init.d/rcK
lrwxrwxrwx 1 root root 16 Mar 19 08:29 K99umount -> ../init.d/umount
lrwxrwxrwx 1 root root 20 Mar 19 08:29 S00sysfixtime -> ../init.d/sysfixtime
lrwxrwxrwx 1 root root 17 Mar 19 08:29 S05xeninit -> ../init.d/xeninit
lrwxrwxrwx 1 root root 17 Mar 19 08:29 S09realtek -> ../init.d/realtek
lrwxrwxrwx 1 root root 14 Mar 19 08:29 S10boot -> ../init.d/boot
lrwxrwxrwx 1 root root 16 Mar 19 08:29 S10system -> ../init.d/system
lrwxrwxrwx 1 root root 20 Mar 19 08:29 S11syscontrol -> ../init.d/syscontrol
lrwxrwxrwx 1 root root 16 Mar 19 08:29 S11sysctl -> ../init.d/sysctl
lrwxrwxrwx 1 root root 14 Mar 19 08:29 S12rpcd -> ../init.d/rpcd
lrwxrwxrwx 1 root root 13 Mar 19 08:29 S13led -> ../init.d/led
lrwxrwxrwx 1 root root 14 Mar 19 08:29 S15lvm2 -> ../init.d/lvm2
lrwxrwxrwx 1 root root 20 Mar 19 08:29 S19btrfs-scan -> ../init.d/btrfs-scan
lrwxrwxrwx 1 root root 17 Mar 19 08:29 S20network -> ../init.d/network
lrwxrwxrwx 1 root root 18 Mar 19 08:29 S30mountusb -> ../init.d/mountusb
lrwxrwxrwx 1 root root 14 Mar 19 08:29 S50cron -> ../init.d/cron
lrwxrwxrwx 1 root root 15 Mar 19 08:29 S50nginx -> ../init.d/nginx
lrwxrwxrwx 1 root root 18 Mar 19 08:29 S50php7-fpm -> ../init.d/php7-fpm
lrwxrwxrwx 1 root root 14 Mar 19 08:29 S60dbus -> ../init.d/dbus
lrwxrwxrwx 1 root root 17 Mar 19 08:29 S60krb5kdc -> ../init.d/krb5kdc
lrwxrwxrwx 1 root root 17 Mar 19 08:29 S60ntpdate -> ../init.d/ntpdate
lrwxrwxrwx 1 root root 22 Mar 19 08:29 S61avahi-daemon -> ../init.d/avahi-daemon
lrwxrwxrwx 1 root root 22 Mar 19 08:29 S93triggerhappy -> ../init.d/triggerhappy
lrwxrwxrwx 1 root root 14 Mar 19 08:29 S95done -> ../init.d/done
lrwxrwxrwx 1 root root 16 Mar 19 08:29 S95smartd -> ../init.d/smartd
lrwxrwxrwx 1 root root 14 Mar 19 08:29 S95wsdd -> ../init.d/wsdd
lrwxrwxrwx 1 root root 17 Mar 19 08:29 S98sysntpd -> ../init.d/sysntpd
lrwxrwxrwx 1 root root 24 Mar 19 08:29 S99rtk-supplicant -> ../init.d/rtk-supplicant
lrwxrwxrwx 1 root root 17 Mar 19 08:29 S99tosboot -> ../init.d/tosboot
Code: Select all
/etc/init.d/nfs
got to root (su -) and:
Code: Select all
./etc/init.d/nfs restart
Shutting down NFS mountd: OK
Shutting down NFS daemon: OK
Shutting down NFS services: OK
Stopping NFS statd: OK
Stopping rpcbind daemon: OK
Starting rpcbind: OK
Starting NFS statd: OK
Starting NFS mountd: OK
Starting NFS daemon: rpc.idmapd: Could not find group "nobody"
Then the final touch:
Code: Select all
./etc/init.d/nfs enable
ls -la /etc/rc.d/
lrwxrwxrwx 1 root root 13 Apr 22 23:08 S60nfs -> ../init.d/nfs
Would be nice if this service is really enabled with the UI: currently the UI says it is enabled, but IS_NOT.
Now I imagine your team can easily fix it?
Thanks for prompt consideration.
TerraMaster F2-210 under TOS 4.2.43, RAID1, Btrfs, serving Mac, Linux & Windows clients
Re: NFS service issues at NAS startup
OK, thanks a lot! will check it soon and come back to you.
To contact our team, please send email to following addresses, remember to replace (at) with @:
Support team: support(at)terra-master.com (for technical support only)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Support team: support(at)terra-master.com (for technical support only)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Re: NFS service issues at NAS startup
Nice work, I was experimenting the same problem.
Re: NFS service issues at NAS startup
Hi macmpi,
We have tested here. the issue you mentioned did not happen here. NFS service was checked and enabled both at front-end and back-end.
We have tested here. the issue you mentioned did not happen here. NFS service was checked and enabled both at front-end and back-end.
To contact our team, please send email to following addresses, remember to replace (at) with @
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Re: NFS service issues at NAS startup
Can you be more specific on TNAS models and SW releases?
See my config in signature.
I'm afraid, I'm not alone with this problem (see @psor for instance).
Maybe it's an older release big that got propagated with firmware updates, or sth.
Anyway, I have it on a standard install for sure...
TerraMaster F2-210 under TOS 4.2.43, RAID1, Btrfs, serving Mac, Linux & Windows clients