I find t that after some time, the client on which my NAS folders are mounted (a Macbook) runs into a connection error and loses the mounts.
Running Macbook 16" 2019 with Big Sur 11.2.3 (20D91).
When the mounts are lost, I find I can still ping the NAS.
After connectivity is lost, I log into TOS and may see the Samba file server as disabled. I try to restart with the TOS user interface, but it does not succeed. The UI shows an attempt to connect, but the checkbox refreshes to unchecked.
Checking the service from the Service Status panel shows that Samba is disabled.
I SSHed into the NAS as root and ran a Samba restart command, then Samba start command, and the following is returned:
Code: Select all
[root@musicinas ~]# /etc/init.d/samba restart
Reloading smb.conf file: killall: smbd: no process killed
killall: nmbd: no process killed
0
0
start-stop-daemon: unable to close pidfile '/var/run/samba.pid' (No space left on device)
start-stop-daemon: child returned error exit status 2
/etc/init.d/functions: line 611: echo: write error: No space left on device
start-stop-daemon: unable to close pidfile '/var/run/samba.pid' (No space left on device)
start-stop-daemon: child returned error exit status 2
/etc/init.d/functions: line 611: echo: write error: No space left on device
[root@musicinas ~]# /etc/init.d/samba start
0
0
start-stop-daemon: unable to close pidfile '/var/run/samba.pid' (No space left on device)
start-stop-daemon: child returned error exit status 2
/etc/init.d/functions: line 611: echo: write error: No space left on device
start-stop-daemon: unable to close pidfile '/var/run/samba.pid' (No space left on device)
start-stop-daemon: child returned error exit status 2
/etc/init.d/functions: line 611: echo: write error: No space left on device
At this point, the only option is to restart the NAS completely. I usually have to restart the NAS about 2 or 3 times a day.
