Quote:
|
Originally Posted by madeinoz
Ok seem to have found the problem.
for anyone else that has the problem.
I initiall tried recovering via the DRImage, but this kept on failing, So I started poking around in the logfiles via the shell.
In the /var/log/samba/log.winbindd I was getting alot of "tdb(/var/lock/samba/winbindd_idmap.tdb): rec_read bad magic 0x42424242 at offset=32280" errors.
So looks like the winbind database got corrupt! I ended up deleting all the files under /var/lock/samba and restarted samba on the snapserver, this re-creates all those files. Snapserver is now talking to the Active directory again 
WARNING doing this stuffs up all userID mappings on the AD on the snapserver, so I went back to factory default ACLs on volume and then had to reset all directory user permisisions for all relevenant Active directory groups/ users etc..
All is working now  |
How can I access /var/lock/samba/ directory on a SnapServer 520 with GuardianOS 4.4.049sp3?
Thankx,
Pulsar