6/2/2023 0 Comments Ata secure erase![]() So in the context of this post, I am trying to unfreeze my drive. There is also 'Enhanced Secure Erase', which (at least on the SSDs I've used it on) takes a few seconds longer and appears to physically erase all cells. ![]() ![]() For SATA SSDs, the ATA 'Secure Erase' command (available through hdparm) is also very fast. I gave up but suspected that connecting it via USB or hotswapping it might fix it. It's not very secure, but practically instant (the disk merely marks all cells as unused). I recall this being a problem a year back when I was trying to securely erase an SSD. When an ATA Secure Erase command is issued against an SSD’s built-in controller (SSD should support ATA Secure Erase), the SSD controller resets all its storage cells as empty, in other words, it restores the SSD to factory default settings and restores SSD performance. I am trying to figure out why -dco-identify is failing and I suspect it may be as a result of the drive being "frozen". ATA Secure Erase will wipe the entire contents of a drive. Relevant thread: Error when running 'hdparm -dco-identify' in Linux My objective is to perform an enhanced secure erase (how? I'll find that out after I know how to unfreeze my drive) and also to detect and remove a Device Configuration Overlay.
0 Comments
Leave a Reply. |