NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Greg_M
Jun 14, 2017Aspirant
SMB Button Disabled - OS 6.7.4
Hi everyone. Am having a bit of trouble with my ReadNAS 104 (OS 6.7.4) and SMB which now fails to activate. About 2 days ago, everything was working perfectly. Had SMB running which all devi...
- Jun 21, 2017
Might be time to use the nuclear option (factory reset and restore the NAS from backup).
Greg_M
Jun 17, 2017Aspirant
Tried that with no luck.
I've PM to you updated logs.
I've PM to you updated logs.
Greg_M
Jun 19, 2017Aspirant
After upgrading to RC 6.7.5, I am still having the same issues with SMB not activating.
Was wondering if it might be worth downgrading the firmware to 6.7.3 or 6.7.1?
Greg
- mdgm-ntgrJun 19, 2017NETGEAR Employee Retired
Your logs show some OOMing.
Please make sure quotas are disabled on the volume. Also try disabling unneeded services.- Greg_MJun 21, 2017Aspirant
You'll have to forgive me as I am not very technically proficient with this.
OOMing? I have googled it and whilst it gives a very basic explanation, not sure what would be causing this.
To recap what I have done so far: :
- updated the os to 6.7.5;
- disabled all quotas (were never loaded to begin with);
- uninstalled all apps and stopped anti-virus;
- closed down all the services I could;
- removed all account permissions and re-loaded them;
- disabled cloud access;
- confirmed no backup services running (never was setup);
and still cannot activate SMB. Sometimes, the green light will illuminate but then disappear a few seconds later.
Not sure if this is relevant but I was reviewing some of the entries in the log files and found this buried in the 'systemd-journal' file.
Jun 21 11:58:01 NAS2 systemd[1]: Starting Samba NMB Daemon...
Jun 21 11:58:01 NAS2 wsdd2[9489]: starting.
Jun 21 11:58:01 NAS2 cron[2052]: (*system*poweroff) WRONG FILE OWNER (/etc/cron.d/poweroff)
Jun 21 11:58:01 NAS2 cron[2052]: (*system*php5) WRONG FILE OWNER (/etc/cron.d/php5)
Jun 21 11:58:03 NAS2 forked-daapd[9335]: [ LOG] scan: Scanned 3000 files...
Jun 21 11:58:03 NAS2 systemd[1]: nmb.service: Control process exited, code=exited status=1
Jun 21 11:58:03 NAS2 systemd[1]: Failed to start Samba NMB Daemon.
Jun 21 11:58:03 NAS2 systemd[1]: nmb.service: Unit entered failed state.
Jun 21 11:58:03 NAS2 systemd[1]: nmb.service: Failed with result 'exit-code'.
Jun 21 11:58:05 NAS2 systemd[1]: smb.service: Main process exited, code=exited, status=1/FAILURE
Jun 21 11:58:05 NAS2 systemd[1]: Failed to start Samba SMB Daemon.
Jun 21 11:58:05 NAS2 systemd[1]: smb.service: Unit entered failed state.
Jun 21 11:58:05 NAS2 systemd[1]: smb.service: Failed with result 'exit-code'.
Jun 21 11:58:05 NAS2 systemd[1]: Stopping WSD/LLMNR Discovery/Name Service Daemon...
Jun 21 11:58:05 NAS2 wsdd2[9489]: Terminated received.
Jun 21 11:58:05 NAS2 wsdd2[9489]: Terminated received.
Jun 21 11:58:05 NAS2 wsdd2[9489]: terminating.
Jun 21 11:58:05 NAS2 systemd[1]: Stopped WSD/LLMNR Discovery/Name Service Daemon.Is this related to what I am experiencing?
I have gone through all settings and could not locate anything obvious. However, as mentoned eariler, I am not very confident with this device.
Not sure where to go from here. Do you think a Factory Reset would resolve this? Its the last preference considering the amount of time (and expense) needed to back up everything but I need to get this running again.
Any assistance provided is always greatly appreciated.
Thank you
Greg
- StephenBJun 21, 2017Guru - Experienced User
Greg_M wrote:
- disabled all quotas (were never loaded to begin with);
Also, the volume itself might have quotas enabled. Click on the settings wheel next to the volume (on the volume tab), and then choose "settings".
If quotas are enabled there, turn them off.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!