NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

MukeshCS's avatar
MukeshCS
Tutor
Feb 06, 2021

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, ...
MukeshCS's avatar
MukeshCS
Tutor
Feb 06, 2021

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/snapshot

 

Root 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 Update

 

There 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.

 

 

StephenB's avatar
StephenB
Guru - Experienced User
Feb 06, 2021
MukeshCS wrote:

 

Root directory is 49% full. How can I free it up?

 

What apps do you have installed?

 

MukeshCS wrote:

 

● smb.service loaded failed failed Samba SMB Daemon

 

Can you try restarting it from ssh - that might give you more information on what's going on.

  • MukeshCS's avatar
    MukeshCS
    Tutor
    Feb 06, 2021

    Thanks again StephenB 

    As I said earlier, there are no apps installed except "SMB Plus".

    In the past I had Plex, VPN and few other apps installe,d but had uninstalled them long time back.

    Restarting the service doesn't give any more details, as the service is already stopped. Anyways tried restarting it and this is what I get:

     

    systemctl restart smb.service
    Job for smb.service failed because the control process exited with error code.
    See "systemctl status smb.service" and "journalctl -xe" for details.

     

    systemctl status smb.service
    ● smb.service - Samba SMB Daemon
    Loaded: loaded (/lib/systemd/system/smb.service; enabled; vendor preset: enabled)
    Active: failed (Result: exit-code) since Sun 2021-02-07 10:35:33 AEDT; 2min 10s ago
    Process: 8038 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMBDOPTIONS (code=exited, status=1/FAILURE)
    Main PID: 8038 (code=exited, status=1/FAILURE)

    Feb 07 10:35:32 MukeshNAS systemd[1]: Starting Samba SMB Daemon...
    Feb 07 10:35:33 MukeshNAS systemd[1]: smb.service: Main process exited, code=exited, status=1/FAILURE
    Feb 07 10:35:33 MukeshNAS systemd[1]: Failed to start Samba SMB Daemon.
    Feb 07 10:35:33 MukeshNAS systemd[1]: smb.service: Unit entered failed state.
    Feb 07 10:35:33 MukeshNAS systemd[1]: smb.service: Failed with result 'exit-code'.

     

    journalctl -xe
    -- Logs begin at Thu 2021-01-28 11:29:14 AEDT, end at Sun 2021-02-07 10:37:58 AEDT. --
    Feb 07 08:40:15 MukeshNAS ng-csd[3570]: Faild to get changes. Error #18
    Feb 07 08:40:15 MukeshNAS ng-csd[3570]: Failed to downsync changes. Error #18
    Feb 07 08:40:45 MukeshNAS ng-csd[3570]: Encountered OneDriveError: resyncRequired
    Feb 07 08:40:45 MukeshNAS ng-csd[3570]: Faild to get changes. Error #18
    Feb 07 08:40:45 MukeshNAS ng-csd[3570]: Failed to downsync changes. Error #18
    Feb 07 08:41:16 MukeshNAS ng-csd[3570]: Encountered OneDriveError: resyncRequired
    Feb 07 08:41:16 MukeshNAS ng-csd[3570]: Faild to get changes. Error #18
    Feb 07 08:41:16 MukeshNAS ng-csd[3570]: Failed to downsync changes. Error #18
    Feb 07 08:41:46 MukeshNAS ng-csd[3570]: Encountered OneDriveError: resyncRequired
    Feb 07 08:41:46 MukeshNAS ng-csd[3570]: Faild to get changes. Error #18
    Feb 07 08:41:46 MukeshNAS ng-csd[3570]: Failed to downsync changes. Error #18
    Feb 07 08:42:16 MukeshNAS ng-csd[3570]: Encountered OneDriveError: resyncRequired
    Feb 07 08:42:16 MukeshNAS ng-csd[3570]: Faild to get changes. Error #18
    Feb 07 08:42:16 MukeshNAS ng-csd[3570]: Failed to downsync changes. Error #18
    Feb 07 08:42:47 MukeshNAS ng-csd[3570]: Encountered OneDriveError: resyncRequired
    Feb 07 08:42:47 MukeshNAS ng-csd[3570]: Faild to get changes. Error #18
    Feb 07 08:42:47 MukeshNAS ng-csd[3570]: Failed to downsync changes. Error #18
    Feb 07 08:43:00 MukeshNAS dbus[2687]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
    Feb 07 08:43:00 MukeshNAS dbus[2687]: [system] Successfully activated service 'org.opensuse.Snapper'
    Feb 07 08:43:00 MukeshNAS org.opensuse.Snapper[2687]: :1: parser error : Document is empty
    Feb 07 08:43:00 MukeshNAS org.opensuse.Snapper[2687]: ^
    Feb 07 08:43:00 MukeshNAS snapperd[32163]: loading 522 failed
    Feb 07 08:43:00 MukeshNAS org.opensuse.Snapper[2687]: :1: parser error : Document is empty
    Feb 07 08:43:00 MukeshNAS org.opensuse.Snapper[2687]: ^
    Feb 07 08:43:00 MukeshNAS snapperd[32163]: loading 522 failed
    Feb 07 08:43:00 MukeshNAS org.opensuse.Snapper[2687]: :1: parser error : Document is empty
    Feb 07 08:43:00 MukeshNAS org.opensuse.Snapper[2687]: ^
    Feb 07 08:43:00 MukeshNAS snapperd[32163]: loading 507 failed
    Feb 07 08:43:00 MukeshNAS org.opensuse.Snapper[2687]: :1: parser error : Document is empty
    Feb 07 08:43:00 MukeshNAS org.opensuse.Snapper[2687]: ^
    Feb 07 08:43:00 MukeshNAS snapperd[32163]: loading 518 failed
    Feb 07 08:43:00 MukeshNAS org.opensuse.Snapper[2687]: :1: parser error : Document is empty
    Feb 07 08:43:00 MukeshNAS org.opensuse.Snapper[2687]: ^
    Feb 07 08:43:00 MukeshNAS snapperd[32163]: loading 501 failed
    Feb 07 08:43:00 MukeshNAS org.opensuse.Snapper[2687]: :1: parser error : Document is empty
    Feb 07 08:43:00 MukeshNAS org.opensuse.Snapper[2687]: ^
    Feb 07 08:43:00 MukeshNAS snapperd[32163]: loading 499 failed
    Feb 07 08:43:00 MukeshNAS org.opensuse.Snapper[2687]: :1: parser error : Document is empty
    Feb 07 08:43:00 MukeshNAS org.opensuse.Snapper[2687]: ^
    Feb 07 08:43:00 MukeshNAS snapperd[32163]: loading 480 failed
    Feb 07 08:43:01 MukeshNAS org.opensuse.Snapper[2687]: :1: parser error : Document is empty
    Feb 07 08:43:01 MukeshNAS org.opensuse.Snapper[2687]: ^
    Feb 07 08:43:01 MukeshNAS snapperd[32163]: loading 506 failed
    Feb 07 08:43:01 MukeshNAS org.opensuse.Snapper[2687]: :1: parser error : Document is empty
    Feb 07 08:43:01 MukeshNAS org.opensuse.Snapper[2687]: ^
    Feb 07 08:43:01 MukeshNAS snapperd[32163]: loading 417 failed
    Feb 07 08:43:01 MukeshNAS org.opensuse.Snapper[2687]: :1: parser error : Document is empty
    Feb 07 08:43:01 MukeshNAS org.opensuse.Snapper[2687]: ^
    Feb 07 08:43:01 MukeshNAS snapperd[32163]: loading 373 failed
    Feb 07 08:43:01 MukeshNAS org.opensuse.Snapper[2687]: :1: parser error : Document is empty
    Feb 07 08:43:01 MukeshNAS org.opensuse.Snapper[2687]: ^
    Feb 07 08:43:01 MukeshNAS snapperd[32163]: loading 324 failed
    Feb 07 08:43:01 MukeshNAS org.opensuse.Snapper[2687]: :1: parser error : Document is empty
    Feb 07 08:43:01 MukeshNAS org.opensuse.Snapper[2687]: ^
    Feb 07 08:43:01 MukeshNAS snapperd[32163]: loading 311 failed
    Feb 07 08:43:01 MukeshNAS org.opensuse.Snapper[2687]: :1: parser error : Document is empty
    Feb 07 08:43:01 MukeshNAS org.opensuse.Snapper[2687]: ^
    Feb 07 08:43:01 MukeshNAS snapperd[32163]: loading 522 failed
    Feb 07 08:43:01 MukeshNAS org.opensuse.Snapper[2687]: :1: parser error : Document is empty
    Feb 07 08:43:01 MukeshNAS org.opensuse.Snapper[2687]: ^
    Feb 07 08:43:01 MukeshNAS snapperd[32163]: loading 281 failed
    Feb 07 08:43:01 MukeshNAS org.opensuse.Snapper[2687]: :1: parser error : Document is empty

    • StephenB's avatar
      StephenB
      Guru - Experienced User
      Feb 06, 2021
      MukeshCS wrote:

       

      In the past I had Plex, VPN and few other apps installe,d but had uninstalled them long time back.

      It could be something left behind by one of those - plex can leave behind transcoding files in the OS partition.  To rule that out you can try this:

      # mount --bind / /mnt
