Question Samsung Evo 850 - 500GB Suddenly died, after i wake it up from Hibernate

[giffmetango]

One day ago, I woke up my PC from hibernation, and it couldn't detect any boot drive. I thought it messed up the BIOS. After several attempts, it was still the same.

The BIOS still detected the Samsung Evo 860 - 500GB, so I plugged it into a SATA-to-USB 3 adapter (tried multiple adapters) to test. None of the adapters showed the contents of the SSD, but the PC slowed down when trying to use DiskPart or find the drive in HDD Sentinel. After a while, DiskPart showed Disk 2, but with no partitions.

The SSD's health is still good, and it's been working fine for several years without any issues. It contains Windows 10, many configuration files, Firefox passwords, sessions, etc.

When the SATA-to-USB 3 adapter stopped blinking the white light, I refreshed Device Manager and rescanned the disk in HDD Sentinel and CrystalDiskInfo. However, the drive was unresponsive. HDD Sentinel took a long time to detect the Samsung Evo 860, but it still did not respond.

DISKPART> list disk

Disk ### Status Size Free Dyn Gpt
-------- ------------- ------- ------- --- ---
Disk 0 Online 119 GB 0 B
Disk 1 Online 465 GB 1024 KB *
* Disk 2 Online 465 GB 465 GB

DISKPART> select disk 2

Disk 2 is now the selected disk.

DISKPART> list partition

There are no partitions on this disk to show.

Is this a hardware failure or a software issue? It's pretty new to me, as I thought this would only happen if the SSD had reached a very low health level. I've hibernated many times, from several days to weeks, so I was pretty shocked when I woke it up yesterday and found out it wasn't working anymore.

I'm trying to find a 5-star screwdriver, but it seems they're rare in my country. I want to open the SSD and see what went wrong, especially since it happened after hibernation. All other devices in the PC are still functioning normally—multiple HDDs, CPU, fans, GPU, etc.

 

[CountMike]

One day ago, I woke up my PC from hibernation, and it couldn't detect any boot drive. I thought it messed up the BIOS. After several attempts, it was still the same.

The BIOS still detected the Samsung Evo 860 - 500GB, so I plugged it into a SATA-to-USB 3 adapter (tried multiple adapters) to test. None of the adapters showed the contents of the SSD, but the PC slowed down when trying to use DiskPart or find the drive in HDD Sentinel. After a while, DiskPart showed Disk 2, but with no partitions.

The SSD's health is still good, and it's been working fine for several years without any issues. It contains Windows 10, many configuration files, Firefox passwords, sessions, etc.

When the SATA-to-USB 3 adapter stopped blinking the white light, I refreshed Device Manager and rescanned the disk in HDD Sentinel and CrystalDiskInfo. However, the drive was unresponsive. HDD Sentinel took a long time to detect the Samsung Evo 860, but it still did not respond.


Is this a hardware failure or a software issue? It's pretty new to me, as I thought this would only happen if the SSD had reached a very low health level. I've hibernated many times, from several days to weeks, so I was pretty shocked when I woke it up yesterday and found out it wasn't working anymore.

I'm trying to find a 5-star screwdriver, but it seems they're rare in my country. I want to open the SSD and see what went wrong, especially since it happened after hibernation. All other devices in the PC are still functioning normally—multiple HDDs, CPU, fans, GPU, etc.

Just like any electronic part, SSDs can also die without warning, that's why backup SW exists. Unless there was smoke or sparks, opening it up would not tell you anything. There is a control chip and one or more memory chips. None of it repairable at home. There is another possibility, control chip firmware may have gone nuts, like what happened to one of my cheap Kingston 250GB SSDs but I was able to flash new one in. Just Google "ssd firmware update tool" and find your SSD. Data would be lost but SSD possibly saved.

 

[Bob.B]

One day ago, I woke up my PC from hibernation, and it couldn't detect any boot drive. I thought it messed up the BIOS. After several attempts, it was still the same.

The BIOS still detected the Samsung Evo 860 - 500GB, so I plugged it into a SATA-to-USB 3 adapter (tried multiple adapters) to test. None of the adapters showed the contents of the SSD, but the PC slowed down when trying to use DiskPart or find the drive in HDD Sentinel. After a while, DiskPart showed Disk 2, but with no partitions.

The SSD's health is still good, and it's been working fine for several years without any issues. It contains Windows 10, many configuration files, Firefox passwords, sessions, etc.

When the SATA-to-USB 3 adapter stopped blinking the white light, I refreshed Device Manager and rescanned the disk in HDD Sentinel and CrystalDiskInfo. However, the drive was unresponsive. HDD Sentinel took a long time to detect the Samsung Evo 860, but it still did not respond.


Is this a hardware failure or a software issue? It's pretty new to me, as I thought this would only happen if the SSD had reached a very low health level. I've hibernated many times, from several days to weeks, so I was pretty shocked when I woke it up yesterday and found out it wasn't working anymore.

I'm trying to find a 5-star screwdriver, but it seems they're rare in my country. I want to open the SSD and see what went wrong, especially since it happened after hibernation. All other devices in the PC are still functioning normally—multiple HDDs, CPU, fans, GPU, etc.

Disk fail and that's a fact of life.
When it does you cuss at it a little and then install your spare disk.
Spin in your backup and go.

 

[Misgar]

the PC slowed down when trying to use DiskPart or find the drive in HDD Sentinel. After a while, DiskPart showed Disk 2, but with no partitions.

