Guide · SSD & NVMe

Can data be recovered from a failed SSD?

Solid state disk failure modes differ significantly from hard disk failures. They tend to fail suddenly with little or no warning. While recovery is possible, the nature of solid state disks complicates that process. In this article we will explore why solid-state disks fail, what can be recovered when they do fail, and what you should NOT do while waiting for professional help.

Free 48-hour diagnostic
Handled in-house
Only pay if we recover your data · most jobs
// in short

Often, but trickier.

SSD recovery is possible but due to NAND flash memory, controllers and encryption it is much more difficult than recovering a hard drive. Do not continue to use it. Never reformat it. Get a professional diagnostic specialist to evaluate it.

Controller
Common fault
NAND
Chip-level work
Don't
Reformat it
Free
Diagnostic
// what it is

Why an SSD fails differently.

Unlike traditional hard disk drives (HDD), solid-state disks (SSDs) have neither heads nor platters. As such, there is no moving parts for which to replace or repair; therefore, the failure of an SSD is typically an electronic event. However, when an SSD does fail, its failure is generally due to some type of electronic malfunction of either the SSD's control logic, its firmware or the flash memory itself. In many cases, however, the data stored on the SSD may remain intact, but inaccessible. This occurs when the SSD's controller module has become non-functional. Since the controller is responsible for managing both the writing/reading process of data onto/from the SSD, as well as translating logical block addresses (LBA) to physical locations on the SSD, without it functioning properly, the data will appear to be gone, even if the actual storage media containing the data remains intact. For example, an SSD might appear as "no drive found" within a particular operating system (such as Microsoft Windows), while also not being recognised as having been installed by a particular hardware detection mechanism (i.e., BIOS).

// how they fail

How SSDs actually fail.

Failure of an SSD is always related to a flaw in its electronic circuitry, whether it be the flash memory or the controller, and which of the two has failed decides how recoverable your data is.

01

Controller failure

