Probably six months ago I got a notice from Scanner that one of my pooled (using DrivePool) 4TB drives was damaged (less than 2MB worth). I moved all the files off of it, deleted the partition (leaving the drive completely empty), and created a new partition with a full (not "quick") format. Scanner says the damage is still there, but (no surprise) there are no files allocated in the damaged area. However, Scanner loves to keep reminding me the drive is damaged, even though the damage has not increased, and I ran a Burst Test on the drive for an entire day, which it passed.
My pool is 99% full without that "damaged" 4TB drive being included and that prevents me backing up the computers in the house, so I would like to add it back to the pool, since the damage area isn't in use. What is frustrating is that DrivePool won't put any files on it, because it is "damaged", even though the damage is old and quarantined. The "damaged" drive had yet to fail in six months, but one of my older 1TB drives has since failed and I lost some non-essential data because there was no room to duplicate it. I finally gave up and disabled the option to remove duplicated files from damaged drives, so that it would use the drive at least for duplication.
I recently discovered that the 4TB drive had a bad SATA cable, so I am wondering if perhaps the "damage" isn't even real. However, I don't see an option in Scanner to manually re-check damaged sectors -- all I see is an option for how often it should automatically retest them.
Anyways, I'm wondering if there's any way to recheck the drive, or somehow clear the "damaged" flag for old damage?
Question
Nerva
Probably six months ago I got a notice from Scanner that one of my pooled (using DrivePool) 4TB drives was damaged (less than 2MB worth). I moved all the files off of it, deleted the partition (leaving the drive completely empty), and created a new partition with a full (not "quick") format. Scanner says the damage is still there, but (no surprise) there are no files allocated in the damaged area. However, Scanner loves to keep reminding me the drive is damaged, even though the damage has not increased, and I ran a Burst Test on the drive for an entire day, which it passed.
My pool is 99% full without that "damaged" 4TB drive being included and that prevents me backing up the computers in the house, so I would like to add it back to the pool, since the damage area isn't in use. What is frustrating is that DrivePool won't put any files on it, because it is "damaged", even though the damage is old and quarantined. The "damaged" drive had yet to fail in six months, but one of my older 1TB drives has since failed and I lost some non-essential data because there was no room to duplicate it. I finally gave up and disabled the option to remove duplicated files from damaged drives, so that it would use the drive at least for duplication.
I recently discovered that the 4TB drive had a bad SATA cable, so I am wondering if perhaps the "damage" isn't even real. However, I don't see an option in Scanner to manually re-check damaged sectors -- all I see is an option for how often it should automatically retest them.
Anyways, I'm wondering if there's any way to recheck the drive, or somehow clear the "damaged" flag for old damage?
Link to comment
Share on other sites
9 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.