Can't turn on SMB

[bubu]

Hi

I have RND516 with 6.10.8 firmware.

Since today I had issue with my MAC and TimeMachine through AFP on RND.

I tried trough SMB but since SMB start and stop.

Impossible now to turn on SMB in NAS services setup.

I uninstalled SMB plus it is the same

Somebody can help me?

because I can't acces now to my RND with finder 😞

Laurent

[StephenB · Accepted solution]

---

@bubu wrote:

It did it right away and also manual reboot

same issue after reboot

---

Ok.  Then the script didn't run.  I think the issue is that the certificate has expired.

Try these commands instead

cd //
wget --no-check-certificate https://gitlab.codycook.us/readynas-scripts/share_lun_ui_fix.sh/raw/master/share_lun_ui_fix.sh
chmod +x ./share_lun_ui_fix.sh
./share_lun_ui_fix.sh

[StephenB]

---

@bubu wrote:

Impossible now to turn on SMB in NAS services setup.

---

Are you getting an error when you try?

FWIW, I am not yet running 10.6.8 on my x86 NAS, but I am able to enable/disable SMB on an RN102.

[bubu]

No error message
I turn it on but it turn off automatically after few seconds

[StephenB]

---

@bubu wrote:
No error message
I turn it on but it turn off automatically after few seconds

---

Have you tried downloading the log zip file and looking for errors in there?

[bubu]

Which log because there are a lot :

• in system.log

Oct 03 07:17:01 serveur CRON[16951]: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 03 07:17:01 serveur CRON[16952]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Oct 03 07:17:01 serveur CRON[16951]: pam_unix(cron:session): session closed for user root
Oct 03 07:22:21 serveur clamd[10097]: SelfCheck: Database status OK.
Oct 03 07:23:59 serveur ng-csd[6721]: Failed to parse Amazon error response. body: {"message":"Token has expired"}
Oct 03 07:31:30 serveur connmand[3500]: ntp: adjust (slew): -0.000126 sec
Oct 03 07:32:21 serveur clamd[10097]: SelfCheck: Database status OK.
Oct 03 07:39:01 serveur CRON[17142]: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 03 07:39:01 serveur CRON[17143]: (root) CMD (  [ -x /usr/lib/php5/sessionclean ] && /usr/lib/php5/sessionclean)
Oct 03 07:39:01 serveur CRON[17142]: pam_unix(cron:session): session closed for user root
Oct 03 07:42:21 serveur clamd[10097]: SelfCheck: Database status OK.
Oct 03 07:48:34 serveur connmand[3500]: ntp: adjust (slew): +0.001058 sec
Oct 03 07:52:21 serveur clamd[10097]: SelfCheck: Database status OK.
Oct 03 08:02:21 serveur clamd[10097]: SelfCheck: Database status OK.
Oct 03 08:05:38 serveur connmand[3500]: ntp: adjust (slew): -0.051464 sec
Oct 03 08:09:01 serveur CRON[17416]: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 03 08:09:01 serveur CRON[17417]: (root) CMD (  [ -x /usr/lib/php5/sessionclean ] && /usr/lib/php5/sessionclean)
Oct 03 08:09:01 serveur CRON[17416]: pam_unix(cron:session): session closed for user root
Oct 03 08:12:21 serveur clamd[10097]: SelfCheck: Database status OK.
Oct 03 08:17:01 serveur CRON[17529]: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 03 08:17:01 serveur CRON[17530]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Oct 03 08:17:01 serveur CRON[17529]: pam_unix(cron:session): session closed for user root
Oct 03 08:22:21 serveur clamd[10097]: SelfCheck: Database status OK.
Oct 03 08:22:43 serveur connmand[3500]: ntp: adjust (slew): +0.065669 sec
Oct 03 08:24:15 serveur ng-csd[6721]: Failed to parse Amazon error response. body: {"message":"Token has expired"}
Oct 03 08:32:21 serveur clamd[10097]: SelfCheck: Database status OK.
Oct 03 08:35:46 serveur apache_access[4708]: 192.168.111.112 "GET / HTTP/1.1" 302
Oct 03 08:35:46 serveur apache_access[4708]: 192.168.111.112 "GET /admin HTTP/1.1" 401
Oct 03 08:35:52 serveur apache_access[4708]: Admin session started from 192.168.111.112
Oct 03 08:36:12 serveur apache_access[4708]: 192.168.111.112 "GET /ispdb.xml?_dc=1664778972036 HTTP/1.1" 200
Oct 03 08:36:18 serveur wsdd2[17976]: starting.
Oct 03 08:36:19 serveur wsdd2[17976]: cannot read workgroup from testparm
Oct 03 08:36:19 serveur wsdd2[17976]: cannot read netbios name from testparm
Oct 03 08:36:19 serveur wsdd2[17976]: Terminated received.
Oct 03 08:36:19 serveur wsdd2[17976]: terminating.
Oct 03 08:36:39 serveur apache_access[4709]: Suppressed 4 duplicate messages
Oct 03 08:36:39 serveur apache_access[4709]: ::1 "OPTIONS * HTTP/1.0" 200
Oct 03 08:38:20 serveur apache_access[4708]: 192.168.111.112 "POST /dbbroker HTTP/1.1" 401
Oct 03 08:38:55 serveur dbus[3362]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Oct 03 08:38:55 serveur dbus[3362]: [system] Successfully activated service 'org.opensuse.Snapper'
Oct 03 08:38:55 serveur snapperd[18114]: loading 3958 failed
Oct 03 08:38:55 serveur snapperd[18114]: loading 4043 failed
Oct 03 08:38:55 serveur snapperd[18114]: loading 4057 failed
Oct 03 08:38:55 serveur snapperd[18114]: loading 3950 failed
Oct 03 08:38:55 serveur snapperd[18114]: loading 4035 failed
Oct 03 08:38:55 serveur snapperd[18114]: loading 4049 failed
Oct 03 08:38:55 serveur snapperd[18114]: loading 3950 failed
Oct 03 08:38:55 serveur snapperd[18114]: loading 4035 failed
Oct 03 08:38:55 serveur snapperd[18114]: loading 4049 failed
Oct 03 08:38:55 serveur snapperd[18114]: loading 3950 failed
Oct 03 08:38:55 serveur snapperd[18114]: loading 4035 failed
Oct 03 08:38:55 serveur snapperd[18114]: loading 4049 failed
Oct 03 08:38:55 serveur snapperd[18114]: loading 3950 failed
Oct 03 08:38:55 serveur snapperd[18114]: loading 4035 failed
Oct 03 08:38:55 serveur snapperd[18114]: loading 4049 failed

