NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Crash_HI
Apr 27, 2025Guide
SMB Stopped working
Hi,
I recently rebuilt my ReadyNAS Pro Pioneer RNDP6000 and did a factory reset and installed drives. This unit had been updated to OS 6.10.9. It was working for a few days as I was loading data onto it via SMB, but there was a power outage, and after restarting, SMB is not working. I can connect via Frontview and DLNA is working, but the SMB service will not start, and even with SMB enabled for a share, the NAS is not visible to Windows and can't be connected as a SMB share. I can ping the NAS IP address from the Windows CMD line. Something may be wrong with one of the files used to generate smb.conf, but I don't know what those consist of so I don't know what to do.
I tried to attach my logs here, but it says it only accepts jpg, gif, png, pdf.
I tried to manually start the SMB service using SSH, and this is the result and error log:
root@CrashTV:/# 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@CrashTV:/# 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 Sat 2025-04-26 16:13:33 HST; 12s ago
Process: 6655 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMBDOPTIONS (
code=exited, status=1/FAILURE)
Main PID: 6655 (code=exited, status=1/FAILURE)
Apr 26 16:13:33 CrashTV systemd[1]: Starting Samba SMB Daemon...
Apr 26 16:13:33 CrashTV smbd[6655]: [2025/04/26 16:13:33.219182, 0] ../lib/param/loadp
arm.c:1121(lp_set_enum_parm)
Apr 26 16:13:33 CrashTV smbd[6655]: WARNING: Ignoring invalid value '(null)' for para
meter 'smb encrypt'
Apr 26 16:13:33 CrashTV systemd[1]: smb.service: Main process exited, code=exited, stat
us=1/FAILURE
Apr 26 16:13:33 CrashTV systemd[1]: Failed to start Samba SMB Daemon.
Apr 26 16:13:33 CrashTV systemd[1]: smb.service: Unit entered failed state.
Apr 26 16:13:33 CrashTV systemd[1]: smb.service: Failed with result 'exit-code'.
Any help would be greatly appreciated
Below is the section of the smbd.log from today:
[2025/04/26 14:36:11.093503, 0] ../lib/param/loadparm.c:1121(lp_set_enum_parm)
WARNING: Ignoring invalid value '(null)' for parameter 'smb encrypt'
[2025/04/26 15:31:29.351910, 0] ../lib/param/loadparm.c:1121(lp_set_enum_parm)
WARNING: Ignoring invalid value '(null)' for parameter 'smb encrypt'
[2025/04/26 15:31:57.913392, 0] ../lib/param/loadparm.c:1121(lp_set_enum_parm)
WARNING: Ignoring invalid value '(null)' for parameter 'smb encrypt'
[2025/04/26 15:32:16.267281, 0] ../lib/param/loadparm.c:1121(lp_set_enum_parm)
WARNING: Ignoring invalid value '(null)' for parameter 'smb encrypt'
[2025/04/26 15:34:13.397765, 0] ../lib/param/loadparm.c:1121(lp_set_enum_parm)
WARNING: Ignoring invalid value '(null)' for parameter 'smb encrypt'
[2025/04/26 15:34:39.810929, 0] ../lib/param/loadparm.c:1121(lp_set_enum_parm)
WARNING: Ignoring invalid value '(null)' for parameter 'smb encrypt'
[2025/04/26 15:34:54.021046, 0] ../lib/param/loadparm.c:1121(lp_set_enum_parm)
WARNING: Ignoring invalid value '(null)' for parameter 'smb encrypt'
[2025/04/26 15:37:50.226151, 0] ../lib/param/loadparm.c:1121(lp_set_enum_parm)
WARNING: Ignoring invalid value '(null)' for parameter 'smb encrypt'
[2025/04/26 15:40:01.424582, 0] ../lib/param/loadparm.c:1121(lp_set_enum_parm)
WARNING: Ignoring invalid value '(null)' for parameter 'smb encrypt'
[2025/04/26 15:49:37.183425, 0] ../lib/param/loadparm.c:1121(lp_set_enum_parm)
WARNING: Ignoring invalid value '(null)' for parameter 'smb encrypt'
[2025/04/26 15:50:33.023881, 0] ../lib/param/loadparm.c:1121(lp_set_enum_parm)
WARNING: Ignoring invalid value '(null)' for parameter 'smb encrypt'
[2025/04/26 15:50:35.968857, 0] ../lib/param/loadparm.c:1121(lp_set_enum_parm)
WARNING: Ignoring invalid value '(null)' for parameter 'smb encrypt'
[2025/04/26 15:51:44.749007, 0] ../lib/param/loadparm.c:1121(lp_set_enum_parm)
WARNING: Ignoring invalid value '(null)' for parameter 'smb encrypt'
[2025/04/26 15:52:29.024027, 0] ../lib/param/loadparm.c:1121(lp_set_enum_parm)
WARNING: Ignoring invalid value '(null)' for parameter 'smb encrypt'
[2025/04/26 15:52:54.650289, 0] ../lib/param/loadparm.c:1121(lp_set_enum_parm)
WARNING: Ignoring invalid value '(null)' for parameter 'smb encrypt'
[2025/04/26 15:52:59.098875, 0] ../lib/param/loadparm.c:1121(lp_set_enum_parm)
WARNING: Ignoring invalid value '(null)' for parameter 'smb encrypt'
[2025/04/26 15:58:26.560194, 0] ../lib/param/loadparm.c:1121(lp_set_enum_parm)
WARNING: Ignoring invalid value '(null)' for parameter 'smb encrypt'
[2025/04/26 15:58:26.766612, 0] ../lib/param/loadparm.c:1121(lp_set_enum_parm)
WARNING: Ignoring invalid value '(null)' for parameter 'smb encrypt'
[2025/04/26 15:58:50.329817, 0] ../lib/param/loadparm.c:1121(lp_set_enum_parm)
WARNING: Ignoring invalid value '(null)' for parameter 'smb encrypt'
[2025/04/26 15:59:31.875287, 0] ../lib/param/loadparm.c:1121(lp_set_enum_parm)
WARNING: Ignoring invalid value '(null)' for parameter 'smb encrypt'
[2025/04/26 16:01:06.398207, 0] ../lib/param/loadparm.c:1121(lp_set_enum_parm)
WARNING: Ignoring invalid value '(null)' for parameter 'smb encrypt'
[2025/04/26 16:01:55.378752, 0] ../lib/param/loadparm.c:1121(lp_set_enum_parm)
WARNING: Ignoring invalid value '(null)' for parameter 'smb encrypt'
3 Replies
- Crash_HIGuide
It seems that the following file
/etc/default/services
contained the line:
USER_HOME_DIRECTORY_SMB_ENCRYPT=(null)
which may have been preventing the SMB service from loading.
I edited this and changed it to:
USER_HOME_DIRECTORY_SMB_ENCRYPT=default
and after restarting, SMB seems to be working again.
I'm not sure what could have caused this, but will report back if it reoccurs.
- StephenBGuru - Experienced User
Crash_HI wrote:
It seems that the following file
/etc/default/services
contained the line:
USER_HOME_DIRECTORY_SMB_ENCRYPT=(null)
which may have been preventing the SMB service from loading.
Odd, as my own NAS has
USER_HOME_DIRECTORY_SMB_ENCRYPT=and it starts normally.
SMB encryption is configured for each share, and is set to "Enabled" in all my shares.
- Crash_HIGuide
The only think I can think of is that having "(null)" there was causing the problem, since that was a warning in the error log, and I didn't know what else to mess with. I don't know what put that value there, but I posted my finding in case anyone else experiences the same scenario. It seems that removing "(null)" completely would have worked too. I used "default" because that was what I read was one of the valid values for this parameter.
Thanks!
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!