DriveErase reports several aspects of a sanitization operation, and they should not be interpreted as though they all mean the same thing. The erasure status describes whether the requested operation completed, verification records whether the relevant checks succeeded, compliance indicates whether the evidence supports a named sanitization outcome, and health describes the condition of the device.
Understanding these distinctions is important when a drive is being sold, returned to a customer, reused within an organization, or permanently retired.
Erasure status
The erasure status indicates what happened during the sanitization stage.
OK means the configured operation completed successfully according to its recorded requirements.
Completed – Not Certified means processing completed, but the requirements for a positive certified result were not established.
Incomplete indicates that the required operation did not finish in full, while Error indicates that the operation could not complete successfully.
These statuses need to be read alongside the detailed information. A drive that completed a logical overwrite but could not establish every compliance prerequisite is different from one that stopped halfway through execution.
Coverage and verification
Coverage describes which required storage areas were processed by the completed method. For overwrite-based sanitization, this concerns the logical address range that had to be written. For firmware-based methods, the relevant scope depends on the storage command and device capabilities.
Verification provides additional evidence about the completed operation. A zero overwrite, for example, may include sampled comparison against the expected zero pattern.
Some random-final profiles do not provide that form of verification because the complete generated random sequence is not retained. Firmware operations may use different command-status evidence rather than ordinary pattern readback.
A method that required verification but failed it should not be described as verified.
Potential Compliance and Actual Compliance
Potential Compliance is shown before execution and indicates the standards-related outcome that may be possible with the selected method and device.
Actual Compliance is determined from the operation that took place.
For example, selecting NIST Clear for a magnetic HDD may indicate that a Clear result is possible. If required writes fail, capacity restrictions remain unresolved, or verification does not pass, the completed operation may not receive a positive Clear result.
A successful firmware command can also have a narrower result than originally expected when the available evidence does not establish the required storage scope.
Always use the Actual Compliance field when describing the completed sanitization.
Firmware fallback results
If Firmware + Fallback was selected, determine whether the firmware method succeeded or whether DriveErase used the overwrite alternative.
A successfully completed fallback does not establish that the firmware method was successful. It also does not provide the device-managed storage coverage that the failed firmware operation might have achieved.
This distinction is particularly important when a Purge outcome is required for an SSD.
Health assessment
A health grade evaluates device condition, not data sanitization.
A drive can be successfully sanitized while receiving a poor health score because of unreadable blocks, SMART warnings, or write errors discovered afterward.
Conversely, a device can have excellent diagnostic results even when the erasure operation is incomplete.
Before releasing the drive, confirm the erasure status and required compliance result. Then consider the health assessment separately if the device is intended for reuse.
