• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Internal Secure Erase (for SSDs) - why so hard to find?

jrichrds

Platinum Member
Drive wiping software for mechanical drives are everywhere. Why is it internal secure erase tools for SSDs are so hard to find? I only know of PartedMagic and one other old DOS utility that didn't work for me. And on some systems, PartedMagic doesn't start up for one reason or another.

Does anyone know of a Windows utility that does internal secure erase? Or other options that can run off of boot USB or CD?
 
You might try a live linux distro with the program partedmagic uses, its called something like hdparm. If partedmagic is based on ubuntu/debian then I have experienced systems that refuse to boot it but have no problem with redhat based distros like fedora or opensuse. Id have to look at it, there is also HDDErase which you can put on a bootable flashdrive.

Ah, check this out. Ill have to see if there is a redhat livecd that can use hdparm because you may have the same boot problem with the ubuntu livecd.
 
Last edited:
The secure erase function and software that initiates it have been around since before SSDs. I remember Hitachi recommending it prior to selling HDDs. It usually existed outside of Windows in Linux and software that did it within Windows surprised me. Intel, Seagate and Samsung all offer it.

Ultimate Boot CD contains PartedMagic and boots off CD. Knowledge up and understand what you are doing. It could be a recipe for disaster if you don't orient yourself. Best of luck.
 
Just boot off of your favorite Linux distro's LiveCD/DVD, and use "sudo hdparm".

Google for "ATA secure erase Eins", that should bring up the correct procedure.

I prefer to do it myself, rather than rely on a program to do it, because it involves an intermediate step of locking the drive with an ATA password, and if a program does it, you may not know the password to unlock it with, if the procedure gets interrupted for some reason.
 
Back
Top