Hi, I love Scanner and DrivePool and I have nothing but good things to say about them to anyone who asks, but this problem is a bad one and I need help.
A couple months ago after running perfectly for at least six months on a new build, Scanner started reporting the size of one disk out of my four disk pool incorrectly (reported 10.9TiB when actually 9.1TiB). Both DP and Windows 10 x64 reported the correct size. I might have left it this way, since it didn't seem to cause any actual problems, but then Scanner tried to run a regular surface scan on that disk and immediately found unreadable blocks. I surmised it was trying to read blocks that didn't exist.
To fix the situation, I went to Scanner's advanced settings and clicked the "Reset settings..." button. This worked! All drive sizes were then correct, and all drives passed their surface scans. DP and Windows still showed the correct information.
BUT then I restarted the machine. When it came up, 2 of the 4 drives, one of which was the original misreported disk, had lost their partitions completely. After a lengthy restore from backup, finally everything seemed in order - all drives were the correct size, no errors during scanning.
And that's the way things stayed through many restarts for at least the last several weeks, but now after the most recent restart the original issue has popped up again. The same 10TB disk is again being reported as a 12TB disk in Scanner while DP and Windows report it correctly. I haven't tried to scan it - in fact I've disabled automatic scanning for that drive.
I'm sure this has something to do with the fact that I'm using two USB enclosures for these drives - 2 drives per enclosure. One enclosure has a 12TB and a 4TB, the other has a 12TB and the misreported 10TB. (I imagine this would never have been an issue if I were using a pair of identically sized drives for each enclosure.) It's just so strange that Scanner would be the only place the problem shows up. I'm currently running 22.214.171.12436, but the issue first arose with the last stable release, whatever that version number was.
Please if there is any way to correct this problem without ending up in another 48 hour rebuild, I would appreciate any advice. For now I just have to live without scanning that particular drive.