SSD gone? Don't treat it like a normal hard drive.
SSD & NVMe Data Recovery for Failed Disks or Missing Files
SSD and NVMe disks rely on a controller and different management technologies. Random attempts can lower recovery odds, especially with a firmware problem or continued use of the disk.
- +25
- Years of experience
- +50K
- Cases handled
- 99%
- Success rate after diagnosis
Silence doesn't mean the data is gone.
When do you need SSD data recovery?
- 01
The disk doesn't appear
The SSD or NVMe stopped showing in the system or device settings.
- 02
Files won't open
Files became unopenable or error messages appear on start-up.
- 03
Missing partitions
Partitions disappeared or the disk became unstable during reads.
The storage method changes the recovery method.
NVMe and M.2 data recovery
NVMe and M.2 disks are common in laptops and workstations. The fault may relate to how the disk is read or how it manages data; so the type, visibility state and error nature are inspected before deciding on recovery feasibility.
Inspect the case
Choose the path
Safe recovery
Supported devices & brands
SSD and NVMe drives we work on
The name on the label does not decide the path. The controller, the firmware revision and the encryption state do.
Samsung
Samsung uses its own controllers and firmware across its NVMe drives such as the 970, 980 and 990, and its SATA drives such as the 860 and 870. When something goes wrong the drive may fall into a read-only or internal protection mode, and that window is the best moment to image it, before it stops appearing altogether.
Kingston and Crucial
Kingston and Crucial drives mostly build on well-known controller families such as Phison and Silicon Motion. Work starts by identifying the controller family and firmware revision, because two drives sold under the same product name can carry different controllers.
WD and SanDisk
WD and SanDisk drives are common in laptops and in USB external drives alike. In the external ones the memory is sometimes soldered next to the controller on a single board, so there is no drive to take out and the path is decided by the state of that board.
M.2 NVMe vs SATA SSD
The M.2 shape does not mean NVMe. Some M.2 drives speak SATA and others speak NVMe over PCIe lanes. The protocol and the connection method are established before the first power-on, because a wrong adapter simply shows nothing and pushes the owner into trying again.
Encrypted drives
Encryption on an SSD may sit in the controller itself (OPAL) or at system level, such as BitLocker. Reaching the memory is not the same as reading the files: without the recovery key or the login credentials the data stays unreadable, and we say so before starting, not after.
TRIM behaviour
After a delete or a format the system issues TRIM, and the controller may keep erasing those areas in the background even while the drive sits idle. Stopping early changes the odds more than any tool used later.
How an SSD or NVMe drive is handled in the lab
- 01
Identify the drive before it is connected
M.2 running NVMe, M.2 running SATA, a 2.5-inch SATA SSD, or memory soldered to a board; each needs a different adapter. The board is also inspected for heat marks or a burnt component before any power reaches it.
- 02
Write-blocked connection, TRIM disabled
The drive is connected through a write-blocked path with automount and TRIM disabled, then the controller identity is read: does it report the correct model and capacity, or does it come up at zero capacity or in a safe mode. If it enumerates and stays stable, it is imaged in that same session in one pass at low queue depth, because SSDs tend to stop all at once rather than degrade slowly.
- 03
Controller and memory level work
If the controller does not respond, the work moves to chip level inside the lab: reading the memory and rebuilding the translation layer from block order, error correction and interleaving. On an encrypted drive with no key available, what comes back stays unreadable.
- 04
Rebuilding the files from the image
The file system is rebuilt from the image, never from the original drive. Samples are opened to confirm they are intact, and the data is handed back on a separate medium.
Start from the symptom
Which case describes your drive?
SSD and NVMe drives do not behave like mechanical disks, and the outcome of deletion on them is fundamentally different.
- 01
Not visible in BIOS or the system
The cause may be power, the port, the controller, or firmware. Not appearing does not prove the memory chips are empty, but it does mean ordinary recovery software cannot reach it.
- 02
Appears then disappears, or freezes the machine
The drive is unstable while reading, and its condition can degrade with long tests or repeated copying. Stop automatic scanning, and do not run speed tests or firmware updates.
- 03
Appears in read-only mode
Some drives enter a protective mode when they detect an internal problem. Do not try to force writing or formatting — this may be the last opportunity to copy the contents.
- 04
Files deleted or the drive formatted
The outcome differs sharply from an HDD because of TRIM and free-space management. Stopping use immediately matters, but it does not justify promising that every deletion is reversible.
- 05
Heat or a sudden shutdown
Some NVMe problems appear with heat, power loss, or component damage. Record what happened, and do not keep trying it in several machines if the drive heats up quickly.
Two things often confused
M.2 is not a synonym for NVMe, and reading the chip is no magic answer
M.2 describes the card's form factor, while the drive itself may run the SATA or the NVMe protocol. So 'I have an M.2' is not enough: we need a photo of the label or the full model, the machine the drive was fitted in, and whether it appeared in BIOS and at what capacity. Controllers and NAND management differ, and it is those — not the connector shape — that determine the reading tools.
In an SSD, files are not stored in direct order inside a single chip. The controller spreads data across chips, corrects errors, swaps cells, and maintains a table mapping logical addresses to physical locations. The data may also be encrypted internally, or by BitLocker or FileVault. Reading raw NAND therefore does not mean the files will simply appear: the route depends on the controller's health, access to the translation data, the state of the chips, and the encryption.
Depending on the case
Possible recovery routes
The drive is stable and reports the right capacity
A read-only image is taken with as little strain as possible, then the file system is analysed on that image. Recovered files are never written back to the same drive.
The drive cuts out or is slow
Priority goes to copying the important regions while monitoring temperature and stability. Work folders or important images may be ordered ahead of everything else if access is limited.
A controller or firmware problem
The drive needs a specialist assessment to establish whether temporary access or handling of that controller family is possible. Firmware is not updated from the internet, and manufacturer tools that can erase the drive are not used.
The drive is encrypted
The physical access problem is separated from the encryption. Even where a full image can be taken, the password or the BitLocker or FileVault key is still required to open the contents.
What we need for the initial assessment
- 01
Make, model and capacity
With a photo of the connector and the label.
- 02
Drive type if known
2.5in SATA, M.2 SATA, M.2 NVMe, or an external SSD.
- 03
Machine and operating system
The machine the drive was running in, and its system.
- 04
Does the system see it?
In BIOS or Disk Management, under what name and capacity.
- 05
How the drive behaves
Whether it heats up, drops the connection, or appears read-only.
- 06
The last event before the fault
An update, power loss, a fall, formatting, deletion, or disappearance.
- 07
What was tried afterwards
The software, updates and adapters that were used.
- 08
Encryption
Whether BitLocker or FileVault is present, and the password or recovery key.
- 09
The most important files
And their order of priority.
FAQ
A faster disk, a more precise diagnosis.
It's possible in some cases; the result depends on the cause of non-appearance and the state of the internal components.
Yes, NVMe and M.2 disks are inspected and recovery feasibility is determined by the fault type.
Yes, because an SSD uses a different way of storing and managing data.
No. M.2 is a physical form factor, and the drive may be SATA or NVMe. The full model number determines which.
You cannot judge from the feature's name alone. It depends on the system, how the deletion or format happened, whether the command reached the drive, and what followed. It does reduce the odds considerably.
A suitable adapter can help with a healthy drive, but it is no remedy for one that overheats, disconnects, or does not appear. An incompatible enclosure can also give a misleading diagnosis.
An update may fix a general operating problem, but it is not a safe step when the data is the priority. Some tools reinitialise the drive or change its state.
The odds are usually very low, because the operation is designed to remove access to the data. The tool used and what happened afterwards must be known before any judgement.
It depends on the integrity of the file system and its metadata. The structure may return intact, or files may return by type without their original names.
Stop powering it and do not keep trying it in different machines. Repeated heating can worsen the drive's condition before any image is taken.
No. It is saved to another medium so the source's state does not change and data not yet recovered is not overwritten.
TRIM can lower the odds because it wipes deleted cells, so how quickly you stop using the drive is a decisive factor in the outcome.
Yes, if the decryption key or password is available; without it the data stays encrypted even after a physical recovery.
Yes. The fault may be in the controller or firmware; we inspect the drive below the operating-system level to assess the possibility.
Next step
Send case detailsStop now to protect what's left.
If your data matters, don't keep powering on and don't install random software. Send your case for an initial assessment.