Hello,
I’m currently unable to recover my files and keep getting the error message “The device is not ready”. The drive is a Samsung nvme 990 Pro SSD installed in a Sabrent enclosure connected to a USB C port on an MSI laptop.
The drive did not initially appear in Windows, so I used disk manager to assign a letter to the primary partition.
I have used the wizard and non-wizard to scan the drive in “deep scan” mode which takes about 3 hours and finds thousands of deleted files that I would like to recover. But when I try, I can’t recover any files because of the reason stated above.
The laptop is plugged in and all sleep modes have been disabled (as some have suggested), but the error continues.
I’m using the paid professional version of Recuva.
Please advise, or advise on how I can obtain a refund.
It is rarely possible to recover much, if anything at all, from a SSD - it’s just the way that SSD technology works.
The only files I’ve managed to recover from SSDs were System Files from ‘hidden’ partitions that were not beingTRIM’med so not garbage collected.
If you look at your results there were zero files recovered and 26 (not thousands) that couldn’t be recovered.
I do also note the filesizes there, they are just KB so they are not going to contain much more than the filename and pointers to where the files used to be.
Sorry but I don’t think that you will be sucessful in recovering files from a SSD.
It is rarely possible to recover much, if anything at all, from a SSD
This is patenetly false, and disqualifies your response.’
If you look at your results there were zero files recovered and 26 (not thousands) that couldn’t be recovered.
That because this was a test. You don’t spend hours selecting files when you are expecting the same, failed result.
I do also note the filesizes there, they are just KB so they are not going to contain much more than the filename and pointers to where the files used to be.
These are Touchdesigner files, which you know nothing about.
Update: I was able to recover many files. I’m not completely sure why it worked this time, but here is what I did differently:
- I moved the external drive from the USB C port to a (blue) USB A port
- I started recovering files immediately after the scan completed, in the hopes of avoiding a situation where windows powers off the drive.
I would hope the developers look into the cause of this problem so they can offer a proper fix to their customers.
Thanks to everyone who offered assistance.
Summary of what was recovered…
