SSD Troubles with initializing the device

[MinTech]

I have a Samsung 850 Pro 256GB that won’t connect to my computer. I’ve tried all the usual stuff, swapping computers, SATA cables, PSUs etc. What it boils down to is that the drive won’t initialize or mount.

I daily drive windows, but spooled up a Linux laptop with a USB to SATA adapter to test.

typing in

sudo tail -f /var/log/messages

results in this:

May 11 01:18:24 localhost kernel: [ 2396.027555] usb 2-1: new SuperSpeed Gen 1 USB device number 10 using xhci_hcd
May 11 01:18:24 localhost kernel: [ 2396.048252] usb 2-1: New USB device found, idVendor=174c, idProduct=55aa, bcdDevice= 1.00
May 11 01:18:24 localhost kernel: [ 2396.048256] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
May 11 01:18:24 localhost kernel: [ 2396.048257] usb 2-1: Product: ASM105x
May 11 01:18:24 localhost kernel: [ 2396.048259] usb 2-1: Manufacturer: ASMT
May 11 01:18:24 localhost kernel: [ 2396.048260] usb 2-1: SerialNumber: 1234567891874
May 11 01:18:24 localhost kernel: [ 2396.051687] scsi host5: uas
May 11 01:18:24 localhost kernel: [ 2396.054548] scsi 5:0:0:0: Direct-Access     ASMT     ASM105x          0    PQ: 0 ANSI: 6
May 11 01:18:24 localhost kernel: [ 2396.055139] scsi 5:0:0:0: Attached scsi generic sg2 type 0
May 11 01:18:24 localhost kernel: [ 2396.055433] sd 5:0:0:0: [sdc] Spinning up disk...
May 11 01:18:24 localhost mtp-probe: checking bus 2, device 10: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
May 11 01:18:24 localhost mtp-probe: bus: 2, device: 10 was not an MTP device
May 11 01:18:24 localhost mtp-probe: checking bus 2, device 10: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
May 11 01:18:24 localhost mtp-probe: bus: 2, device: 10 was not an MTP device
May 11 01:20:04 localhost kernel: [ 2397.079557] ..................................................................................................not responding...
May 11 01:20:25 localhost kernel: [ 2517.226942] sd 5:0:0:0: [sdc] Read Capacity(16) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
May 11 01:20:25 localhost kernel: [ 2517.226946] sd 5:0:0:0: [sdc] Sense Key : Not Ready [current] 
May 11 01:20:25 localhost kernel: [ 2517.226949] sd 5:0:0:0: [sdc] Add. Sense: Logical unit is in process of becoming ready
May 11 01:20:46 localhost kernel: [ 2538.076264] sd 5:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
May 11 01:20:46 localhost kernel: [ 2538.076270] sd 5:0:0:0: [sdc] Sense Key : Not Ready [current] 
May 11 01:20:46 localhost kernel: [ 2538.076273] sd 5:0:0:0: [sdc] Add. Sense: Logical unit is in process of becoming ready
May 11 01:20:46 localhost kernel: [ 2538.076580] sd 5:0:0:0: [sdc] 0 512-byte logical blocks: (0 B/0 B)
May 11 01:20:46 localhost kernel: [ 2538.076583] sd 5:0:0:0: [sdc] 0-byte physical blocks
May 11 01:21:07 localhost kernel: [ 2558.925626] sd 5:0:0:0: [sdc] Test WP failed, assume Write Enabled
May 11 01:21:14 localhost kernel: [ 2565.877514] sd 5:0:0:0: [sdc] Optimal transfer size 33553920 bytes not a multiple of physical block size (0 bytes)
May 11 01:21:14 localhost kernel: [ 2565.892150] sd 5:0:0:0: [sdc] Spinning up disk...
May 11 01:22:54 localhost kernel: [ 2566.903514] ............................................................................................not responding...
May 11 01:23:15 localhost kernel: [ 2686.821282] sd 5:0:0:0: [sdc] Read Capacity(16) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
May 11 01:23:15 localhost kernel: [ 2686.821287] sd 5:0:0:0: [sdc] Sense Key : Not Ready [current] 
May 11 01:23:15 localhost kernel: [ 2686.821289] sd 5:0:0:0: [sdc] Add. Sense: Logical unit is in process of becoming ready
May 11 01:23:35 localhost kernel: [ 2707.670597] sd 5:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
May 11 01:23:35 localhost kernel: [ 2707.670603] sd 5:0:0:0: [sdc] Sense Key : Not Ready [current] 
May 11 01:23:35 localhost kernel: [ 2707.670606] sd 5:0:0:0: [sdc] Add. Sense: Logical unit is in process of becoming ready
May 11 01:24:03 localhost kernel: [ 2735.469766] sd 5:0:0:0: [sdc] Attached SCSI disk

It won’t initialize, mount, or boot, and upon botting up a machine with it attached directly via SATA, it confuses the heck out of the BIOS.

Is there anything I can do to get this drive online enough to get my data off of it?

Thanks in advance,
MinTech

[hp185688]

That is interesting. All I’ve found so far is: https://docs.oracle.com/cd/E19105-01/storedge.6320/817-5918-10/817-5918-10.pdf

Which is neither here, nor there. I’ll see what else I find.

[hp185688]

I’m not seeing much else on that error code.

You could call the manufacturer. They might have their own tools to diagnose it. I just went through this with Intel, because of an esoteric lock on a drive I have which was implemented by bios when it shouldn’t have.