Re: Readynas 104 SMB won't activate

ma33axaka · ‎2018-05-19

Been using it for almost 2 years and no problem.

All of suddent I can't enalbe SMB. Did a OS reinstallation, and upgrade to 6.9.4-T8, non of them helped.

I did some research and the only way is to factory reset, but with almost 3TB data stored on my 4 hard drives, I really hate to do that.

Please help me as this is a really common problem and I have no idea why can't I just fix it with simple reset on the settings.

Please let me know if you need any log files

ma33axaka · ‎2018-05-19

I tried so:

apt-get remove samba samba-common smbclient swat samba-doc smbfs libpam-smbpass libsmbclient libsmbclient-dev winbind

This removes all samba-related packages.

Then:

apt-get install samba

Then reboot and:

systemctl status -a smb

give:

root@NAS:~# systemctl status -a smb
● smb.service - Samba SMB Daemon
   Loaded: loaded (/lib/systemd/system/smb.service; enabled; vendor preset: enab
led)
   Active: active (running) since Sat 2018-05-19 16:30:45 MSK; 19min
ago
 Main PID: 2219 (smbd)
   Status: "smbd: ready to serve connections..."
   CGroup: /system.slice/smb.service
           ├─2219 /usr/sbin/smbd --foreground --no-process-group
           ├─2325 /usr/sbin/smbd --foreground --no-process-group
           ├─2326 /usr/sbin/smbd --foreground --no-process-group
           ├─2355 /usr/sbin/smbd --foreground --no-process-group
           └─3723 /usr/sbin/smbd --foreground --no-process-group

May 19 16:30:39 NAS systemd[1]: Starting Samba SMB Daemon...
May 19 16:30:45 NAS systemd[1]: Started Samba SMB Daemon.
May 19 16:30:45 NAS smbd[2219]: [2018/05/19 16:30:45.997388,  0] ../lib/
util/become_daemon.c:124(daemon_ready)
May 19 16:30:46 NAS smbd[2219]:   STATUS=daemon 'smbd' finished starting
 up and ready to s

View solution in original post

Giggos · ‎2018-05-19

I have/had this same exact problem. It started after installing the latest firmware upgrade. I have a temporary fix but it seems to revert itself after a while.

Your problem is most likely caused by the Samba(SMB) service not being able to start. For me this is caused by the fault value for "smb encrypt = (null)" in the /etc/samba/smb.conf file.

What you'll wanna do is enable ssh in your readynas admin page. Then download something like putty and connect to your nas. Login with root and the password you use to login to your admin page. Next open the /etc/samba/smb.conf file with your preferred editor and edit the above value to "smb encrypt = default"

Reboot the nas.

This fixes it for me atleast temporarily.

ma33axaka · ‎2018-05-19

root@NAS:~# /etc/samba/smb.conf
-bash: /etc/samba/smb.conf: Permission denied
root@NAS:~#

How do I open this file?

Giggos · ‎2018-05-19

Use an editor.

Try installing a simple editor like nano

> apt-get install nano

then

> nano /etc/samba/smb.conf

ma33axaka · ‎2018-05-19

 This file is auto-generated.  Do not modify!

[global]
 include = /etc/frontview/samba/smb.conf.defaults
#dashboard: allow trusted domains = 0
 dos charset = CP1252
 hostname lookups = 0
 map to guest = Bad User
#dashboard:map untrusted to domain = no
 oplocks = 1
#dashboard:#dashboard:orgunit =
#dashboard:#dashboard:no_sync_ads = 0
#dashboard:idmap config AOK : backend = rid
#dashboard:idmap config AOK : range = 32768 - 2000000000
#dashboard: password server = *
#dashboard: include system krb5 conf = 0
 realm =
 security = user
 template homedir = /home/%U
 workgroup = AOK
#dashboard:
#dashboard:domain_admin_user =

include = /etc/frontview/samba/smb.conf.%a
include = /etc/frontview/samba/smb.conf.overrides
include = /etc/frontview/samba/Shares.conf
include = /etc/frontview/samba/Shares.conf.%G
include = /etc/frontview/samba/addons/addons.conf
include = /run/usb/samba/Shares.conf

[homes]
 browseable = 0
 writeable = 1
 public = 0
 valid users = %D\%S

Giggos · ‎2018-05-19

What does

> systemctl status -a smb

