We are committed to providing fast, efficient, and affordable software solutions that set new standards in the software development industry.
  • How to recover data from NVMe devices

General information:
Solid State Drives (SSD) have now become the main storage devices in modern computers, even in very inexpensive models. They have many advantages over conventional hard disk drives: they have higher read/write speed, consume less power, and are more shock-resistant. Even their two main disadvantages, relatively less capacity and higher cost, are steadily descending.

At first, SSD devices had the same form factor (2.5" HDD) and interface (SATA) as conventional hard drives did. But now they also have a different, much smaller, form factor M.2, more convenient for laptops. They also may have several different interfaces: SATA 3.0, USB 3.0, and the fastest one: NVM Express (NVMe), which is based on the PCI Express bus.

An example of a NVMe device
Click image to enlarge
Fig.1. An example of a NVMe device

Specifics for file recovery from NVMe devices
Software must be able to work correctly with such devices to get direct access to their data which is necessary for file recovery. All data recovery products of R-TT, Inc, R-Undelete, R-Photo, and all R-Studio versions (including R-Studio Emergency) support such work. Moreover, they specifically show such devices on their panels.

R-Undelete
Click image to enlarge
R-Undelete
R-Studio
Click image to enlarge
R-Studio
Fig.2. NVMe devices in R-Undelete and R-Studio.

Being SSD devices in nature, NVMe devices have all their drawbacks in file recovery. We discussed them in detail in our article File Recovery Specifics for SSD devices. Below is a brief summary.

File Recovery Specifics for SSD devices.

  • Deleted files can almost never be recovered on Windows and Mac computers. Even raw file recovery cannot help. It may be possible to recover some deleted files on Linux machines if recovery is done before the TRIM command is issued.
  • Some files can be recovered from slightly damaged file systems (recognized by their native OS) if recovery is done fast and on systems with the TRIM command disabled.
  • Data recovery is possible from severely damaged file systems (not recognized by their native OS).

Recommendations for file recovery from NVMe devices:
A standard procedure for file recovery from a system storage device - taking the device out of the system and connecting it to a SATA port, or through a USB, FireWire, or Thunderbolt external box to an another computer specially set up for file recovery - something that usually cannot be applied to NVMe devices because such a task requires serious experience in handling electronic components. Quite often such devices are hardwired to the system board which makes such extraction impossible for a common computer user and needlessly difficult even for a skilled professional. That is why the data has to be recovered on that same computer with the NVMe device. Here there are two options:

  • Disable the TRIM command on the computer with the NVMe device. See the File Recovery Specifics for SSD devices article for more information on how to do that. We recommend you to use portable versions of our file recovery programs: R-Undelete for Windows machines and R-Studio for Mac for Apple computers.
  • Use the startup version of R-Studio. It has all of the features of R-Studio for Windows/Mac/Linux and similar looking panels and controls, but starts from a separate bootable disk with the TRIM command disabled.

The last but perhaps the most important advice: with all the difficulties that come with file recovery from SSD devices, a regular data backup from such devices becomes especially important. We have a very powerful yet easy-to-use solution for such tasks: R-Drive Image. We strongly recommend you to download the fully functional 30 day trial and give it a try.

Data Recovery Feedback
370 feedbacks
Rating: 4.8 / 5
I really love your R-Studio product, I am doing Data Recovery as a professional, I used RS since the early versions and I loved the product, as far as I can tell, R-Studio, especially the Tech Version (but including the standard) is one of the best and excellent tools for a pro to have in the arsenal of tools in a pro DR lab, especially combining with the specialized Data Recovery hardware providers like DeepSpar, and PC3000, the rest of `wannabees` out there are waste of time, strongly recommend
I lost more than 200K files from my NAS due to a mistake. I tried 3 different recovery solutions over the 4 TB raid disks, and all of them performed ok but to be honest none of them were able to Raw recover the files and rename them with meaningful names out of the Metadata like R-TT did, then I was able to sort again my files and pictures and kind of restore all of them.

R-TT may not be the easiest or most user-friendly solution, but the algorithm used for the renaming saved me THOUSAND of hours of opening ...
Just recovered my old ext4 partition with R-Studio after trying testdisk and R-Linux without success. That partition was overwritten by another ext4 partition and I was losing my hope until I tried R-Studio demo. It detected all my files and directories again!

Bought it and 100% recommend it for anyone with a similar issue.
Genuinely tried every free program available without luck of recovering a deleted file from months ago. Thinking my file was deleted forever and lose all hope I came across this website as a recommendation.

I was reluctant as it seemed pricey compared to other programs, but damn worth every penny. It managed to even find files I thought were wiped from existence.

Kudos to r-tools, thank you!
Why make incremental backups, when there is R-Studio?

I`m an IT professional who has worked from home for over a decade. Early on in my career, I configured an HP ProLiant Server (Raid 1+0) as a workstation that I would remote into from my laptop. As technology evolved, I began to use it only for email and as a config file repository.

A short while ago, one of the drives degraded, but the HP ProLiant Server (Raid 1+0) still functioned fine on the remaining drive. I was complacent and didn`t replace the ...