Applies to: All editions
Overview
Overwrite-based sanitization writes a defined pattern sequence across the logical address range exposed by the selected physical device. DriveErase processes the device in blocks, records write and flush results, and applies method-specific verification where available.
Overwrite is available in every edition and is the only sanitization approach available in Standard.
Processing sequence
A normal overwrite operation includes:
- Confirming the target identity and reported capacity;
- Preparing access to the physical device;
- Writing each configured pass from the beginning to the end of the addressable range;
- Issuing controlled flush operations so buffered data is submitted to the storage stack;
- Running the method’s verification procedure when applicable;
- Recording coverage, failed ranges, verification, duration, and final status.
Multi-pass profiles repeat the full logical-range write for each pass.
Appropriate use
Overwrite is normally the preferred host-driven method for functioning magnetic HDDs. It is also used when firmware sanitization is unavailable.
For USB-attached storage, overwrite is generally the available approach because the bridge often does not expose native firmware sanitization commands.
Flash-media scope
On SSDs, NVMe devices, USB flash drives, and memory cards, an overwrite processes the exposed logical addresses. Internal wear leveling, over-provisioning, remapped blocks, and retired cells can contain data that is not addressable through ordinary host writes.
Use a supported device-firmware method for directly attached flash storage when the required assurance calls for device-managed sanitization. Where that is impossible, document the overwrite limitation and apply physical destruction when residual risk remains unacceptable.
Pass count
More passes increase duration and device writes. Pass count alone does not determine sanitization quality. Device type, complete coverage, errors, verification, hidden storage, and the actual disposition are more important than selecting the largest pass count.
Random-final profiles
Some profiles end with cryptographically generated random data. Because the complete generated random stream is not retained for later comparison, sampled final-pattern verification is not available for those profiles. The report distinguishes the completed write from a verified fixed final pattern.