Samsung EVO 850 2TB SSD Failing

Hello all, looking for a bit of help.

I have an Alienware 17 that I put a Samsung EVO 850 2TB SSD into, and after a recent Windows 10 update, my computer ended up restarting a bunch of times. I think something must have gone wrong because now it won't find the drive at all. I've tried it in a hard drive dock with 2 other machines, and it will show up temporarily, but only if no other drive is in the dock as well. Same if I add it into the bay and run off the m.2 drive - it will find it, but will disappear.

I've tried reformatting the drive, and it won't show up long enough even for that. I tried Macrium and Easeus.

I'm starting to worry that the drive may be fried and I'm wondering if there's any way to confirm and recover what is on the drive, preferably at home and not through some service.

Thanks all.

 

I'm assuming its a 2.5 SATA SSD?
JayzTwoCents had a video where he had the same issue happen to him, you might want to check that out

 

It is, yes. Would you mind pointing me at the video? If its the "New Test Bench Keeps Boot Looping" video, I'm past the point I can even enter safemode - it gives me the no boot filename received message, and can't boot into any desktop.

 

Its older than that I think, a few months older

 

Have you tried turning it on and leaving it sit for 20-40 minutes?

I have had my boot ssd disappear after powerloss few times. Even ssd manufactures advise to let it sit turned ON so it can repair whatever is corrupted.

 

I had that sort of thing happen with an older (and smaller) Crucial drive. I found the solution on the forum on their site - it was, as you indicate, to leave it on for a significant time. You might see if there is a forum on the Samsung site.
Good luck,
Joe

 

I really wonder what "turning it on for a significant time" really does? It's not magic is it?

 

It seemed like magic to me - however, the Crucial folks had posted that this was expected - without a clear explanation. Further, I cannot answer the question about the duration. I think it was less than one hour, but it was never specified.

If I had more details, I would certainly pass them along. I'm just trying to be helpful. I do think it would be worthwhile checking with Samsung and any available forum of users, however.

Joe

 

Usually, when the drive is on, but inactive, the drive's controller goes through its garbage collection (GC) on the NAND cells, and any other housekeeping it deems necessary.

This is a rule of thumb for SSDs over the years - http://www.tomshardware.com/forum/264656-32-activate-ensure-garbage-collect-working

However, I've seen some posts where Samsung says its GC routine runs more aggressively. But in any case, just leaving it up and alone for a bit of time may or may not solve the problem, but there's not much to lose.