Running 2.5.0.2968 beta on WHS2011
Just thinking outloud...
[i know it has been said before that the scanner program is designed not to write to the hard disk]
I just had a disk develop problems - currently 4,390 bad sectors on a 3TB advanced format drive per Stablebit Scanner. [Why does HD Sentinel v4.50 only report 592 weak sectors?] The drive is marked "Damaged", and the drive pool balancer started to move files off of the drive (until I turned it off).
I ran a file scan, and only one file was reported as being damaged. My only automoated option appears to be to try to recover the file.
1) Why not add an option to permit me to delete the file from the results screen? Instead, I had to manually track down the file to delete it via Windows Explorer.
After I deleted the file, I ran another file scan and it reported no damaged files.
I copied over the file from my backup offline storage. Almost immediately, HD Sentinel reported another bad sector on the drive. I started another Stablebit Scanner file scan, and the same file was reported as damaged. So apparently, the location where that file is being stored is still unstable.
2) Why not add an option to permit me to deep scan all of the sectors of a damaged file to see if additional damaged surface area can be found and marked inactive? I don't want to scan the entire 3TB drive again, if only a small area is damaged.
To prevent the problem from replicating again when I replaced the damaged file with my backup copy, I left it on the disk, rename it to "Damaged File.xxx", and reloated it to the root directory outside the pool. I then copied the backup file to the drive - this time to a different location, as the damaged area is still occupied by the "Damaged File.xxx".
3) Why not add an option to permit me to rename the file from the results screen? Instead, I had to manually track down the file to rename it via Windows Explorer.
I am now paranoid about the stability of this drive, and am concerned about further deteriation over time. Waiting to see if I should RMA it...
4) Why not add an option to rescan "damaged drives" on a different time schedule vs. the default 30 day cycle. I might like to scan this drive every 14 days to ensure that there is no additional performance deteriation.
5) I noticed that were were good sectors mixed in with bad sectors. Why not add an option to block off and mark all sectors as bad beginning with xxxxx and ending with xxxxx - that way you are not trying to store data in a questionable area.
Just some thoughts...