Active KillDisk removes recoverable data from disks, partitions, and unused storage areas before a device is retired, reassigned, or reused. The operator selects a physical device or volume, chooses an erasure method, and runs a write operation that replaces the targeted data. This is different from deleting files or formatting a volume, which can leave underlying content recoverable. Active KillDisk can also wipe only free space when active files must remain. The target choice is destructive, and the program cannot infer which similar-looking disk the user meant to preserve.
Erase and Wipe differ
Erase targets the data in a selected disk or partition. Erasing a physical disk removes its partitions as well as their contents. Wipe targets unused space inside a supported volume so current files remain available while remnants of previously deleted files are overwritten.
Selecting Erase when Wipe was intended destroys active data. The physical-disk workflow requires the operator to enter ERASE-ALL-DATA before it proceeds, but that confirmation proves intent only after the target has been selected. Match the device by model, capacity, serial number, and partition layout before confirming.
Volumes need a lock
Active KillDisk must lock a partition before erasing it or wiping its free space. A program with an open document or another process using the volume can prevent that lock. Closing files and applications gives the operation a clean boundary.
A forced dismount invalidates existing file handles. Unsaved work can be lost even during a free-space wipe that is meant to preserve active files. Do not force the dismount until every application using the volume has stopped and its work has been saved elsewhere.
Methods change time
Erasure methods define the data pattern and number of passes written over the target. More passes multiply the amount of data written and extend the operation. Verification then reads selected areas to check the result, which adds another stage.
Verification coverage needs an explicit choice. A partial check samples less data and finishes sooner than a full read. A completed percentage applies to the areas checked; it does not make an ignored hardware error disappear. Review bad-sector messages and the final job result instead of relying on elapsed time alone.
SSDs use firmware
Flash storage manages physical cells behind a controller, so repeated host writes do not map as simply as they do on a magnetic disk. ATA Secure Erase asks a supported device to perform the erase through its own firmware. The documented workflow is available in the Linux-based Active KillDisk packages, not the Windows package, because Windows storage pass-through restrictions prevent that path.
Secure Erase must not lose power or be interrupted. The manual warns that interruption can leave a device damaged or locked. Use stable power, keep the machine awake, and do not treat the operation like a cancellable file copy.
Interrupted jobs leave state
Active KillDisk can detect a previously interrupted erasure and offer Resume or Restart. Resume continues from the recorded point, while Restart begins the selected method again. The appropriate choice depends on whether the target, method, and job record still match the intended operation.
Do not resume merely because the button is available. Confirm that no disk was replaced or reordered after the interruption. External enclosures and removable devices can appear under another device number after reconnecting, while a familiar capacity may belong to a different unit.
Reports need context
Logs and certificates record the target details, method, timestamps, verification, and reported outcome. They support an audit trail for a completed sanitization job. They do not restore data or correct a job that ran against the wrong disk.
Initializing an erased disk writes a new empty partition table so the device can be partitioned again. It does not undo the erase or recover the former volumes. If the device will leave the organization, finish the erasure and retain the report before creating any new filesystem.
