 |
HDShredder will try to troubleshoot sector errors as they occur. If this is not possible, the errors will be tallied in a corresponding error statistic.
When read or write errors occur, HDShredder will implement certain strategies in an attempt to read or write the data, if possible. The amount of time used on defective areas to a large extent depends on the respective media. The media and its respective status will determine whether a few seconds or several minutes are needed for repeated attempts. Therefore, it is recommended to always activate the SmartDefectSkip option, which postpones the handling of defective sectors until the deletion of all intact areas has been completed. If too much time elapses, the process can be aborted without exposing the data in the intact areas.
During the deletion process, read errors can only occur in a Verfication Run. HDShredder will then try to read the defective areas immediately following the termination of the run within a single Troubleshooting Run, by using special access strategies. During the Troubleshooting Run, the number of the indicated errors may reduce depending on the areas on the media that at first were not, then could ultimately be accessed.
|
Write errors can only occur during a deletion run. In this case, HDShredder will attempt to write the defective areas immediately following termination of the deletion run with a proper Troubleshooting Run, by using special access strategies. During the error recovery run, the number of write errors indicated may decrease, depending on the areas that are successfully deleted.
If the selected deletion method contains verification runs, HDShredder will execute them in addition to the deletion process. Verification errors are counted whenever there is a mismatch between the data read and the previously written pattern. Furthermore, if read errors occur during the Verification Run, they are also counted as verification errors. Therefore, the number of verification errors indicates the number of sectors in which the safe deletion could not be confirmed.