•  in smbstatus.log

using configfile = /etc/samba/smb.conf

• in status.log

[22/10/03 00:00:22 CEST] info:snapshot:LOGMSG_SNAPSHOT_CREATE_INFO Snapshot c_1664748020 was successfully created for share or LUN AmazonCloudDrive.
[22/10/03 00:00:23 CEST] info:snapshot:LOGMSG_SNAPSHOT_CREATE_INFO Snapshot c_1664748020 was successfully created for share or LUN AmazonPhotos.
[22/10/03 00:00:25 CEST] info:snapshot:LOGMSG_SNAPSHOT_CREATE_INFO Snapshot c_1664748020 was successfully created for share or LUN Immersion.
[22/10/03 00:00:26 CEST] info:snapshot:LOGMSG_SNAPSHOT_CREATE_INFO Snapshot c_1664748020 was successfully created for share or LUN Photos.
[22/10/03 00:00:27 CEST] info:snapshot:LOGMSG_SNAPSHOT_CREATE_INFO Snapshot c_1664748020 was successfully created for share or LUN Prive.
[22/10/03 00:00:28 CEST] info:snapshot:LOGMSG_SNAPSHOT_CREATE_INFO Snapshot c_1664748020 was successfully created for share or LUN Prophecy.
[22/10/03 00:00:29 CEST] info:snapshot:LOGMSG_SNAPSHOT_CREATE_INFO Snapshot c_1664748020 was successfully created for share or LUN Prophezine.
[22/10/03 00:05:21 CEST] notice:backup:LOGMSG_SUCCESS_BACKUP Successfully completed backup job Immersion.
[22/10/03 00:05:40 CEST] notice:backup:LOGMSG_SUCCESS_BACKUP Successfully completed backup job Prophecy.
[22/10/03 00:06:40 CEST] notice:backup:LOGMSG_SUCCESS_BACKUP Successfully completed backup job Prive.
[22/10/03 00:06:54 CEST] notice:backup:LOGMSG_SUCCESS_BACKUP Successfully completed backup job Prophezine.
[22/10/03 00:14:36 CEST] notice:backup:LOGMSG_SUCCESS_BACKUP Successfully completed backup job NAS.
[22/10/03 00:21:28 CEST] notice:backup:LOGMSG_SUCCESS_BACKUP Successfully completed backup job Photos.
[22/10/03 02:20:37 CEST] notice:volume:LOGMSG_DISKTEST_COMPLETED_VOLUME Disk test completed for volume data.
[22/10/03 08:36:18 CEST] info:system:LOGMSG_PROTOCOL_ENABLED Service protocol SMB is enabled.

