Hdparm secure erase
- HDPARM SECURE ERASE HOW TO
- HDPARM SECURE ERASE CODE
- HDPARM SECURE ERASE PASSWORD
- HDPARM SECURE ERASE PLUS
I was actually trying to run hdparm secure erase on an SSD, it wasn’t accepting the hdparm commands at all so i tested the commands on my WD Drive in the same SATA bay.
HDPARM SECURE ERASE PLUS
Here is the log file from what I did in Parted Magic plus some additional comments from me.
HDPARM SECURE ERASE CODE
Test Option:Ġ6-Quick Test on drive 2 did not complete! Status code = 07 (Failed read test element), Failure Checkpoint = 102 (Unknown Test) SMART self-test did not complete on drive 2! I think the interrupted hdparm secure erase + power outage may have caused corrupted drive firmware.įinally here is the Data Lifeguard Test Summary when the drive is connected to the SATA port on the PC. Not so concerned about recovering the data on the drive. My aim is to get the drive working again. Any support / advice would be appreciated. So in Summary - it looks like the Parted Magic Linux hdparm secure erase attempt which was cut short due to a power outage has hosed my drive. Test Error Code: 20- Delete Partitions error! Test Error Code: 08-Too many bad sectors detected. Last edited by SteveT 22nd August 2021 at 10:13 AM.Finally I ran the Data Lifeguard Disk Checks. hdparm -I shows the device as unlocked and gnome-disk-utility can now format the drive. The two commands ( with params -security-unlock and -security-disable) now seem to do the trick - and the change sticks after a re-power of the drive. Sudo hdparm -security-disable "xxxx" /dev/ Sudo hdparm -security-unlock "xxxx" /dev/ '.Also for those looking for the commands to use to unlock a drive bricked by this. Obviously something else is at play.Ī bit further down the page at, below advatens post, WizardTim writes: Also, if the drive is powered down and restarted, hdparm shows it as locked again. The command works and hdparm -I shows the drive now as unlocked, but gnome-disk-utility won't format the drive still and gparted doesn't see it. Sudo hdparm -security-unlock xxxx /dev/sdbĬommand works and unlocks the drive - spoke too early.
HDPARM SECURE ERASE PASSWORD
Password used in ATA Enhanced Security Erase: xxxx. After some months with the HDD locked, everything good now. Searching the udisks source code I found the password at storaged-project/udisks:src/udiskslinuxdriveata.c#L1895. '.Found it! I didn't pay attention before to the fact the Gnome Disk Utility is a graphical front-end for udisks. the answer is provided by user advatens a few lines down on that page where he says: This has happened to others - as this shows: OK - found the solution - ie what password the gnome-disk-utility uses to perform the ATA enhanced secure erase. PS gparted and dd don't appear to work - gparted doesn't see the drive and a dd to write zeros to the drive just runs forever - gnome-disk-utility still sees the drive though - but fails whenever I try to use that to format it.
HDPARM SECURE ERASE HOW TO
Does anyone know how to unlock it (I can see an option with hdparm) or how to know what password was used? I don't recall being asked for a password at all when using the ATA Secure option - so presumably it defaults.
![hdparm secure erase hdparm secure erase](https://linuxhint.com/wp-content/uploads/2021/06/35.png)
Logical Unit WWN Device Identifier: 50014ee1010df536 * SMART Command Transport (SCT) feature setĤ2min for SECURITY ERASE UNIT. *ĝevice Configuration Overlay feature set * SET_FEATURES required to spinup after power upĪutomatic Acoustic Management feature set Recommended acoustic management value: 128, current value: 254ĭMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6Ĭycle time: no flow control=120ns IORDY flow control=120ns R/W multiple sector transfer: Max = 16Ĝurrent = 0 Standby timer values: spec'd by Standard, with device specific minimum Transport: Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5ĬHS current addressable sectors: 16514064
![hdparm secure erase hdparm secure erase](https://dhzhd1.files.wordpress.com/2016/08/2.png)
That seems to show me (if I'm reading it right), that the drives is locked - hdparm -I /dev/sdb shows: But now I can't access that disk at all - apart from using hdparm. I removed 4x160GB drives from a very old server and wanted to clear the data on them, so I used gnome-disk-utility to clear the drives and in one case 'stupidly' used the ATA Secure Erase without reading how/what it was (as it was the fastest option).