Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

33kb 200026BB? Recovery sandforce help.

FancyPants101
 Share

I have some old sandforce drives. I'm trying to recover them. I have power cycled them and one of them at least shows up in general as 33kb 200026BB if I'm not mistaken.

 

In gnome disk utility its:

33kb Disk Drive

Sandforce{200026BB}

Model: Sandforce{200026BB} (402ABBR0)

Size: 33kb (32,768 bytes)

Serial number: 1

 

Size: 33kb (32,768 byte)

Device/dev/sdf

Contents: unknown.

 

I'm on fedora 28 btw.

 

I'm not concerned about data recovery(infact I will ultimately destroy the data more than likely). I'm just trying to see if I missed a way to recover the disk on any level. I've tried using gnome disk utility to wipe the partition and other things and it is limited. I've tried using mushkin field updater or the firmware software and even in administrator/sudo it does not detect the drive. I think Gparted doesn't detect it, but KDEparted does but can't do anything useful to it as far as I can tell. Is there anything I'm missing. Any way to manually change the drive in order to make it work or make it make itself work. I've read stuff about the trash collection needing to be triggered from trim not working and the drive filling and other things. I would love to get this working again.

 

Gnome disk utiilty can currently attempt to:

Spoiler

Eject the disk(gives error)

Format Disk

Create Disk image

Restore Disk image

Benchmark Disk

Drive settings(only write caching)

 

Format Partition

Create partition image

Restore partition image

Benchmark partition

 

New Disk Image

Attach Disk Image

Help

About

Quit

 

The other drive is not detected at all so far. But I'm not giving up hope if possible. I'm hoping I missed things in the past to get the drive(s) working again.

 

sudo hdparm -I /dev/sdf

/dev/sdf:

ATA device, with non-removable media
        Model Number:       SandForce{200026BB}                     
        Serial Number:      1                   
        Firmware Revision:  402ABBR0
        Transport:          Serial; Revision: 0x0002
Standards:
        Used: unknown (minor revision code 0x0029) 
        Supported: 8 7 6 5 
        Likely used: 8
Configuration:
        Logical         max     current
        cylinders       0       0
        heads           16      16
        sectors/track   63      63
        --
        CHS current addressable sectors:           0
        LBA    user addressable sectors:          64
        LBA48  user addressable sectors:          64
        Logical  Sector size:                   512 bytes
        Physical Sector size:                  4096 bytes
        Logical Sector-0 offset:                  0 bytes
        device size with M = 1024*1024:           0 MBytes
        device size with M = 1000*1000:           0 MBytes 
        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 = ?
        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:
           *    Power Management feature set
           *    Write cache
                Look-ahead
           *    WRITE_BUFFER command
           *    READ_BUFFER command
           *    DOWNLOAD_MICROCODE
                SET_MAX security extension
           *    48-bit Address feature set
           *    Mandatory FLUSH_CACHE
           *    FLUSH_CACHE_EXT
           *    General Purpose Logging feature set
           *    64-bit World wide name
           *    Gen1 signaling speed (1.5Gb/s)
           *    Gen2 signaling speed (3.0Gb/s)
           *    Native Command Queueing (NCQ)
           *    Host-initiated interface power management
           *    DMA Setup Auto-Activate optimization
           *    Software settings preservation
Logical Unit WWN Device Identifier: 500232d000000001
        NAA             : 5
        IEEE OUI        : 00232d
        Unique ID       : 000000001
Checksum: correct
Spoiler

$ sudo hdparm --dco-identify /dev/sdf

/dev/sdf:
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
DCO Checksum verified.
DCO Revision: 0x0000 -- unknown, treating as 0002
The following features can be selectively disabled via DCO:
        Transfer modes:

        Real max sectors: 1
        ATA command/feature sets:

 

Any odd this would do any good?

Spoiler

--dco-restore

sudo hdparm --yes-i-know-what-i-am-doing --dco-restore /dev/sdf

/dev/sdf:
 issuing DCO restore command
SG_IO: bad/missing sense data, sb[]:  70 00 05 00 00 00 00 0a 04 51 40 00 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

https://bbs.archlinux.org/viewtopic.php?id=221957

 

Would the 

--security-disable NULL

work?

Spoiler

$ sudo hdparm --security-disable NULL /dev/sdf
security_password: ""

/dev/sdf:
 Issuing SECURITY_DISABLE command, password="", 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

http://rabexc.org/posts/recovering-from-failed-ssd

Spoiler

$ sudo hdparm --user-master u --security-set-pass "" /dev/sdf
security_password: ""

/dev/sdf:
 Issuing SECURITY_SET_PASS command, password="", 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

Spoiler

sudo smartctl -a /dev/sdf
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.19.2-200.fc28.x86_64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     SandForce{200026BB}
Serial Number:    1
LU WWN Device Id: 5 00232d 000000001
Firmware Version: 402ABBR0
User Capacity:    32,768 bytes [32.7 KB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    Solid State Device
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 2.6, 3.0 Gb/s
Local Time is:    Tue Nov 27 02:09:22 2018 EST
SMART support is: Unavailable - device lacks SMART capability.

A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

http://www.overclockers.com/forums/archive/index.php/t-693716.html

Spoiler

$ sudo hdparm --user-master u --security-unlock "" /dev/sdf
security_password: ""

/dev/sdf:
 Issuing SECURITY_UNLOCK command, password="", 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

I'm not really knowledgable about this stuff. Does anyone understand what the disk is having problems with? Or how to fix it? I'm assuming it's not actually dead.

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share


×