RN104 on 6.9.5 - SMB Doesn't Load (problem in smb.conf)

[WiredRacing]

So I recently upgraded the firmware from 6.7.5 to 6.9.5 and also did a drive upgrade, exporting a volume, re-importing it and various other things that have led to several reboots of the NAS. But basically after the second reboot, SMB wasn't loading anymore. I could select it in the Management Console and check the boxes but when I checked the status ("systemctl status -a smb") I'd get:

 [2019/03/17 04:00:22.733065,  0] ../lib/param/loadparm.c:1121(lp_set_enum_parm)
 WARNING: Ignoring invalid value '(null)' for parameter 'smb encrypt'

I found a thread on here that says I need to change that to "smb encrypt = default", and sure enough, it then would load smb (after "systemctl start smb" of course). However this is temporary as the file seems to be auto generated and each boot of the NAS reverts back to the problematic change. 

Anyone have any idea what I need to change/fix so this doesn't get reverted on every reboot?

Or, anyone have any suggestions on how to build a timed script to make this edit in the file on reboot, but after the failed attempt is made (just concerned of a race condition).

[JohnCM_S]

Hi WiredRacing,

2019/03/17 04:00:22.733065,  0] ../lib/param/loadparm.c:1121(lp_set_enum_parm)
 WARNING: Ignoring invalid value '(null)' for parameter 'smb encrypt'

That is just a warning and should not be the reason the NAS does not start the SMB. It says it is ignoring the invalid entry, which then defaults to the default smb.conf configuration.

There could be another reason the SMB does not load. You may download the logs and then provide it to us so we can check. You may upload it to Google Drive then PM me the download link.

Regards,

[JohnCM_S]

Hi WiredRacing,

We’d greatly appreciate hearing your feedback letting us know if the information we provided has helped resolve your issue or if you need further assistance.

If your issue is now resolved, we encourage you to mark the appropriate reply as the “Accept as Solution” or post what resolved it and mark it as a solution so others can be confident in benefiting from the solution. 
 
The NETGEAR community looks forward to hearing from you and being a helpful resource in the future!
 
Regards,