Phison mSATA RAID 0 SSD (SSE256GTTCR-S80)

[lcoughey]

I haven't seen RAID 0 SSD for quite some time and all that I did see were ZIF/LIF connections. This time around, I've got an mSATA dual 128GB (total 256GB) SSD. I'm kind of hoping to save some time and my client some money by hoping that someone here has already laid out the ground work and can confirm the correct pinout for the secondary SATA line.

Channel 0 (based on mSATA standard layouts)
33 - C1 = TX+
31 - C2 = TX-
25 - C3 = RX-
23 - C4 = RX+

Channel 1 (this is where I'm not sure)
following numerical order from channel 0
5 - C5 = TX+
3 - C6 = TX-
13 - C7 = RX-
11 - C8 = RX+

or following positional order from above
13 - C7 = TX+
11 - C8 = TX-
5 - C5 = RX-
3 - C6 = RX+

or is it completely different? I've already got an image of channel 0 and plan to block 23, 25, 31 & 33 and run bypass wires for 3, 5, 11 & 13 once I know the correct pinout. Any suggestions?

[lcoughey]

Got it figured out.

So, the layout is as follows:

51 [------------------]17,15[--------] 1

Channel 0 [33 (TX+), 31 (TX-), 25 (RX-), 23 (RX+)] Channel 1 [13 (RX+), 11 (RX-), 5 (TX-), 3 (TX+)]

[lcoughey]

Now that we have a tried and tested solution, we have added the service to our website.

https://www.recoveryforce.com/msata-int ... -recovery/

[lcoughey]

It is nice when the research of the past helps pave the way for future cases. Just did one today, this time the brand was a Kingston SMSR150S3/128G which turns out to be 2 x 64GB SSDs setup in a RAID 0.

Mirrored one half with a standard mSATA adapter, mirrored the other half with my modified mSATA adapter and then virtually reconstructed the RAID 0 and saved the targeted files.

[lcoughey]

Here is a link to a thread on hddguru for a different model of this drive showing possible short points for each controller to get into safe mode.

https://forum.hddguru.com/viewtopic.php?f=10&t=42059

[webclaw]

Just a quick note -

For our case (SMSR150S3/128GB) the only loader version that would find the L2P tables was 7.2.
The default selection w/PC3000 is 3.8.

Oddly enough 3.8 finds FW assets and correctly ID’s the chips.