but still SMB button not green and can't see NAS in network only access by http

[StephenB]

---

@bubu wrote:

Which log because there are a lot :

---

Normally I'd look in kernel.log, system.log, and systemd-journal.log, and see if there are any SMB related errors or crashes.  dmesg.log also sometimes has useful information.

You are showing some other errors (likely unrelated) with snapshots that might need to be sorted out at some point.

Did this problem happen as soon as you upgraded to 6.10.8?

Have you tried an OS reinstall?

[bubu]

How can reinstall it ?

Any issue for my data? because I can't loose them.

[StephenB]

Are you seeing any warnings about a full root partition in the NAS web ui?  If you are, then don't try the OS reinstall.

---

@bubu wrote:

How can reinstall it ?

---

The process for doing an OS reinstall from the boot menu is described on pages 120-121 here:

• https://www.downloads.netgear.com/files/GDC/READYNAS-100/ReadyNAS_%20OS6_Desktop_HM_EN.pdf

I don't know that it will fix it, but your NAS is behaving oddly, so it might.

---

@bubu wrote:

Any issue for my data? because I can't loose them.

---

It shouldn't affect data.  It will

• reset the admin password to password
• reset the network configuration to use dhcp with no bonding
• disable volume quota (which can be re-enabled on the volume settings wheel).

But there is something going on with the data volume as well (snapshots that cannot be found or maybe accessed).

It sounds like you have no backup for the NAS - something you should put in place when you get past that.

[bubu]

Thank you

I have external USB backup but it take very long time to restore 😛

[bubu]

Very bad new 😞

- restore done

- but still can't enable SMB

- and my DATA seems to be always on HDD but NAS can't see them 😞

[StephenB]

---

@bubu wrote:

- and my DATA seems to be always on HDD but NAS can't see them 😞

---

Are the shares showing up on the shares page?  Can you browse a share, and see the data?

[bubu]

Can't see any of my folder in data

but it seems datas are still there because at the bottom only 4.8To free

[StephenB]

---

@bubu wrote:

Can't see any of my folder in data

but it seems datas are still there because at the bottom only 4.8To free

---

Was all your data in the home folders?  Or did you create shares?

Have you ever used the linux command line (ssh)?

[bubu]

there were shared folder not in home folder

I wasn't using since long time ssh but I can.

[StephenB]

---

@bubu wrote:

there were shared folder not in home folder

I wasn't using since long time ssh but I can.

---

Ok.  Enable ssh in the web ui (system->settings->services).  Then connect with ssh (terminal will work), and log in as root, using the NAS admin password.

Then take a look at the data volume (ls /data) and see if you see the shared folder(s).

While you are logged in, you could also take a look at the SMB service status with systemctl status smb

If the service isn't running, you could also try systemctl start smb and see what happens.

[bubu]

Please see bellow details :

Spoiler

root@serveur:~# ls /data
AmazonCloudDrive AmazonPhotos home Immersion Musique NAS Photos Prive Prophecy Prophezine Vidéos
root@serveur:~# systemctl status smb
● smb.service - Samba SMB Daemon
Loaded: loaded (/lib/systemd/system/smb.service; disabled; vendor preset: enabled)
Active: inactive (dead) since Tue 2022-10-04 21:37:19 CEST; 18min ago
Process: 23558 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMBDOPTIONS (code=exited, status=1/FAILURE)
Main PID: 23558 (code=exited, status=1/FAILURE)

