Hi,
Received a C400 256 GB SSD with the following symptoms.
In Windows:
- Not detected as storage by Windows (and was blocking Windows from starting).
- Invisible from the disk manager, wether connected in eSATA or USB 3.0.
In Linux:
- detected by lsblk, but was very unstable and disappeared after a few seconds
- undetected by fdisk -l
- ddrescue was failing as trying to clone Petabytes
I made this :
- pressed on all pins of the SATA (data+power) connector 350° with the soldering iron to melt the solder if any microcrack(s)
- preheated the circuit board with hot air and applied hot air at 220°C on the Marvell MCU
This improved the operation of the SSD, which became much more stable.
The SSD answers quickly to lsblk and ddrescue. However fdisk -l is still not detecting it.
ddrescue now correctly attempts to clone the correct capacity ~256 Gb but is unable to clone any data however, whatever the logical location (offset) is.
I tried again the reflow, ramping up to ~245 °C, and also on the 2U22 chip on the verso. No further improvement.
In have no idea if the firmware had been upgraded or not. (I assume not.)
In the past I have known "blue screen errors" with Micron M4 SSDs because of an early firmware. However the SSD could be upgraded from Windows as detected by it, which is not the case this time.
Diagnosing SSD is alsways a difficult thing and I'm not sure whether it is an hardware or firmware issue here.
Seems that the SSD is unable to access the memory of the chips.
I attach a few pictures.
Anyone having faced such a problem with the RealSSD C400?
Thanks.
- Attachments
-

- Verso of the Micro RealSSD C400 MTFDDAK256MAM-1K12 circuit board
-

- Recto of the Micro RealSSD C400 MTFDDAK256MAM-1K12 circuit board
-

- After the reflow
-

- Before the reflow
-

- Sticker of the C400 SSD