Typically speaking, most SSD failures occur at the level of the controller. When an SSD controller becomes faulty, it can cause several different types of problems depending upon the nature of the problem. In general, once an SSD controller fails, users may find that their drive cannot be accessed through an operating system, or through any other means. Despite this fact, however, the NAND flash memory modules (which contain the user's data) are generally unaffected by the problem that caused the controller to fail. Therefore, if the failure was limited solely to the controller (and did not affect the underlying flash memory), then it may be possible to restore access to the contents of the drive.

02

Firmware corruption

Firmware errors are another source of SSD failures. They can cause problems with SSD functionality. Some examples include updates to a drive's firmware failing during execution (thereby rendering the firmware unusable). Additionally, firmware bugs can result in SSD failure. Furthermore, sudden loss of power to an SSD while it is updating its firmware can also render the firmware unusable. Any of these scenarios can lead to unexpected behaviour when trying to use an SSD. Such examples include seeing an SSD reported incorrectly in terms of size or interface, or not at all. Also, some SSDs can enter into a locked state or read-only mode after a failure, thereby preventing any changes to files on that drive.

03

Worn-out NAND

The number of write cycles an SSD's flash memory components are capable of supporting before they begin to degrade varies greatly depending on many factors including usage patterns and quality of construction. Because each write cycle causes damage to a portion of the flash memory cell, repeated writes can eventually reduce the effectiveness of an individual cell until it reaches a point where it ceases to function reliably. Once a cell can no longer store data, it will normally turn into a bad sector. Over time, as more and more cells become unreliable or damaged beyond recovery, an SSD can turn unstable or read-only, and its performance can slow dramatically or cease altogether.

04

Power-loss corruption

A partial write on an SSD (interrupted by loss of power; a dislodged cable) is likely to leave the SSD in an intermediate write state. So when you access the SSD via your file system, you see that it has been corrupted/RAW.

05

Physical, liquid or board damage

Portable and NVMe devices are prone to physical damage caused by a variety of things including but not limited to: drops, spills, electrical surges which can cause damage to the circuit boards or controllers that prevent further use of otherwise functional memory chips.

06

Encryption lock

A large number of today's solid-state drives (SSDs) are encrypted using default settings with the encryption keys being stored within the SSD controllers. Once the SSD's controller dies, it may become difficult or impossible for us to access those keys to recover your data.

// the honest part

The honest answer on SSD recovery.

It would be extremely simple to promise that all SSDs can be restored; however, SSDs do not function in the same manner as hard drives. There are three reasons why SSDs are much more difficult. First, TRIM: When you remove files from an SSD or format it, it tells the drive that those particular memory locations are available. In many cases, these areas are wiped clean by the drive within just seconds after they have been made available. This makes deleted-file recovery almost impossible using common methods for recovering deleted files. Second, Wear levelling: Data is randomly distributed throughout the chips on the SSD and placed into specific patterns that are determined by the controller. Therefore, simply accessing the raw flash provides a jumbled puzzle that needs to be rebuilt. Third, Encryption: If the SSD encrypts data at rest and the controller fails, there is a chance that the encryption key will also fail along with the controller. That doesn't mean that an SSD cannot be recovered. Controller and firmware failure, where the actual chips are still good, are typically quite recoverable. What it does indicate is that the honest answer regarding an SSD's ability to be recovered depends entirely upon how it failed and that the fastest method to determine that information is through a complimentary diagnostic.

×The most critical factor is time. The longer an SSD is used while it is failing, then the longer it will continue to perform "house cleaning" (garbage collection & wear levelling) which could overwrite the very data being attempted to recover.
// what to do

What to do — and what not to.

If your system has a Solid-State Drive (SSD), then writing to that drive will be its worst enemy. Your goal should be to prevent as much as possible from being written to the drive until it gets into good hands.

Do

Stop using the drive

Shut down the computer and remove the SSD from the device if possible so the drive itself cannot erase data due to the drive's "background cleaning" process running while the device sits idle.

Do

Note what happened

Is your problem with the firmware upgrade failing, was there a power outage, did you drop it, or has your computer simply been slowing down gradually over time to where it crawls along like a snail? There could be one of several faults here.

Do

Send it in for a free diagnostic

Simply send it in by insured post or have it dropped off to our location. We will let you know prior to you spending anything whether we believe this is a recoverable failure or it is a TRIM issue.

×Don't continue to restart your system and/or reformat hoping it will eventually recognise and mount again. On an SSD each write operation is another opportunity for losing data.
×Do not execute “SSD repair” or formatting tools because many will send TRIM and/or firmware commands which will delete all the information you need recovered.
×Don't even think about reflashing the firmware to try to recover your data from a dead SSD. A bad flash can brick the controller completely so you'll lose your data too!
×Avoid doing any sort of chip-level repairs yourself. Flash memory chips are fragile and will destroy themselves in seconds when handled improperly without proper equipment.
// how we recover it

How a failed SSD is recovered.

SSD recovery has its own set of rules, and we do everything in our facility. The approach is based upon whether the controller can be accessed.

01

Free diagnostic

We determine whether the problem is the controller, the firmware, the NAND flash, or file system; and if there is an encryption layer. Before proceeding, you receive a written, fixed price for what needs to be done.

02

Controller-level access

If the controller is partially working then we can also run some of our SSD specialists' tools in order to speak with it, to build its translation table again (and thus allow us to read past the faulty area) and to read data around the faulty area.

03

Reading the flash directly

If the controller has completely died then we will read the NAND itself, and then we will rebuild this model's translation and wear levelling scheme so that we can turn all the randomised flash memory into a series of readable files.

04

Encryption & file system

When dealing with a device's own hardware encryption, we will go through the device's controller. However when using BitLocker or FileVault, we will need your encryption key or password. We will then rebuild the file system on the SSD and verify that the data was properly read.

05

Read-only, then your file list

All images are taken as read only so they may be worked from a duplicate image; and you will receive a complete report of everything that was recovered prior to making any decisions regarding recovery.

// faq

Common questions.

What people generally ask us about their failed SSDs.

Often not. We would say this right from the start. Virtually all SSDs are using TRIM (which deletes the deleted files and data) very quickly. So generally speaking, virtually all of your deleted data is gone when you delete a file. The only other possibility is the failure of an SSD (controller, firmware etc.) as opposed to a deletion of a file; but your data should still be present on the NAND memory chips.

Usually not. An SSD that does not show in Windows or BIOS is usually a faulty controller or bad firmware, which means that the NAND chips (and your data) are likely fine. This is probably one of the best chances for recovering data from an SSD.

Discipline-wise, they're the same thing. NVMe, M.2 and SATA drives all write data to NAND flash memory and then read it back through a controller, just different connectors.

If it's encrypted by either BitLocker or FileVault, we'll need to know your recovery key or password so we can get going. If the SSD was encrypted internally by its manufacturer and the controller has stopped working then we may not be able to decrypt your data; again our diagnostic will give you an honest answer first before taking payment.

Diagnostics are free, with prices for SSD recovery starting from £300 + VAT. In most cases you only pay if we recover your data. There is a 50% down payment toward any necessary specialist bench time if we need to open up the SSD and inspect the internal chips, and the balance only if we recover your data.

// failed ssd?

SSD died or vanished? Don't keep writing to it.

Turn it off and send it in to us for a free evaluation to see if we can recover your files. Generally speaking, if the controller dies, the files are still present on the solid state drive (SSD).

Call us — 028 9002 0144
Mon–Fri · 9am–5:30pm · No fix, no fee
Start a free diagnostic →
028 9002 0144