{"id":1,"date":"2024-04-05T11:18:25","date_gmt":"2024-04-05T08:18:25","guid":{"rendered":"https:\/\/diginotion.com\/?p=1"},"modified":"2025-02-04T00:38:06","modified_gmt":"2025-02-03T21:38:06","slug":"how-we-repaired-an-ssd-with-failed-sectors","status":"publish","type":"post","link":"https:\/\/ssd-life.com\/en\/how-we-repaired-an-ssd-with-failed-sectors\/","title":{"rendered":"How We Repaired an SSD with Failed Sectors: A Rare Success Case"},"content":{"rendered":"\n

<\/h1>\n\n\n\n

The combination of SSD and “bad sectors” will seem unbelievable to many people: It doesn’t happen! In fact, SSD controllers are typically configured so that the user never sees “bad sectors” – the controller promptly removes these errors at the expense of “spare” blocks of flash memory. Theoretically, they can occur when the spare space runs out, but in practice this is very rare. Sometimes, when SSD disks “die”, they simply stop being recognized by the computer (as if they were never connected in the first place). While most experts consider SSDs with failed sectors beyond repair, we share a rare success story where recovery was possible. Here\u2019s how we defied the odds.<\/p>\n\n\n\n

This true story happened on a home server. The system disk was an old SSD Samsung 470 model, only 64GB. Released more than 10 years ago! It worked successfully, great performance and a lot of space was not required there, the activity of disk use is small.<\/p>\n\n\n\n

But then one day the Windows Update installation started failing – the next update was installed, the system rebooted, and then an installation error was reported. And so on, almost endlessly. Then other programs sometimes started to behave strangely. It became clear that “something was wrong”.<\/p>\n\n\n\n

After conducting a few tests, we found that while SMART was functioning properly, reading the SSD surface was causing errors in multiple locations. This was unexpected, as SSD controllers are typically programmed to automatically resolve these errors by utilizing extra space in flash memory. The user should never see this happen.<\/p>\n\n\n\n

We had already decided to throw out the SSD and replace it with another one, but then I got an idea – what if we just try to overwrite the entire surface of the disk? This could force the controller to reinitialize the flash memory arrays and potentially correct the error. We create a disk backup (a separate story, by the way, as we searched for image-based backup, which would ignore the erroneous sectors, I will say briefly – I recommend AOMEI Backuper, although there is such an option in many others, but it really worked out only with this one), booted from a flash drive and performed a disk surface write test, erasing all contents with new data.<\/p>\n\n\n\n

In the end, everything worked out!<\/strong> The writing test passed without errors, and data recovery from the backup was successful. This SSD has been functioning flawlessly in the home server for several months. Regular surface tests, such as SMART Long Selftest and other programs, confirm its perfect performance.<\/p>\n\n\n\n

I had to boot from a flash drive because it was the system disk. Although I could have plugged it into another computer, I did not want to go through the hassle of unscrewing a bunch of screws and taking out the disk.<\/p>\n\n\n\n

Why This SSD Recovery Was an Exception<\/strong>?<\/p>\n\n\n\n

Unlike typical cases, this SSD\u2019s controller architecture allowed partial sector remapping, making recovery possible despite the failed sectors.<\/p>\n\n\n\n

Conclusions:<\/h5><\/div>\n\n\n\n
    \n
  1. Don’t be in a hurry to throw away an SSD that is “glitchy”.<\/li>\n\n\n\n
  2. Try to overwrite the entire disk surface with a test first. For this purpose you can use any free disk testing utilities, in “surface test – write or erase” mode – Victoria, HDDTune, HDDScan.<\/li>\n\n\n\n
  3. Don’t forget about regular backups ))<\/li>\n<\/ol>\n\n\n\n
    \n\n\n\n