MultiDrive – free backup, clone & wipe disk utility from Atola Technology

All times are UTC - 5 hours [ DST ]


Switch to mobile style


Post new topic Reply to topic  [ 2 posts ] 
Author Message
 Post subject: SSD bricked after secure erase?
PostPosted: August 2nd, 2015, 6:49 
Offline

Joined: August 2nd, 2015, 5:52
Posts: 1
Location: Poland
Hello everyone (sorry for my english).
Yesterday i decided to erase my KingstonSSDNow v300.
I found this link: https://ata.wiki.kernel.org/index.php/ATA_Secure_Erase
I was using Ubuntu 14.04.1 botted on Sony VAIO sve 1511g1esi.
Steps i made:
1.first, i checked if disk is locked/frozen. Everything was ok so i go to the next step,
2.
Code:
hdparm --user-master u --security-set-pass Eins /dev/sda
this command did not return any errors, it looked like the password "Eins" was set properly,
3.
Code:
time hdparm --user-master u --security-erase Eins /dev/sda

And finally i stuck here, because this command returned:
Code:
/dev/sda:
Issuing SECURITY_ERASE command, password="Eins", user=user
ERASE_PREPARE: Input/output error

At the moment, commands with --security-* don't work, everytime i get I/O errors.
I don't need data from ssd because i made backup.
Information from hdparm -I /dev/sda:
Code:
/dev/sda:

ATA device, with non-removable media
   Model Number:       KINGSTON SV300S37A120G                 
   Serial Number:      50026B774608D51F   
   Firmware Revision:  527ABBF0
   Transport:          Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0
Standards:
   Used: unknown (minor revision code 0x0110)
   Supported: 8 7 6 5
   Likely used: 8
Configuration:
   Logical      max   current
   cylinders   16383   16383
   heads      16   16
   sectors/track   63   63
   --
   CHS current addressable sectors:   16514064
   LBA    user addressable sectors:  234441648
   LBA48  user addressable sectors:  234441648
   Logical  Sector size:                   512 bytes
   Physical Sector size:                   512 bytes
   Logical Sector-0 offset:                  0 bytes
   device size with M = 1024*1024:      114473 MBytes
   device size with M = 1000*1000:      120034 MBytes (120 GB)
   cache/buffer size  = unknown
   Nominal Media Rotation Rate: Solid State Device
Capabilities:
   LBA, IORDY(can be disabled)
   Queue depth: 32
   Standby timer values: spec'd by Standard, with device specific minimum
   R/W multiple sector transfer: Max = 16   Current = 1
   Advanced power management level: 254
   DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
        Cycle time: min=120ns recommended=120ns
   PIO: pio0 pio1 pio2 pio3 pio4
        Cycle time: no flow control=120ns  IORDY flow control=120ns
Commands/features:
   Enabled   Supported:
      *   SMART feature set
      *   Security Mode feature set
      *   Power Management feature set
      *   Write cache
          Look-ahead
      *   Host Protected Area feature set
      *   WRITE_BUFFER command
      *   READ_BUFFER command
      *   NOP cmd
      *   DOWNLOAD_MICROCODE
      *   Advanced Power Management feature set
          Power-Up In Standby feature set
      *   SET_FEATURES required to spinup after power up
          SET_MAX security extension
      *   48-bit Address feature set
      *   Mandatory FLUSH_CACHE
      *   FLUSH_CACHE_EXT
      *   SMART error logging
      *   SMART self-test
      *   General Purpose Logging feature set
      *   WRITE_{DMA|MULTIPLE}_FUA_EXT
      *   64-bit World wide name
      *   IDLE_IMMEDIATE with UNLOAD
          Write-Read-Verify feature set
      *   {READ,WRITE}_DMA_EXT_GPL commands
      *   Segmented DOWNLOAD_MICROCODE
          unknown 119[6]
      *   Gen1 signaling speed (1.5Gb/s)
      *   Gen2 signaling speed (3.0Gb/s)
      *   Gen3 signaling speed (6.0Gb/s)
      *   Native Command Queueing (NCQ)
      *   Phy event counters
      *   NCQ priority information
      *   READ_LOG_DMA_EXT equivalent to READ_LOG_EXT
      *   DMA Setup Auto-Activate optimization
          Device-initiated interface power management
      *   Software settings preservation
      *   SMART Command Transport (SCT) feature set
      *   SCT Write Same (AC2)
      *   SCT Data Tables (AC5)
      *   reserved 69[3]
      *   DOWNLOAD MICROCODE DMA command
      *   SET MAX SETPASSWORD/UNLOCK DMA commands
      *   WRITE BUFFER DMA command
      *   READ BUFFER DMA command
      *   Data Set Management TRIM supported (limit 1 block)
Security:
   Master password revision code = 65534
      supported
      enabled
      locked
   not   frozen
      expired: security count
      supported: enhanced erase
   Security level high
   2min for SECURITY ERASE UNIT. 2min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 50026b774608d51f
   NAA      : 5
   IEEE OUI   : 0026b7
   Unique ID   : 74608d51f
Checksum: correct

Any suggestions?


Top
 Profile  
 
 Post subject: Re: SSD bricked after secure erase?
PostPosted: December 26th, 2015, 13:34 
Offline

Joined: December 26th, 2015, 13:13
Posts: 2
Location: United Kingdom
Have you had any luck? I am in the same state :( .....
Your drive is in Locked stated and Encrypted, if you remember your password or master password then only you can unlock it.
Anyone know how to crypto erase a drive without PSID as my drive is an enterprise Samsung SSD SM843T with No PSID on the label?


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 2 posts ] 

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 52 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group