Applies to: All editions; detailed exports require the applicable edition
Separate the result dimensions
A DriveErase operation has several distinct result dimensions:
- Erasure status: whether the configured operation completed.
- Coverage: whether the required logical range or device-managed operation was processed.
- Verification: whether the method’s verification procedure was available and passed.
- Compliance: whether the recorded method, device, execution, and evidence support a named Clear or Purge result.
- Health: whether the selected diagnostic found adverse device conditions.
Do not combine these into a single unsupported statement.
Typical erasure statuses
- OK: the configured operation completed successfully according to its recorded requirements.
- Completed – Not Certified: the operation completed, but required certification criteria were not established.
- Incomplete: the required range, pass sequence, or stage did not fully complete.
- Error: the operation could not complete.
A firmware-plus-fallback result can also identify that the firmware attempt failed and the overwrite fallback was used.
Verification
Verification can be:
- Performed and passed;
- Performed and failed;
- Not available for the final random pattern;
- Not applicable to the firmware method;
- Incomplete because of an error or interruption.
A successful write with failed required verification must not be described as verified.
Potential and actual compliance
Potential Compliance is an advance indication based on the selected device and method. Actual Compliance is determined after execution.
A positive actual result can depend on:
- Confirmed device and media type;
- Suitable method for that type;
- Complete preparation and coverage;
- Successful command or writes;
- Successful flushes;
- No disqualifying failed ranges;
- Required verification;
- Sufficient evidence about the firmware operation and its scope.