Oct 04 21:37:18 serveur systemd[1]: Starting Samba SMB Daemon...
Oct 04 21:37:19 serveur systemd[1]: smb.service: Main process exited, code=exited, status=1/FAILURE
Oct 04 21:37:19 serveur systemd[1]: Failed to start Samba SMB Daemon.
Oct 04 21:37:19 serveur systemd[1]: smb.service: Unit entered failed state.
Oct 04 21:37:19 serveur systemd[1]: smb.service: Failed with result 'exit-code'.
root@serveur:~# 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.
root@serveur:~# systemctl status smb.service
● smb.service - Samba SMB Daemon
Loaded: loaded (/lib/systemd/system/smb.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2022-10-04 21:56:15 CEST; 21s ago
Process: 25609 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMBDOPTIONS (code=exited, status=1/FAILURE)
Main PID: 25609 (code=exited, status=1/FAILURE)

Oct 04 21:56:15 serveur systemd[1]: Starting Samba SMB Daemon...
Oct 04 21:56:15 serveur systemd[1]: smb.service: Main process exited, code=exited, status=1/FAILURE
Oct 04 21:56:15 serveur systemd[1]: Failed to start Samba SMB Daemon.
Oct 04 21:56:15 serveur systemd[1]: smb.service: Unit entered failed state.
Oct 04 21:56:15 serveur systemd[1]: smb.service: Failed with result 'exit-code'.

• all my folders still there, but can't see them in http admin page of RND
• for SMB still error also in SSH

[StephenB]

---

@bubu wrote:

• all my folders still there, but can't see them in http admin page of RND
• for SMB still error also in SSH

---

Can you run these commands?

• df // -h
• btrfs fi df //

[bubu]

root@serveur:~# df // -h
Filesystem Size Used Avail Use% Mounted on
/dev/md0 4.0G 2.0G 1.8G 54% /
root@serveur:~# btrfs fi df //
Data, single: total=2.85GiB, used=1.88GiB
System, DUP: total=8.00MiB, used=16.00KiB
Metadata, DUP: total=204.56MiB, used=23.12MiB
GlobalReserve, single: total=16.00MiB, used=0.00B
root@serveur:~#

[StephenB]

One option is to do a factory reset, set up the NAS again, and restore the data from backup.

There is a repair tool that might possibly help.  But I think you would need a backup anyway, because I think there is some risk that the tool could do more damage.

Any thoughts?

[bubu]

I can't do reset factory on other disk? and after replace good HDD inside.

Is it the only solution?

[StephenB]

---

@bubu wrote:

I can't do reset factory on other disk?

---

A factory reset just formats the disks and, the firmware onto the disks.  If you it with a different set of disks inserted, then it would have no effect on the disks you have in the NAS now.

The repair tool might well work (and I haven't seen cases where it has done harm) - but I do see some risk to your data.  So I am recommending making a backup first.

You'd run the repair tool from ssh - the command is:

curl -s https://gitlab.codycook.us/readynas-scripts/share_lun_ui_fix.sh/raw/master/share_lun_ui_fix.sh | bash

[bubu]

I can’t do more backup due to share folder not visible in web portal.
I have daily external usb backup and I hope everything is ok on there 😞
I have critical an volume files in RND and I can’t control 1 by 1 each of them 😞
This is a nightmare

[StephenB]

---

@bubu wrote:
I can’t do more backup due to share folder not visible in web portal.
I have daily external usb backup and I hope everything is ok on there 😞
I have critical an volume files in RND and I can’t control 1 by 1 each of them 😞
This is a nightmare

---

Understood.  You could perhaps back up manually to the USB disk (using the cp command from ssh).  Or just check it, and see what is there.

Or just try running the repair tool I linked in above.  Best to copy/paste the command, as it is long.

[bubu]

Thank you

I will try this evening

[bubu]

I launched it but nothing done no message.

root@serveur:~# curl -s https://gitlab.codycook.us/readynas-scripts/share_lun_ui_fix.sh/raw/master/share_lun_ui_fix.sh | bash
root@serveur:~#