SKhynix M+B mSATA SSD not recognized

[canebaycomputers]

SKhynix SC300 M.2 2280 512 GB. There is no doubt this is not working. I've tried plugging it into a PCIe adapter card, USB adapter and now a SATA adapter. In the thermal the SH878104AA chip just gets a little warm. I tested all caps for any shorts and see no issues there. No missing components. No corrosion. My only guess is that this is a controller chip and would need to be replaced? I did already order a duplicate SSD that has that same chip. Not sure if that even works? Does it hold TRIM data? Just not sure on this. I realize this is a M+B key mSATA and I have plugged it up properly into the correct adapters that support it. I do run a professional computer and mobile repair shop but I'm limited on advanced data recovery. I don't have much experience and don't have pro tools. Willing to learn and invest. Any help or advice very much appreciated. Thank you in advance.

 

[canebaycomputers]

Plugged it into Linux box with an adapter.

dmesg -w

[   17.043178] usb 1-4: reset high-speed USB device number 3 using xhci_hcd
[16620.840398] usb 2-2: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[16620.865071] usb 2-2: New USB device found, idVendor=152d, idProduct=0578, bcdDevice= 2.09
[16620.865073] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[16620.865075] usb 2-2: Product: USB to ATA/ATAPI Bridge
[16620.865076] usb 2-2: Manufacturer: JMicron
[16620.865077] usb 2-2: SerialNumber: 0123456789ABCDEF
[16620.902951] usbcore: registered new interface driver usb-storage
[16620.931446] scsi host6: uas
[16620.931547] usbcore: registered new interface driver uas
[16620.936057] scsi 6:0:0:0: Direct-Access     JMicron  Generic          0209 PQ: 0 ANSI: 6
[16620.936738] sd 6:0:0:0: Attached scsi generic sg1 type 0
[16630.964379] sd 6:0:0:0: [sda] Spinning up disk...
[16633.979305] ................not responding...
[16745.593556] sd 6:0:0:0: [sda] Read Capacity(16) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[16745.593560] sd 6:0:0:0: [sda] Sense Key : Not Ready [current]
[16745.593562] sd 6:0:0:0: [sda] Add. Sense: Logical unit is in process of becoming ready
[16751.610568] sd 6:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[16751.610571] sd 6:0:0:0: [sda] Sense Key : Not Ready [current]
[16751.610572] sd 6:0:0:0: [sda] Add. Sense: Logical unit is in process of becoming ready
[16751.611116] sd 6:0:0:0: [sda] 0 512-byte logical blocks: (0 B/0 B)
[16751.611118] sd 6:0:0:0: [sda] 0-byte physical blocks
[16757.627581] sd 6:0:0:0: [sda] Test WP failed, assume Write Enabled
[16759.633255] sd 6:0:0:0: [sda] Asking for cache data failed
[16759.633260] sd 6:0:0:0: [sda] Assuming drive cache: write through
[16765.650276] sd 6:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of physical block size (0 bytes)
[16773.729941] sd 6:0:0:0: [sda] Spinning up disk...
[16776.759487] ...........not responding...
[16849.774730] sd 6:0:0:0: [sda] Read Capacity(16) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[16849.774733] sd 6:0:0:0: [sda] Sense Key : Hardware Error [current]
[16849.774735] sd 6:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81
[16849.775621] sd 6:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[16849.775624] sd 6:0:0:0: [sda] Sense Key : Hardware Error [current]
[16849.775626] sd 6:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81
[16849.778180] sd 6:0:0:0: [sda] Attached SCSI disk

 

[lcoughey]

Controller is not supported by PC3000 for firmware fixes. Linux is only talking to the Jmicron controller in the USB bridge being used.

Probably best to send out to a data recovery professional with tools and experience to handle it, if it is even recoverable at all.

 

[jimmy5]

did it get warm when it was in the adapter or you added some voltage somewhere and which ones are the caps to test on a ssd?
does pc3k support those samsung evo and pro disks or which tools should be used to run some hardware tests on it without any harm for the data?

 

[bflcafe]

It sounds like you’ve taken a systematic approach to troubleshoot your SKhynix SC300, and you’ve already ruled out many potential causes. Let’s break this down and see if we can uncover next steps or solutions to help recover the drive—or at least salvage the data.

---

What We Know About the Problem​

1. No Response Across Multiple Adapters: You’ve tried connecting the SSD through PCIe, USB, and SATA adapters with no success. This eliminates the possibility of a single faulty adapter or compatibility mismatch.
2. Thermal Activity on the Controller: The SH878104AA chip warming up suggests it’s receiving power, but this doesn’t confirm that the chip is functioning correctly. If the drive is not recognized, the controller is a prime suspect.
3. No Shorts, Missing Components, or Corrosion: It’s good that the PCB appears physically intact and shows no signs of catastrophic damage. However, microdamage, firmware corruption, or internal NAND issues could still be in play.
4. You Ordered a Duplicate SSD: Swapping components between a working and non-working SSD can be effective in certain scenarios, but this depends on the architecture of the drive. Many modern SSDs store unique firmware, TRIM data, or encryption keys that tie the NAND chips to the original controller. This complicates board or chip swaps.