Hello to all. This is my first post and I would like to say hello to the whole forum.

I have a Kingston SUV400S SSD which was used as the internal hard drive of a Lenovo Thinkpad Model W510 Notebook.
The BIOS was set in AHCI mode and not Compatibility but it never gave any major problems until yesterday when it stopped working and returned the following error:

https://imagesharing.com/uploads/20201111/31fc240c6b5837e949a6c71ac405d5df10ba2daa.jpg

The SSD partition table is now no longer recognized by any software and, if you try to create it with programs like TestDisk or GParted, the I/O Read error is returned. Even with Kingston's SSD Manager software we can't upgrade the firmware which is currently the "0C3G" (LBA: 468862128) because we cannot detect it.
If you do a scan with software like HDDScan, the sectors are all "Bad".
These are the photos of the piece:

https://imagesharing.com/uploads/20201111/dba98ca46fbd9db4030baacab811737baf415cf4.jpg
https://imagesharing.com/uploads/20201111/842950936ae3c437f2226401bbf2f5f4deebcff9.jpg

From a brief search on the web it would seem that the problem is the controller that does not communicate correctly with the devices to which it is connected.
I ask you for help on how to fix it.

Thanks in advance to anyone who can help me out.

It doesn't seem supported yet by PC3000, so if it's really a controller issue, there might not be a solution available yet.

_________________
http://www.pclab.com.pt facebook.com/PCLAB.A.T
ACELab partner

The model isn't listed, but the controller "88SS1074" is. So, it may be possible to recover if the OP sends it to a lab with an up-to-date PC3000 SSD.

_________________
Luke
Recovery Force Donor Inventory: 5,000+ Fully Cataloged HDDs & Growing

The controller is 88SS1079.

_________________
A backup a day keeps DR away.

Thanks for your answers.
We brought the SSD to a lab and they told us that we should actually bypass the controller and access the memory directly but the cost is around € 750.

Wouldn't it be possible to try to recover the data in another way? For example desoldering the memories with hot air and trying to put them on another board of the same model?
Would it be necessary at that point to instruct the controller to read the new memories because they are encoded?

or could we flash the Marvell controller with the correct .blf file?

Alternatively, if you were not using PC3000, is there a DIY and freewere solution to fix it?

sorry if I ask perhaps absurd questions but I am very interested in learning

Unfortunately all the answers to your questions are NO.



NO.


No. Well, maybe yes, but your data will be lost forever.


No. Even PC-3000 cannot handle this drive.


€750 is a very good price for this kind of job, assuming they have a workaround. I'm surprised, though. We've had very limited success with this controller (less than 15%), I'd be interested to know if someone has actually figured out a solution for these.

_________________
http://www.northwind.gr
SandForce SSD Recovery
Ransomware Reverse Engineering - NoMoreRansom! partners

Ok. Why Not?



Ok, but if it worked and we could create a partition map, even with unallocated space in a specific volume, would we be able to recover something using data recovery software? If not, why?



first they replied that PC3000 could recover this SSD by acting on the controller if I am not mistaken.



they did not assure us the success of the thing in fact.

I found this link in which they explain that they have succeeded:
https://www.szsghdd.cn/11715.html

Right, this link says that the drive would ID and they could access sectors without problems, but the drive had problem in SMART and reported bad sectors (they can also be seen in their screenshots).
It doesn't say anywhere that the controller is not working or that the translator is damaged.

_________________
http://www.northwind.gr
SandForce SSD Recovery
Ransomware Reverse Engineering - NoMoreRansom! partners

so in this case what procedure did they have to use to restore the SSD status?
I would like to understand it better because they don't explain it.

If it's a controller issue, PC3000 have to create a translator to bypass the controller and access data.
The problem is if that controller is not supported, the translator creation will be hard or impossible to do.

_________________
http://www.pclab.com.pt facebook.com/PCLAB.A.T
ACELab partner

They didn't restore any status.
They connected drive to PC-3000, created a task and used PC-3000 to bypass certain areas with bad sectors.

_________________
http://www.northwind.gr
SandForce SSD Recovery
Ransomware Reverse Engineering - NoMoreRansom! partners