A
A
Alexander2015-11-24 11:02:43
linux
Alexander, 2015-11-24 11:02:43

Why can't I set a password (hangs) on the SSD using sudo hdparm --user-master u --security-set-pass?

I got a buggy 400Gb Intel SSD DC S3700, I want to restore it.
shows a volume of 8 MB
command sudo hdparm -I /dev/sdd issues

[email protected]:~$ sudo hdparm -I /dev/sdd
/dev/sdd:

ATA device, with non-removable media
  Model Number:       Intel Taylorsville                      
  Serial Number:      *XASSERT_120      MC
  Firmware Revision:  5DV10250
  Media Serial Num:   
  Media Manufacturer: 
  Transport:          Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6
Standards:
  Used: unknown (minor revision code 0x0029) 
  Supported: 8 7 6 5 
  Likely used: 8
Configuration:
  Logical		max	current
  cylinders	16383	16
  heads		16	16
  sectors/track	63	63
  --
  CHS current addressable sectors:      16128
  LBA    user addressable sectors:      16384
  LBA48  user addressable sectors:      16384
  Logical  Sector size:                   512 bytes
  Physical Sector size:                   512 bytes
  Logical Sector-0 offset:                  0 bytes
  device size with M = 1024*1024:           8 MBytes
  device size with M = 1000*1000:           8 MBytes 
  cache/buffer size  = unknown
  Form Factor: 2.5 inch
  Nominal Media Rotation Rate: Solid State Device
Capabilities:
  LBA, IORDY(can be disabled)
  Queue depth: 32
  Standby timer values: spec'd by Standard, no device specific minimum
  R/W multiple sector transfer: Max = 1	Current = 1
  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
      	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_UNCORRECTABLE_EXT command
     *	{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
     *	READ_LOG_DMA_EXT equivalent to READ_LOG_EXT
     *	Software settings preservation
     *	SMART Command Transport (SCT) feature set
     *	SCT Write Same (AC2)
     *	SCT Error Recovery Control (AC3)
     *	SCT Features Control (AC4)
     *	SCT Data Tables (AC5)
     *	Data Set Management TRIM supported (limit 6 blocks)
     *	Deterministic read ZEROs after TRIM
Security: 
  Master password revision code = 65534
    supported
  not	enabled
  not	locked
  not	frozen
  not	expired: security count
    supported: enhanced erase
  2min for SECURITY ERASE UNIT. 2min for ENHANCED SECURITY ERASE UNIT. 
Logical Unit WWN Device Identifier: 0000000000000000
  NAA		: 0
  IEEE OUI	: 000000
  Unique ID	: 000000000
Checksum: correct

when you try to set a user password on it sudo hdparm --user-master u --security-set-pass qwerty /dev/sdd
thinks and issues for 5 minutes
sudo hdparm --user-master u --security-set-pass qwerty /dev/sdd
security_password="qwerty"

/dev/sdd:
 Issuing SECURITY_SET_PASS command, password="qwerty", user=user, mode=high

Now if you try to check again sudo hdparm -I /dev/sdd - the terminal freezes
after a reboot, the password is still not set
sudo hdparm -I /dev/sdd -> gives out
not locked
not frozen
What can be done with it? What do you think?
I would like to restore a 400GB disk

Answer the question

In order to leave comments, you need to log in

1 answer(s)
C
Cole, 2015-11-24
@Cole

Why-why...
Here is the answer :)
Perhaps the memory is covered in it, and maybe the controller. This cannot be determined at home.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question