Give you?

ma33axaka · ‎2018-05-19

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-05-19 15:24:40 MSK; 18min ago
  Process: 4337 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMBDOPTIONS (code=exited, status=1/FAILURE)
 Main PID: 4337 (code=exited, status=1/FAILURE)

May 19 15:24:39 NAS systemd[1]: Starting Samba SMB Daemon...
May 19 15:24:40 NAS systemd[1]: smb.service: Main process exited, code=exited, status=1/FAILURE
May 19 15:24:40 NAS systemd[1]: Failed to start Samba SMB Daemon.
May 19 15:24:40 NAS systemd[1]: smb.service: Unit entered failed state.
May 19 15:24:40 NAS systemd[1]: smb.service: Failed with result 'exit-code'.
root@NAS:~#

StephenB · ‎2018-05-19

Also check the OS partition fullness, as a filling partition can cause a number of quirky issues.

df // -h and df // -i are the two commands. Normally the OS partition has about 70% free space and around 98% free inodes.

ma33axaka · ‎2018-05-19

root@NAS:~# df // -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/md0        3.7G  643M  2.9G  19% /
root@NAS:~# df // -i
Filesystem      Inodes IUsed   IFree IUse% Mounted on
/dev/md0       1048576 14436 1034140    2% /
root@NAS:~#

Giggos · ‎2018-05-19

Let's also check permissions.

>cd /var/lib/samba

>ls -al

ma33axaka · ‎2018-05-19

root@NAS:~# cd /var/lib/samba
root@NAS:/var/lib/samba# ls -al
total 1772
drwxr-xr-x  3 root root   4096 May 19 15:19 .
drwxr-xr-x 26 root root   4096 May 19 15:18 ..
-rw-------  1 root root 421888 May 19 15:19 account_policy.tdb
-rw-------  1 root root 430080 May 19 15:20 group_mapping.tdb
drwxr-xr-x  3 root root   4096 May 19 15:19 private
-rw-------  1 root root 528384 May 19 15:19 registry.tdb
-rw-------  1 root root 421888 May 19 15:19 share_info.tdb
root@NAS:/var/lib/samba# private
-bash: private: command not found
root@NAS:/var/lib/samba# cd private
root@NAS:/var/lib/samba/private# ls -al
total 844
drwxr-xr-x 3 root root   4096 May 19 15:19 .
drwxr-xr-x 3 root root   4096 May 19 15:19 ..
drwx------ 2 root root   4096 May 19 15:23 msg.sock
-rw------- 1 root root 421888 May 19 15:19 passdb.tdb
-rw------- 1 root root 430080 May 19 15:19 secrets.tdb
root@NAS:/var/lib/samba/private#

ma33axaka · ‎2018-05-19

Purge & reinstall samba do not given the effect

ma33axaka · ‎2018-05-19

I tried so:

apt-get remove samba samba-common smbclient swat samba-doc smbfs libpam-smbpass libsmbclient libsmbclient-dev winbind

This removes all samba-related packages.

Then:

apt-get install samba

Then reboot and:

systemctl status -a smb

give:

root@NAS:~# systemctl status -a smb
● smb.service - Samba SMB Daemon
   Loaded: loaded (/lib/systemd/system/smb.service; enabled; vendor preset: enab
led)
   Active: active (running) since Sat 2018-05-19 16:30:45 MSK; 19min
ago
 Main PID: 2219 (smbd)
   Status: "smbd: ready to serve connections..."
   CGroup: /system.slice/smb.service
           ├─2219 /usr/sbin/smbd --foreground --no-process-group
           ├─2325 /usr/sbin/smbd --foreground --no-process-group
           ├─2326 /usr/sbin/smbd --foreground --no-process-group
           ├─2355 /usr/sbin/smbd --foreground --no-process-group
           └─3723 /usr/sbin/smbd --foreground --no-process-group

May 19 16:30:39 NAS systemd[1]: Starting Samba SMB Daemon...
May 19 16:30:45 NAS systemd[1]: Started Samba SMB Daemon.
May 19 16:30:45 NAS smbd[2219]: [2018/05/19 16:30:45.997388,  0] ../lib/
util/become_daemon.c:124(daemon_ready)
May 19 16:30:46 NAS smbd[2219]:   STATUS=daemon 'smbd' finished starting
 up and ready to s