>It depends on the drive's firmware. Some do background scans of blocks while >idle. Others do not. Since you >have no way of knowing which is which (or even >when the backgroundscan is done), the safest way to force a >scan is to read >the whole drive... any blocks whose raw error count is too high will be >rewritten to fresh >blocks. If it's a good SSD you'll likely not notice this >happening. If it's a crappy thumb drive... you may >be better off copying to >some other media..
Hmmm.. I wonder if there is a program akin to Spinrite that will do that on SSDs (i.e. reread and rewrite every byte). I know Steve Gibson is working on a new version of Spinrite that will work with SSDs so that could be the solution when it comes out... -Ali