3 Step 3 - Issue the ATA Secure Erase command:.2.2.1 Step 2b - Command Output (should display "enabled"):.2.2 Step 2b - Make sure it succeeded, execute:.2 Step 2 - Enable security by setting a user password:.1.1 Step 1a - Ensure the drive is not frozen:.1 Step 1 - Make sure the drive Security is not frozen:.It was run from an Ubuntu 9.04 32-bit (Jaunty) Live CD booted from a USB flash drive. The example output shown is from an INTEL X25-M G1 80GB SSD running 8820 firmware. This step is omitted from almost all other sources which describe how to secure erase with hdparm. To successfully issue an ATA Security Erase command you need to first set a user password. Note: My hdparm program has an option -security-disable PWD. I finally found a board with a Phoenix TrustedCore BIOS which does allow clearing an empty password - Chris. I'm now stuck with three drives that are passworded and I cannot unpassword. It also freezes the drive so that you can't change the password later, after booting into an OS. The Lenovo BIOS at least will not allow you to change the password if it's blank. Do not set the password to an empty string or NULL. WARNING: If the SECURITY ERASE fails, use -disable-security to set your drive back to normal. Read this experience and learn from it - Chris) (I've had a similar experience - managed to lock myself out of three drives. I will update this warning if I find a way to un-brick the drive. I shut down the system, reconnected the drive to the SATA controller, and found that the drive was bricked - BIOS couldn't recognize it. When I tried it again later on the same drive through a USB adapter, it let me password protect the drive, but would not accept the SECURITY-ERASE command. WARNING: Do not attempt to do this through a USB interface! This procedure worked fine when I tried it on my X-25M through the SATA interface. Do not use versions of hdparm prior to 9.31 with such interfaces. Additionally, hdparm versions prior to 9.31 do not pass-through the long command time-outs required for the erase commands to the SCSI-ATA Command Translation ("SAT") layer which such devices use. Such devices may still be unlocked by connecting them directly to a different SATA interface. They may also decide that locked devices are faulty, and hence not provide any access to them in order to issue unlock commands. Whilst drives directly attached to a straight-forward SATA controller should work reliably, some "intelligent" interfaces such as USB or firewire to PATA/SATA bridges, SAS controllers or hardware RAID controllers may try to reset devices which they have decided are no longer responding. When a Secure Erase is issued against a SSD drive all its cells will be marked as empty, restoring it to factory default write performance.ĭISCLAIMER: This will erase all your data, and will not be recoverable by even data recovery services.ĭISCLAIMER: If you hit kernel or firmware bugs (which are plenty with not widely-tested features such as ATA Secure Erase) this procedure might render the drive unusable or crash the computer it's running on.ĭISCLAIMER: The security-erase command is a single command which typically takes minutes or hours to complete, whereas most ATA commands take milliseconds, or seconds to complete. This procedure describes how to use the hdparm command to issue a Secure Erase ATA instruction to a target storage device.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |