Search the Community

I've noticed DrivePool gets stuck some times if the disk it's trying to read from has a problem. I'm currently looking at Windows Events 7 & 153, the first read error was at 1:52pm and it is now 2:30pm and the Event log keeps writing new 153s and 7s. The DrivePool GUI is hung, the Disk Management snap-in won't load, and other machines on the network can't read or write to the share of this pool. My question is, why can't DrivePool give up and read from the other copy of the file? I'm sure the Scanner would eventually tell me I have a bad drive and I could deal with it, but neither DrivePool or Scanner seem to know anything is wrong at the moment. My instance of DrivePool 2.1.1.561 is on on win server 2012 R2 There is only one Pool and the whole thing to set to Duplicate data. Windows Event 153: The IO operation at logical block address [some address] for Disk [some disk] (PDO name: \Device\[some device]]) was retried. Windows Event 7: The device, \Device\Harddisk[some disk]\DR##, has a bad block.