SmartDisk stops shortly after starting. Studying chunkstored trace, you see:
0 FILESYS -984 1279813225273234 Failed to open lock file '\\?\D:\store\dedupe\lock'
0 CSD -643 1279813225273234 error calling FileSysOpenLocked()
0 CSD -1140 1279813225273234 Error locking lock file! (Is another chunkstored running?)
SmartDisk is unable to access the lock file.
This issue has been reported during a disaster recovery. If SmartDisk data is held on a non-system disk, and the system disk is lost, the data in SmartDisk is recoverable. When a new SmartDisk installation on a Windows OS system disk is attached to the existing SmartDisk data (see the DR solution for details), this error is likely to be reported.
The root cause of the error is Windows security. The newly created SmartDisk user does not have permissions on the directories and files in the chunkstore, or the staging areas because the user_id is not the same.
For all SmartDisk data directories, there is an unknown user who has permissions but the SmartDisk user has none. It is necessary to recursively remove the old user from directories and files, then recursively add the SmartDisk user will Full Control to all the directories and files.
Windows uses an internal user_id to register permissions to files and directories. If the user is dropped and recreated and the user_id changes then it is a different user, even if it has the same username.