How to securely erase a SATA SSD
Overwriting an SSD from software doesn't reliably destroy data — and it wears the drive out. ATA Secure Erase is the right tool.
SATA SSDs speak the ATA command set, and ATA has a purpose-built answer to erasure: Secure Erase. It tells the SSD controller to wipe every stored cell, including the over-provisioned area the operating system can't see.
Why overwriting an SSD is a bad idea
SSDs spread writes across flash cells via a controller that the host can't address directly. Writing zeros from software misses cells the controller has set aside, and it burns through the drive's write endurance for no good reason. A single Secure Erase is both more complete and far gentler.
Secure Erase vs Enhanced Secure Erase
- Secure Erase — the standard ATA erase. Maps to NIST 800-88 Clear.
- Enhanced Secure Erase — additionally erases sectors that were written then reallocated. Maps to NIST 800-88 Purge.
If the drive supports Enhanced Secure Erase and the data is leaving your control, use it — it covers edge cases the standard erase can leave behind.
Frozen drives
Many BIOSes issue a security freeze on boot, which blocks ATA erasure commands until the drive is power-cycled without the freeze being re-issued. This is a safety feature, but it trips people up: the erase simply fails while the drive is frozen.
tScrub detects a frozen drive, guides you through the power-cycle needed to lift the freeze, and re-runs the erase.
Erasing a SATA SSD with tScrub
- Boot the appliance with the SSD connected.
- tScrub identifies it as an ATA drive and checks which erase commands it supports.
- It runs Enhanced Secure Erase where available (Secure Erase otherwise), handling any freeze automatically.
- The report records the method, final status, and pre/post-wipe SMART health.
FAQ
Is Secure Erase the same as "formatting" the drive?
No. A filesystem format just rewrites the directory structures — the data is still there. Secure Erase destroys the data itself at the controller level.
Will Secure Erase brick my SSD?
No. It's a standard, supported ATA command. The old warnings date from buggy early SSDs; on any modern drive it's routine.