duro

Christopher, I do thank you for responding and offering to help, but instead of drilling down to discover the root cause, I've decided to go ahead and just rearrange things to avoid the problem in the future. I'm going to purchase another 10TB drive to replace the 4TB. I'll put the two 12TB drives in one enclosure, and the two 10TBs in the other. That way Scanner won't have the opportunity to get the sizes mixed up. I'll probably end up restoring 20 or 30 TBs of data from backup, but hey that's what backups are for. Thanks again. And for the record I'm still happy with the Stablebit soft

No I have definitely not opened a ticket. The misreported drive is a WD100EFAX. It shares the enclosure with a WD121KRYZ. The enclosure - which is technically more of a docking station - is a Wavlink ST334U. I've been on the latest stable release of Scanner - 2.5.6.3336 since shortly after it was posted, I believe. The issue first appeared with the last stable release. I have never installed a beta or release candidate version of Scanner.

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 unreadabl