StableBit Scanner Advanced Settings
You can tweak advanced settings in DrivePool by editing a .config file in notepad.
The file is located in C:\Program Files (x86)\StableBit\Scanner\Scanner.Service.exe.config_default on the server.
Some older builds did not include the file, it can be downloaded here: http://dl.covecube.com/configs/Scanner.Service.exe.config
In order to put the file into effect, you will need to rename it from Scanner.Service.exe.config_default to Scanner.Service.exe.config and restart the server (or just restart the StableBit Scanner system service).
A fresh copy of the .config file is written to C:\Program Files (x86)\StableBit\Scanner\Scanner.Service.exe.config_default on upgrade, so your changes will not be overwritten.
Editing the config file
Open the file in notepad. You will see an XML formatted file. If you're not familiar with XML then all that you need to know is that the values that you can change look like this:
You can change this line to:
The setting name is right above that line:
<setting name="UnsafeDirectIo" serializeAs="String">
In this case the name is CoveFsLogSizeMB.
There are also numerical values and time values.
- ErrorReportingOverride - Report errors to Covecube Inc. automatically.
- DirectIOOverride - Set to False to disable Direct I/O.
- SmartOverride - Set to False to disable all SMART calls.
- NotificationOverride - Set to False to disable WHS notifications.
- GoodIdentifyOverride - Scanner will not query certain disks for SMART or identification data because of some bad firmware on them that causes data corruption. If you have one of these disks and would like to force Scanner to query your disk, then set this to a regular expression of your disk model.
- UnsafeDirectIo - The Scanner supports different methods of communicating with the disk directly, it needs to do this to obtain SMART data and identification data and to issue commands to it that provide additional functionality. The access methods are grouped into 4 groups, Internal and External, and for each, Safe and Unsafe. Methods that have been known to cause a system crash on a small percentage of machines are categorized as Unsafe and are disabled by default. If the Scanner is having trouble talking to your disk directly, you can enable Unsafe mode to see if you get better results.
Don't forget to rename the config file after you make the change and restart the server (or service), as noted at the top of this page.