- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
smb.conf keeps getting corrupted
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Recently my RN202 crashed. Only option to get it running again was to powercycle it. Since then I have troubles with running SMB. When I try to enable it in Frontview, it simply does not. I used ssh to check and found that if I manually wanted to start smbd, it gives an error:
root@NAS:/# smbd -F -S
smbd version 4.4.5 started.
Copyright Andrew Tridgell and the Samba Team 1992-2016
WARNING: Ignoring invalid value '' for parameter 'security'
error opening config file '/etc/samba/smb.conf'
I checked the smb.conf file. It contains the line
security =
if I edited that line to
security = user
I can manually start SMB this way. However, I cannot use Frontview to make any SMB related configuration changes because it overwrites smb.conf and the issue is back. I know that smb.conf is automatically regenerated by design, but in my case it is regenerated incorrectly.
How can I permanently fix this issue?
I have a RN202 running 6.6.1
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You can check what it currently looks like by doing e.g.
# sqlite3 -column -header /var/readynasd/db.sq3 'SELECT * from service_cifs'
If that field is set incorrectly this ought to do the trick:
# sqlite3 /var/readynasd/db.sq3 'UPDATE service_cifs SET security="user"'
Normally it's the config file that needs fixing not the database. We use the database to automatically repair broken configuration.
All Replies
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: smb.conf keeps getting corrupted
It's certainly something broken in the database: /var/readynasd/db.sq3, in table service_cifs maybe? I have only one entry, second field value is 'user'. What do you have?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You can check what it currently looks like by doing e.g.
# sqlite3 -column -header /var/readynasd/db.sq3 'SELECT * from service_cifs'
If that field is set incorrectly this ought to do the trick:
# sqlite3 /var/readynasd/db.sq3 'UPDATE service_cifs SET security="user"'
Normally it's the config file that needs fixing not the database. We use the database to automatically repair broken configuration.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content