Error Handling
Error Handling section has the advanced settings to configure error handling while erasing or cloning the data.
Error handling attributes
KillDisk allows to select one of ways to handle Read/Write Errors:
- Abort entire group processing
- If erase Batch is in progress and one of the disks has errors, the erase process for ALL the disks in the Batch will be terminated.
- Abort only failed disk from group processing
- This is the default setting. Failed disks return an error and terminate the erase process. Other disks in the Batch will continue current operation.
- Ignore error for group processing
- Ignores the read/write error and continues erasing whatever is possible on the disk. None active or forth going operations will be terminated.
- Terminate process after number of errors
- Sets the error threshold to a certain amount before the disk operation is terminated and deemed unsuccessful.
- Number of read/write attempts
- Sets the number of attempts KillDisk makes to perform an operation when an error is encountered before it stops execution.
- Ignore preceding results
- Errors (if any) on previous steps (i.e. Examination) are ignored and following steps (i.e. Erase, Clone) will be executed. If turned off the errors on previous steps will stop all further actions.
- Use disk lock
- Locks disks from being used by any other applications while operation is in progress.
- Ignore disk lock errors
- Errors encountered with KillDisk not being able to access locked disks will be ignored.
- Ignore read/write errors
- Toggle whether read errors or write errors will be just ignored.
- Rely upon disk performance
- Sets a minimum acceptable read/write speed in megabytes per second for disks to flag under-performing drives.
SMART Diagnostics
S.M.A.R.T attributes can be used in error handling. Threshold limits can be set for some disks or for all the disks based on S.M.A.R.T parameters. This can speed up processing by terminating operations with unusable drives immediately.
Note:
Query execution for S.M.A.R.T attributes is time consuming and resource consuming operation. Single query can interrupt disk erasure procedure for several seconds. Thus it is recommended to validate these attributes less frequently.