Craig

I was looking under: Control Panel\System and Security\Security and Maintenance\Reliability Monitor and noticed every day I have a "critical" problem that is StableBit Scanner Service stopped working, and based on the times, I can only assume this is happening when I shutdown the machine for the night. If it makes a difference, I have windows set to really shut down, and not the windows 10 fake shutdown for fast resume (that appeared to be causing me problems with external drives). I was wondering whether this was indicative of a real problem, or is this just a quirk/slow shut down by the scanner? There are no other daily criticals like this. Here are the problem details if they are of any help: Description Faulting Application Path: C:\Program Files (x86)\StableBit\Scanner\Service\Scanner.Service.exe Problem signature Problem Event Name: CLR20r3 Problem Signature 01: Scanner.Service.exe Problem Signature 02: 2.5.6.3336 Problem Signature 03: 5ddaf7c5 Problem Signature 04: System.Management Problem Signature 05: 4.8.4084.0 Problem Signature 06: 5dda3e36 Problem Signature 07: 8a Problem Signature 08: 51 Problem Signature 09: PSZQOADHX1U5ZAHBHOHGHLDGIY4QIXHX OS Version: 10.0.19041.2.0.0.256.48 Locale ID: 2057 Additional Information 1: 2beb Additional Information 2: 2beba6fb4680d73a8c78ca7c24ccdb46 Additional Information 3: 430e Additional Information 4: 430eb0c2672849df16da595cad5eb9e6

Thanks to the service log I've spotted that renaming a duplicated file appears to make drivepool check the entire pool. Is that the expected behaviour? (I probably do this at least once a day, which is why I must see it checking so often.)

I'll report back when I've had time to look at all the options, but wanted to say thank you now for both the replies.

I'm a big fan of DrivePool, and recently moved a load of pooled drives to a new computer and it just worked, so that was brilliant. Just getting that out there so you know I'm not moaning for the sake of it! However, I'd really like to know more about why DrivePool is doing certain things. My system seems to re-measure a lot. To resolve this I've slowly replaced cables, drives, controllers, and now the whole computer (not just for DrivePool, but I had hoped it would help.) I probably do have a dodgy disk, but I can't afford to replace the whole lot, and it's not obvious which one is suspect. (I do also have scanner, 3 drives have minor smart problems, but otherwise healthy.) So would it be possible to find out what triggered a measure? If it thinks a drive disappeared for a second, can I find that in a log, or could it be exposed in the UI better? A bonus question: could DrivePool tell us what files it thinks are open? A few months ago I'd always have a baseline 20+ files open (as reported in the UI), with no pool activity. I replaced an old drive and the files open dropped to 10, which made me wonder is having persistent files open another symptom of an underlying disk issue? Thanks!