NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
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?
Balance failed to start for volume data
This morning, my email notification reported the following error: "Volume: Balance failed to start for volume data." I searched for this message on the community forum, and the documentation, but no reference to this specific message. What does it mean? What action is required. Here's the last three days of log info:Admin Page offline - Error rndb_import() / dba import failed
Our ReadyNAS 3138 is not loading the Admin Page. The Readynasd is down, anything else incl. Apache is working. If I want to restart the daemon it logs the following infos: root@raid1:~# /usr/sbin/readynasd -v 5 -t -l /root/readynasd.log root@raid1:~# cat /root/readynasd.log [17/02/01 08:00:00] 9796:9796 readynasd.c:1016 () readynasd log started [17/02/01 08:00:00] 9796:9796 context.c:177 (debug) NEW GLOBAL_CONTEXT: db.sq3=0x1584ec8 [17/02/01 08:00:00] 9796:9796 context.c:213 (debug) NEW GLOBAL_CONTEXT: event.sq3=0x15ab8e8 [17/02/01 08:00:00] 9796:9796 context.c:216 (debug) NEW GLOBAL_CONTEXT: globalctx=0x1584600 [17/02/01 08:00:00] 9796:9796 readynasd.c:1206 () readynasd started. (restarted=0) [17/02/01 08:00:00] 9796:9796 db_access.c:122 (error) Error rndb_import() ==> rc=1 [17/02/01 08:00:00] 9796:9796 readynasd.c:1261 (error) dba import failed Was working without any issues over the last month, currently tried to switch from DOMAIN to AD but wasn't working and we continued to use the NT-Domain.