If a PC slows down considerably and takes ages trying to detect a hard disk or SSD, I take this a sign the drive has probably died.

I've experienced this whilst trying to delete hidden system partitions from cheap 120GB and 240GB SATA SSDs, but I never use Windows Hibernate, preferring to disable it completely and then delete 'hiberfil.sys'.

The faulty SATA SSDs are now sitting in my dead components bin. One day I'll recycle them as electronic WEEE scrap.

 

[giffmetango]

If a PC slows down considerably and takes ages trying to detect a hard disk or SSD, I take this a sign the drive has probably died.

I've experienced this whilst trying to delete hidden system partitions from cheap 120GB and 240GB SATA SSDs, but I never use Windows Hibernate, preferring to disable it completely and then delete 'hiberfil.sys'.

The faulty SATA SSDs are now sitting in my dead components bin. One day I'll recycle them as electronic WEEE scrap.

I bought the Samsung one because everyone told me it's a good SSD. (Even though I have an 850 250GB that has been in use for 1,948 days with 144TB written and 55% health, it's still good.)

However, the 860 suddenly died, which surprised me. I hibernate it because my motherboard doesn't have a sleep mode. Maybe hibernating it poses a higher risk than just using sleep mode alone?

The PC has experienced multiple power outages in the past—outages while in use and during hibernation—but everything was still fine until midnight on November 4.

The price for the EVO 860 was not cheap in 2019; I think you could buy a 1TB NVMe drive in 2024 for the same price.

Already ordered x5 screwdriver 5 point-star to open it,

 

[USAFRet]

Electronics die.
Eventually all of them.

While it may be rare, Samsung is not immune.

 

[giffmetango]

Electronics die.
Eventually all of them.

While it may be rare, Samsung is not immune.

Lesson learned: I need to schedule mirroring of Windows to 1-2 HDDs.

I’ve already ordered a screwdriver; let’s see if my luck is still there..

btw today, the computer power supply exploded, causing a power outage on the entire third floor and tripping the circuit breaker.

Jump test confirms the PSU is dead, but everything else is still working when I swap in a new MSI PSU. I’m not sure if the PSU was the culprit behind the SSD dying after waking from hibernate, or if it’s due to the phone with a supercapacitor soldered onto the battery mainboard (and plugged into usb hub) which was connected directly to the motherboard’s USB 3 port using a Type-C to USB cable.

 

[dreamteam]

I bought the Samsung one because everyone told me it's a good SSD. (Even though I have an 850 250GB that has been in use for 1,948 days with 144TB written and 55% health, it's still good.)

55% it's not healthy at all I think you have learn nothing from past mistakes.
the average endurance is 75 TBW so it's likely to die at any given moment LOL

 

[dreamteam]

However, the 860 suddenly died, which surprised me. I hibernate it because my motherboard doesn't have a sleep mode. Maybe hibernating it poses a higher risk than just using sleep mode alone?

The PC has experienced multiple power outages in the past—outages while in use and during hibernation—but everything was still fine until midnight on November 4.

why on earth do you set it to sleep ?
unlike HDD's that take longer to boot up this is not necessary for SSD's

I can't tell what's going on while the SSD stays in hibernate mode but it might be the cause of your loss, go figure

https://www.quora.com/Can-an-SSD-hard-drive-be-damaged-by-a-sudden-power-loss

A Closer Look At SSD Power Loss Protection - Kingston Technology

The combination of firmware/hardware PFAIL protection are a highly effective method for preventing data loss in enterprise SSD applications, allowing important metadata information to be written to flash memory to ensure a successful recovery of the SSD on the next power up.

www.kingston.com

 

[dreamteam]

Already ordered x5 screwdriver 5 point-star to open it,

what waste of time and money....
there is nothing you can do unless you send it in to a the repair center lab

View: https://www.youtube.com/watch?v=TQdkhFGCcgs

 

[dreamteam]

I’m not sure if the PSU was the culprit behind the SSD dying after waking from hibernate

I think I ve got a bad power supply as well.
I use it on my test bed computer only, the two main power plugs feed 1 SSD and 1 HDD which work as expected however when plugging another HDD into the other plugs the disk head gets start buzzing (clic, clic, clic)
I have suffered from many power outages (mainly during winter days) with no major issues though

 

[dreamteam]

There is another possibility, control chip firmware may have gone nuts, like what happened to one of my cheap Kingston 250GB SSDs

SA400S ?

 

[CountMike]

SA400S ?

Yes. 128GB

 

[dreamteam]

Yes. 128GB

somebody on reddit showed off a box full of dead SA400 drives but he didn't tell what the cause was he only claimed they are not good drives. LOL

I have the 240GB one that I didn't pay for and it never left me down to my knowledge except one time I felt a weird boot up session like it was frozen but right after some reboots it went back to normal

 

[CountMike]

I found and flashed new firmware in hope to save files but they were gone. It went bad once when PC was shut down because of power cut. Because of small capacity and now I have only NVME drives, this and second same one are used as removable over USB.

 

[giffmetango]

look like controller is <Mod Edit> broken, i tear the ssd apart, and use one probes of multimeter to bridge between each in red circle , it immediately recognized seagate usb sata to usb adaptor

but still extremely slow when rescan disk, my hdd sentinel even hang up

disk management it show : unknow, not initialized
when trying to initialize,

hdd sentinel recognized

https://imgur.com/t4lw4HA