NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
MukeshCS
Feb 06, 2021Tutor
SMB service not starting on ReadyNAS 314
Hello Team,
I have a ReadyNAS 314, which has been working fine for last few years.
Current Firmware: 6.10.4
Suddnely, I am unable to start the SMB service on it.
Based on some other discussions, tried downgrading and upgrading the firmware, but no help.
I am not an expert with Linux, but have been able to connect to the system via SSH.
An attempt to start the smb service fails with this message:
systemctl start smb.service
Failed to start smb.service: The name org.freedesktop.PolicyKit1 was not provided by any .service files
See system logs and 'systemctl status smb.service' for details.
When searched on the error "The name org.freedesktop.PolicyKit1 was not provided by any .service files" found that it might be due to the fact that I haven't used sudo command before starting the service. sudo command is not accepted by the ssh session for some reason.
I referred to the discussion: OS6.2.2 - Service SMB suddenly stopped working, wo... - NETGEAR Communities but could not find a way to look into the smbd.log file
I will appreciate any suggestions to solve the problem.
14 Replies
Replies have been turned off for this discussion
- StephenBGuru - Experienced User
You are supposed to log in with ssh using root as the username (and using the NAS admin password). If you did that, then there's no need for sudo.
Did you check for a full OS partition? (or see any errors in the web ui saying that root is full)?
What apps do you have installed?
MukeshCS wrote:
but could not find a way to look into the smbd.log file
Download the log zip file from the logs tab of the web ui. It's in there (along with a lot of other logs that might have clues on what is going on).
For instance, if you look in volume.log, you can scroll down to the df - h section:
=== df -h === Filesystem Size Used Avail Use% Mounted on udev 10M 4.0K 10M 1% /dev /dev/md0 4.0G 650M 3.0G 18% /
.../dev/md0 is the OS partition - you can see in the above snippet that the OS partition on this NAS is 18% full. Normally it is ~20% or so. If it gets full for some reason, the configuration files in the NAS can get corrupted - which is a common cause for your particular problem.
- MukeshCSTutor
Thank you very much StephenB for the guidance.
I am logged in with the root user now, and still unable to start the service.
Output of the df -h command is this:
df -h
Filesystem Size Used Avail Use% Mounted on
udev 10M 4.0K 10M 1% /dev
/dev/md0 4.0G 1.8G 1.9G 49% /
tmpfs 993M 4.0K 993M 1% /dev/shm
tmpfs 993M 13M 980M 2% /run
tmpfs 497M 4.0K 497M 1% /run/lock
tmpfs 993M 0 993M 0% /sys/fs/cgroup
/dev/md127 3.7T 2.2T 1.6T 58% /data
/dev/md127 3.7T 2.2T 1.6T 58% /home
/dev/md127 3.7T 2.2T 1.6T 58% /apps
/dev/md127 3.7T 2.2T 1.6T 58% /vault
/dev/md127 3.7T 2.2T 1.6T 58% /var/ftp/Folder1
/dev/md127 3.7T 2.2T 1.6T 58% /run/nfs4/data/Folder2
/dev/md127 3.7T 2.2T 1.6T 58% /run/nfs4/data/Folder3
/dev/md127 3.7T 2.2T 1.6T 58% /run/nfs4/data/Folder4
/dev/md127 3.7T 2.2T 1.6T 58% /run/nfs4/data/Folder5
tmpfs 4.0K 0 4.0K 0% /data/Folder6
tmpfs 4.0K 0 4.0K 0% /home/admin/snapshot
tmpfs 4.0K 0 4.0K 0% /home/Folder7/snapshot
tmpfs 4.0K 0 4.0K 0% /home/Folder8/snapshotRoot directory is 49% full. How can I free it up?
Looking into the logs directory, I also found systemctl-status.log file and it shows failure for the following services:
● smb.service loaded failed failed Samba SMB Daemon
● radar.service loaded failed failed Radar Update
● auto-fw-reminder.service loaded failed failed ReadyNAS Firmware Update Reminder
● auto-fw-update.service loaded failed failed ReadyNAS Firmware UpdateThere are no apps installed, except SMB Plus. app-install.log shows "-- No entries --"
Looked in the web ui logs, there are no errors complaining about the OS drive being full
Looking forward to the suggestions. Please do let me know, if you would like to see any other logs, I am happy to share them.
- StephenBGuru - Experienced User
- hogeInitiate
Hello,
I faced same issue on 6.10.4.
The issue resolved by downgrading to 6.10.2.
When downgrading,I can easily start SMB service.
So I might think 6.10.4 has a severe bug.
If you've worried about the issue,try it!
Related Content
NETGEAR Academy

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