# cd /mnt
# find . -name chunk*.m4s

      If you find this, just remove them.

       

      Undo the mount when done with 

      # umount /mnt

       

      But 49% isn't full enough to corrupt the configuration files.  Do you have a back up of the data?

      • MukeshCS's avatar
        MukeshCS
        Tutor
        Feb 06, 2021

        I followed the suggestion to look for left over files from Plex, there isn't anything:


        root@MukeshNAS:~# mount --bind / /mnt
        root@MukeshNAS:~# cd /mnt
        root@MukeshNAS:/mnt# find . -name chunk*.m4s
        root@MukeshNAS:/mnt#

    • MukeshCS's avatar
      MukeshCS
      Tutor
      Feb 06, 2021

      Searching for the error message: "Failed to start Samba SMB Daemon" I also reinstalled samba following this article: Solved: Re: Readynas 104 SMB won't activate - NETGEAR Communities

      Rebooted the NAS, still the service failed to start:

       

      systemctl start smb.service
      Job for smb.service failed because the control process exited with error code.
      See "systemctl status smb.service" and "journalctl -xe" for details.
      root@MukeshNAS:~# 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 Sun 2021-02-07 10:49:32 AEDT; 6s ago
      Docs: man:smbd(8)
      man:samba(7)
      man:smb.conf(5)
      Process: 7555 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMBDOPTIONS (code=exited, status=1/FAILURE)
      Main PID: 7555 (code=exited, status=1/FAILURE)

      Feb 07 10:49:29 MukeshNAS systemd[1]: Starting Samba SMB Daemon...
      Feb 07 10:49:32 MukeshNAS systemd[1]: smb.service: Main process exited, code=exited, status=1/FAILURE
      Feb 07 10:49:32 MukeshNAS systemd[1]: Failed to start Samba SMB Daemon.
      Feb 07 10:49:32 MukeshNAS systemd[1]: smb.service: Unit entered failed state.
      Feb 07 10:49:32 MukeshNAS systemd[1]: smb.service: Failed with result 'exit-code'.

NETGEAR Academy

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

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More