Technical data

6.1 Deletion area

Important: The sectors specified for the sector area always refer to the initially selected dele-

tion area (6.1 Deletion area) and are indicated in relation to it. Example: If you have selec-

ted a partition as deletion area and specified the sector area from 0 to 9, the first 10 sectors

of the partition will be deleted, even if these sectors have another absolute number on the

medium.

6.2 Automatic troubleshooting

In case of occurring errors, HDShredder tries to troubleshoot them the best possible. If this is

not possible, the errors will be mentioned in a corresponding error statistic. The following

chapters give you more detailed information on the troubleshooting and error statistic in HD-

Shredder.

6.2.1 Intensive reading/writing

In case of read or write errors, HDShredder uses different strategies in order to still be able to

read or write the data, if possible. The time used for defective areas depends to a large extent

on the respective medium. According to the medium and its state, several seconds up to

minutes can be needed for repeated attempts. Therefore, it is recommended to always activ-

ate the option SmartDefectSkip (5.9.2 General options) because then handling defective

sectors takes place after the deletion of all intact areas has been finished. The process can

then be aborted if it takes too long without exposing the data in the intact areas.

6.2.2 Read errors

During the deletion process, read errors can only occur in a verification run. HDShredder then

tries to read the defective areas immediately after termination of the run (option SmartDefect-

Skip 5.9.2 General options) within a special troubleshooting run (5.10.6 Course of the pro-

cess), using special access strategies. During the troubleshooting run, the number of the indic-

ated errors can reduce according to the areas on the medium, which could be finally accessed.

Note: Read errors, that occur during the verification run, are not counted as read errors but

as verification errors (5.10.3 Status indication).

6.2.3 Write errors

Write errors can only occur during a deletion run. HDShredder then tries to write the defective

areas immediately after termination of the deletion run (option SmartDefectSkip, 5.9.2 Gen-

eral options) within a special troubleshooting run (5.10.6 Course of the process), using spe-

cial access strategies. During the troubleshooting run, the number of the indicated write errors

can reduce according to the areas on the medium, which could be finally accessed.

6.2.4 Verification errors

If the selected deletion method contains verification runs, HDShredder executes verification

runs (5.10.6 Course of the process) in addition to the deletion process. A verification error is

counted if the data read does no match the previously written pattern.. Furthermore, read er-