NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
6.9.3
3 TopicsCant 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?Solved2KViews0likes2CommentsCannot access admin page
Updated several RNAS 312's with firmware 6.9.3. -Also updated a 212 with 6.9.3. After the update, RAIDar application 6.3.0 can no longer access the 312's on the internal network through login. Can access the shares via "browse" and thru ReadyCloud....but not thru local or Cloud admin page login. Did not affect the RNAS 212. Ideas? Suggestions on restoring local login with RAIDar app?7.2KViews0likes20CommentsWhen shutting down or upgrading firmware my RN214 will not sutdown all the way. I get a do_exit+9ec
When trying to shutdown my ReadyNAS 214 it hangs with an error of do_exit+9ec on display. The only way to recover is to disconnect the AC power cord and reconnect. I have the most current version of firmware Version 6.9.3. Same error occurs regardless of how it is done. Occurs when shutting down from the power button or from the system device webpage. Any suggestions? Had a similar problem when I first purchased this unit and during upgrades and shut downs. The NIC lights do not light up when this problem occurs. I am directly connected to 1gb router. The network settings on the RN214 was set to DHCP with the GB Router reserving a specific IP for the RN214 prior to the firmware upgrade - system was working, had network connection. Before upgrading to 6.9.3 I changed the Network on the RN214 to Static. After the firmware ugrade and rebooting I got the do_exit+9ec error. I did this thinking the dhcp option was causing a problem. Any help to get me back on line would be greatly appreciated. Please advise. Thank you.2.5KViews0likes12Comments