Search the Community

Hi Guys, this week i got my first damage error via launchpad notification from my system SSD (Kingston 60GB). There were not much free space on it since months, so i was planning to swap it with a bigger one (WD 240GB) in any case. After file scan there was only one file damaged, which was not important, so i deleted it, run chkdsk /f on it and clone the whole partitions to a newer bigger SSD. Actually everything is working fine but the damage message is still present in launchpad's notification window and the old kingston drive is unplugged lying in the cubboard. I know from other launchpad messages that there are some error mesages which will not be reset immediatelly and are shown for days after the reason is already solved/gone. How long are damage error(s) present in launchpads warning display/window? Version-Info: Scanner v2.5.3.3191

I recently had Scanner flag a disk as containing "unreadable" sectors. I went into the UI and ran the file scan utility to identify which files, if any, had been damaged by the 48 bad sectors Scanner had identified. Turns out all 48 sectors were part of the same (1) ~1.5GB video file, which had become corrupted. As Scanner spent the following hours scrubbing all over the platters of this fairly new WD RED spinner in an attempt to recover the data, it dawned on me that my injured file was part of a redundant pool, courtesy of DrivePool. Meaning, a perfectly good copy of the file was sitting 1 disk over. SO... Is Scanner not aware of this file? What is the best way to handle this manually if the file cannot be recovered? Should I manually delete the file and let DrivePool figure out the discrepancy and re-duplicate the file onto a healthy set of sectors on another drive in the pool? Should I overwrite the bad file with the good one??? IN A PERFECT WORLD, I WOULD LOVE TO SEE... Scanner identifies the bad sectors, checks to see if any files were damaged, and presents that information to the user. (currently i was alerted to possible issues, manually started a scan, was told there may be damaged files, manually started a file scan, then I was presented with the list of damaged files). At this point, the user can take action with a list of options which, in one way or another, allow the user to: Flag the sectors-in-question as bad so no future data is written to them (remapped). Automatically (with user authority) create a new copy of the damaged file(s) using a healthy copy found in the same pool. Attempt to recover the damaged file (with a warning that this could be a very lengthy operation) Thanks for your ears and some really great software. Would love to see what the developers and community think about this as I'm sure its been discussed before, but couldn't find anything relevant in the forums.

Hi there, I saw a previous thread about putting a damaged disk back into the pool, but my question is slightly different... I have a disk that StableBit Scanner says has some damage. It's a small amount of damage vs. the whole disk, but of course, it's part of a big file, so that's likely toast. What happens now? What happens with DrivePool when a bad file is either "fixed" or becomes corrupt? Does the bad file get replicated to other pool members? Or does DrivePool figure out the disk has damage and overwrites the bad file? Should I leave the bad file in place (rename it so it stays put over the bad disk area) and copy a good file over to that folder? I've run chkdsk /f /b on the drive a few times (it takes around 18 hours), and Scanner is trying to "recover" the file - but I think that's going to fail. If chkdsk has done its process on some bad sectors, is the drive OK for a while? Or will DrivePool keep trying to write back to those sectors? Thanks...