are my drives e-waste?

[smoosh]

I recently recovered two Intel SSDs from an e-waste bin. I don't care about the data on them, but I think it would be nice if I could store data on them (keeping them out of the e-waste stream for a few more years)

- They are "Intel SSD Pro 1500" models
- The spec sheet for them is here: https://www.intel.com/content/dam/www/p ... cation.pdf
- The spec sheet says they "support the TCG Opal SSC Specification Version 1.0 Rev 3.0 mandatory commands"
- The spec sheet says they support "PSID (Physical presence Security ID) Revert for SSD Repurposing"
- They have 32 character PSIDs printed on their labels that I can clearly read

Code:

# hdparm -V
hdparm v9.65

# hdparm -I /dev/sda

/dev/sda:

ATA device, with non-removable media
        Model Number:       INTEL SSDSC2BF240A4L                   
        Serial Number:       [REDACTED] 
        Firmware Revision:  LS2i   
        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 0xffff)
        Supported: 9 8 7 6 5
        Likely used: 9
Configuration:
        Logical         max     current
        cylinders       16383   16383
        heads           16      16
        sectors/track   63      63
        --
        CHS current addressable sectors:    16514064
        LBA    user addressable sectors:   268435455
        LBA48  user addressable sectors:   468862128
        Logical  Sector size:                   512 bytes
        Physical Sector size:                  4096 bytes
        Logical Sector-0 offset:                  0 bytes
        device size with M = 1024*1024:      228936 MBytes
        device size with M = 1000*1000:      240057 MBytes (240 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, no device specific minimum
        R/W multiple sector transfer: Max = 16  Current = 16
        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
           *    WRITE_BUFFER command
           *    READ_BUFFER command
           *    NOP cmd
           *    DOWNLOAD_MICROCODE
           *    Advanced Power Management feature set
           *    48-bit Address feature set
           *    Mandatory FLUSH_CACHE
           *    FLUSH_CACHE_EXT
           *    SMART error logging
           *    SMART self-test
           *    General Purpose Logging feature set
           *    64-bit World wide name
           *    WRITE_UNCORRECTABLE_EXT command
           *    {READ,WRITE}_DMA_EXT_GPL commands
           *    Segmented DOWNLOAD_MICROCODE
           *    Gen1 signaling speed (1.5Gb/s)
           *    Gen2 signaling speed (3.0Gb/s)
           *    Gen3 signaling speed (6.0Gb/s)
           *    Native Command Queueing (NCQ)
           *    Host-initiated interface power management
           *    Phy event counters
           *    DMA Setup Auto-Activate optimization
                Device-initiated interface power management
           *    Software settings preservation
                Device Sleep (DEVSLP)
                unknown 78[10]
           *    SMART Command Transport (SCT) feature set
           *    SCT Write Same (AC2)
           *    SCT Data Tables (AC5)
           *    Device encrypts all user data
           *    Data Set Management TRIM supported (limit 1 block)
           *    Deterministic read data after TRIM
Security:
        Master password revision code = 16385
                supported
                enabled
                locked
        not     frozen
        not     expired: security count
                supported: enhanced erase
        Security level high
        4min for SECURITY ERASE UNIT. 2min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: [REDACTED]
        NAA             : 5
        IEEE OUI        : [REDACTED]
        Unique ID       : [REDACTED]
Device Sleep:
        DEVSLP Exit Timeout (DETO): 20 ms (drive)
        Minimum DEVSLP Assertion Time (MDAT): 10 ms (drive)
Checksum: correct


It seems like any standard read/writes to them fail. I assume that's because they're locked/encrypted (or whatever).

I've tried to reset/disable the ATA password like this without luck:

Code:

# hdparm --user-master m --security-disable PWD /dev/sda
security_password: "PWD"

/dev/sda:
Issuing SECURITY_DISABLE command, password="PWD", user=master
SG_IO: bad/missing sense data, sb[]:  70 00 05 00 00 00 00 0a 04 51 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
SG_IO: bad/missing sense data, sb[]:  70 00 05 00 00 00 00 0a 04 51 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
# hdparm --user-master u --security-disable PWD /dev/sda
security_password: "PWD"

/dev/sda:
Issuing SECURITY_DISABLE command, password="PWD", user=user
SG_IO: bad/missing sense data, sb[]:  70 00 05 00 00 00 00 0a 04 51 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
SG_IO: bad/missing sense data, sb[]:  70 00 05 00 00 00 00 0a 04 51 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00


sedutil-cli can't/won't do a PSID revert (I've tried) because it thinks the drive isn't Opal compliant:

Code:

# sedutil-cli --scan
Scanning for Opal compliant disks
/dev/sda   No  INTEL SSDSC2BF240A4L                     LS2i

# sedutil-cli --query /dev/sda
Invalid or unsupported disk /dev/sda


1) Is PSID revert blocked by a locked ATA password?
2) or could there be some other reason that's not working?
3) Is there _anything_ I can do to make these drives usable again if I can't ask the previous owner for the password(s) they've put on them?

Thanks in advance for any help anyone can offer!

[sourcerer]

I would suggest to try the security erase commands provided in this article:
https://grok.lsu.edu/article.aspx?articleid=16716

[smoosh]

I would suggest to try the security erase commands provided in this article:
https://grok.lsu.edu/article.aspx?articleid=16716

I've seen that article. My drive starts in a different state to the one there (mine's locked, theirs isn't). I can follow their steps alright until step 7. When I do step 7:

# hdparm --user-master u --security-set-pass p /dev/sdb

security_password: "p"

/dev/sdb:
Issuing SECURITY_SET_PASS command, password="p", user=user, mode=high
SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 51 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Then step 9 fails similarly

The key difference between what I have and what's going on in that page is that they have

Code:

not locked

whereas I have

Code:

locked

Is there really no way I can unbrick these drives? Of course I can understand the data not being recoverable if I don't have the unlock password, but are they really actually unusable trash now?

[fzabkar]

Have you tried Intel's tool?

https://www.intel.com/content/dam/support/us/en/documents/solid-state-drives/Intel_SSD_ProAdminTool_UserGuide.pdf