NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Cant enable SMB on ReadyNas 316
Hi,
I noticed that SMB service on my ReadyNas 316 with version 6.9.3 stopped working 2 days ago and I can't turn it on. At first I didnt see the shares and after reboot, I saw that SMB was turned off.
I have tried to search for any solutions but I cant find one. I really don't want to do an factory reset.
What I tried so far:
- OS Reinstall
- Downgrade from: 6.9.3 -> 6.9.1 -> 6.9.0 -> 6.8.1 and then back to 6.9.3 = None version is working
- Update pagages with "apt upgrade"
When I run "systemctl status -a smb":
root@NAS:~# systemctl status -a smb
smb.service - Samba SMB Daemon
Loaded: loaded (/lib/systemd/system/smb.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2018-04-28 13:18:04 CEST; 49s ago
Process: 8988 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMBDOPTIONS (code=exited, status=1/FAILURE)
Main PID: 8988 (code=exited, status=1/FAILURE)
Apr 28 13:18:03 NAS systemd[1]: Starting Samba SMB Daemon...
Apr 28 13:18:04 NAS systemd[1]: smb.service: Main process exited, code=exited, status=1/FAILURE
Apr 28 13:18:04 NAS systemd[1]: Failed to start Samba SMB Daemon.
Apr 28 13:18:04 NAS systemd[1]: smb.service: Unit entered failed state.
Apr 28 13:18:04 NAS systemd[1]: smb.service: Failed with result 'exit-code'.
When I try to manually start smb.service I get:
root@NAS:~# systemctl start smb
Job for smb.service failed because the control process exited with error code.
See "systemctl status smb.service" and "journalctl -xe" for details.
I find following in journalctl -xe:
Apr 28 13:14:57 NAS systemd[1]: Starting Samba NMB Daemon...
-- Subject: Unit nmb.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit nmb.service has begun starting up.
Apr 28 13:14:58 NAS systemd[1]: nmb.service: Main process exited, code=exited, status=1/FAILURE
Apr 28 13:14:58 NAS systemd[1]: Failed to start Samba NMB Daemon.
-- Subject: Unit nmb.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit nmb.service has failed.
--
-- The result is failed.
Apr 28 13:14:58 NAS systemd[1]: nmb.service: Unit entered failed state.
Apr 28 13:14:58 NAS systemd[1]: nmb.service: Failed with result 'exit-code'.
Apr 28 13:15:09 NAS readynasd[3398]: Service 'nmb.service' goto unexpected state 'failed'. Expect to be 'active'('activating').
Apr 28 13:15:09 NAS readynasd[3398]: Protocol 'cifs' is reloaded
Apr 28 13:15:09 NAS systemd[1]: Starting Samba NMB Daemon...
-- Subject: Unit nmb.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit nmb.service has begun starting up.
Apr 28 13:15:09 NAS systemd[1]: Started WSD/LLMNR Discovery/Name Service Daemon.
-- Subject: Unit wsdd2.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit wsdd2.service has finished starting up.
--
-- The start-up result is done.
Apr 28 13:15:09 NAS wsdd2[8270]: starting.
Apr 28 13:15:09 NAS systemd[1]: nmb.service: Main process exited, code=exited, status=1/FAILURE
Apr 28 13:15:09 NAS systemd[1]: Failed to start Samba NMB Daemon.
-- Subject: Unit nmb.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit nmb.service has failed.
--
-- The result is failed.
Apr 28 13:15:09 NAS systemd[1]: nmb.service: Unit entered failed state.
Apr 28 13:15:09 NAS systemd[1]: nmb.service: Failed with result 'exit-code'.
Apr 28 13:15:09 NAS systemd[1]: Starting Samba SMB Daemon...
-- Subject: Unit smb.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit smb.service has begun starting up.
Apr 28 13:15:09 NAS wsdd2[8270]: cannot read workgroup from testparm
Apr 28 13:15:09 NAS wsdd2[8270]: cannot read workgroup from testparm
Apr 28 13:15:09 NAS wsdd2[8270]: cannot read netbios name from testparm
Apr 28 13:15:09 NAS wsdd2[8270]: cannot read netbios name from testparm
Apr 28 13:15:09 NAS systemd[1]: smb.service: Main process exited, code=exited, status=1/FAILURE
Apr 28 13:15:09 NAS systemd[1]: Failed to start Samba SMB Daemon.
-- Subject: Unit smb.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit smb.service has failed.
--
-- The result is failed.
Apr 28 13:15:09 NAS systemd[1]: smb.service: Unit entered failed state.
Apr 28 13:15:09 NAS systemd[1]: smb.service: Failed with result 'exit-code'.
Apr 28 13:15:09 NAS wsdd2[8270]: Terminated received.
Apr 28 13:15:09 NAS wsdd2[8270]: Terminated received.
Apr 28 13:15:09 NAS systemd[1]: Stopping WSD/LLMNR Discovery/Name Service Daemon...
-- Subject: Unit wsdd2.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Can someone please help me? 
apt-get upgrade isn't recommended.
Though it is brute-force (and not your desire), the fastest path to get it working again might be to backup the data, do a factory reset, reconfigure the NAS, and restore the data from the backup.
Though perhaps mdgm-ntgr or another Netgear mod might have another suggestion to offer.
2 Replies
Replies have been turned off for this discussion
apt-get upgrade isn't recommended.
Though it is brute-force (and not your desire), the fastest path to get it working again might be to backup the data, do a factory reset, reconfigure the NAS, and restore the data from the backup.
Though perhaps mdgm-ntgr or another Netgear mod might have another suggestion to offer.
Downgrades from 6.9.x firmware to pre-6.9.x firmware aren't supported.
You should check for fullness of the 4GB root volume.
The next thing to check would be configuration files e.g. the main services configuration file (/etc/default/services) and samba configuration files. These configurations files are found in the config backup (well the main services configuration is also found in the logs).
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
