When using the "Force Damage Drive Removal", it skips "problem files" and removes the drive from the pool.
You'll see a "PoolPart.xxxxx" folder on the drive, and a folder structure that mirrors the pool (it may only be partial, as .. it only had part of the pool on it). From there , you can copy the files back into the pool manually, if needed. (or to another folder).
I've deleted the other post, as this is a DrivePool specific question and not as much Scanner related. So to keep everything in one thread, rather than potentially split between two...
That said, I'm sorry to hear about the problem drive!
For the drive removal, the "Force Damaged Disk Removal" option will skip files that generate errors and continue removing the drive. It will leave the remaining files on the drive, which you can then access and attempt to move off yourself.
Additionally, if the entire pool (or at least the data on the drive) is duplicated, then you can use the "duplicate data later" option when removing the disk, or even just physically remove the drive. Then let StableBit DrivePool reduplicate the data.
Alternative, you could use the balancing engine to do this, as it may have more luck.
To do this, open up the balancer settings and then the balancers tab, and open up the "Drive Usage Limiter" balancer. Uncheck both the duplicated and unduplicated options for the disk in question.
