Hdparm Erase Prepare Input Output Error
Contents |
its cells will be marked as empty, restoring it to factory default write performance. DISCLAIMER: This will erase all your data, and will not be recoverable by even hdparm input/output error data recovery services. DISCLAIMER: If you hit kernel or firmware bugs (which are hdparm secure erase plenty with not widely-tested features such as ATA Secure Erase) this procedure might render the drive unusable or crash the computer
Hdparm Enhanced Security Erase
it's running on. DISCLAIMER: 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. Whilst drives directly attached to
Security Unlock Input/output Error
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. They may also decide that locked devices are faulty, and hence not provide any access to them in order to issue unlock commands. Such devices may still be unlocked by connecting them hdparm frozen directly to a different SATA interface. 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. Do not use versions of hdparm prior to 9.31 with such interfaces. 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. 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. I shut down the system, reconnected the drive to the SATA controller, and found that the drive was bricked - BIOS couldn't recognize it. I will update this warning if I find a way to un-brick the drive. (I've had a similar experience - managed to lock myself out of three drives. Read this experience and learn from it - Chris) WARNING: If the SECURITY ERASE fails, use --disable-security to set your drive back to normal. Do not set the password to an empty string or NULL. The Lenovo BIOS at least will not allow you to change the password if it's blank. I
Posts: 3 SSD Secure Erase Fails Hi,After several years of use I thought
Enhanced Secure Erase
the SSD in my Asus EeePC 1000 could benefit hdparm unlock drive from a cell reset as described below:https://wiki.archlinux.org/index.php/SS … l_Clearinghttps://ata.wiki.kernel.org/index.php/ATA_Secure_EraseI ran the following commands secure erase linux using a recent copy of Arch off a USB stick. # hdparm -V hdparm v9.43 # hdparm -iI /dev/sda /dev/sda: Model=ASUS-PHISON SSD, FwRev=TST2.04U, https://ata.wiki.kernel.org/index.php/ATA_Secure_Erase SerialNo=SOQ1881040 Config={ HardSect NotMFM Fixed DTR>10Mbs } RawCHS=15636/16/63, TrkSize=32256, SectSize=512, ECCbytes=4 BuffType=DualPort, BuffSize=1kB, MaxMultSect=1, MultSect=off CurCHS=15636/16/63, CurSects=15761088, LBA=yes, LBAsects=15761088 IORDY=yes, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio1 pio2 pio3 pio4 DMA modes: mdma0 mdma1 mdma2 UDMA modes: udma0 udma1 udma2 udma3 *udma4 AdvancedPM=no Drive conforms to: https://bbs.archlinux.org/viewtopic.php?id=169974 Unspecified: ATA/ATAPI-4,5 * signifies the current active mode CompactFlash ATA device Model Number: ASUS-PHISON SSD Serial Number: SOQ1881040 Firmware Revision: TST2.04U Standards: Supported: 5 4 Likely used: 6 Configuration: Logical max current cylinders 15636 15636 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 15761088 LBA user addressable sectors: 15761088 Logical/Physical Sector size: 512 bytes device size with M = 1024*1024: 7695 MBytes device size with M = 1000*1000: 8069 MBytes (8 GB) cache/buffer size = 1 KBytes (type=DualPort) Capabilities: LBA, IORDY(cannot be disabled) Standby timer values: spec'd by Standard, no device specific minimum R/W multiple sector transfer: Max = 1 Current = 0 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 *udma4 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=120ns IORDY flow control=1
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions http://askubuntu.com/questions/785337/secure-erase-returns-input-output-error/785408 you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and developers. output error Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top secure erase returns input/output error up vote 0 down vote favorite I've already given a detailed description of my predicament in my previous hdparm erase prepare question. Now I've got this: sudo hdparm --user-master u --security-erase my_password /dev/sda returns: security_password: "my_password" /dev/sda: Issuing SECURITY_ERASE command, password="my_password", user=user SECURITY_ERASE: Input/output error What's going on? password secure-erase hdparm share|improve this question edited Jun 13 at 19:45 muru 69.1k12125176 asked Jun 10 at 15:37 m.a.a. 5310 Please don't add "solved" to the title. When you can, just mark the correct answer as accepted. –muru Jun 13 at 19:45 add a comment| 2 Answers 2 active oldest votes up vote 2 down vote accepted FYI: unlocking a Kingston SSD by use of hdparm, after setting a user password appears to be impossible. NOTE: The drive will appear as locked next time you reboot after setting your password. Until then, security will only appear as enabled. Whether trying the very user-password you just set, or other variants, such as "", "NULL", NULL or a row of 32 spaces, either as a user-password or as a master-password, will not unlock your drive, but ins