Error Handling
Disk Clone has a wide capabilities to handle errors during continuous disk processing. Those are the advanced settings to configure Disk Clone's error handling.
Error handling attributes
Disk Clone allows user to select 1 of 3 ways to handle Read/Write Errors:
- Abort entire disk group processing
- This means that if user runs a Batch erase and one of the disks has errors the erase process for ALL the disks in the batch is terminated
- Abort only failed disk from group processing
- This is the suggested setting. Failed disks return an error and terminate the erase process. But other disks in the batch are not interrupted from the erase operation
- Ignore error for disk grouping
- Ignores the read/write error and continues erasing wherever is possible on the disk. No active or forth going operations are 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 Disk Clone 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 performed. 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
- Ignore disk lock errors
- Errors encountered with Disk Clone not being able to access locked disks are ignored
- Ignore read/write errors
- Toggle whether errors should appear for read/write errors
- Rely upon disk performance
- Set a minimum acceptable read/write speed in megabytes per second for disks to flag under-performing drives.
S.M.A.R.T. Diagnostics
S.M.A.R.T. attributes may also be used in error handling. So threshold limits may be set on some or on all of the disks S.M.A.R.T. parameters. This may speed up processing by immediately terminating operations with unusable drives
Note: Query execution for S.M.A.R.T. attributes is time and resource consuming operation. It can interrupt disk erasure procedure for
several seconds. Thus it is recommended to validate these attributes not very frequently