We are committed to providing fast, efficient, and affordable software solutions that set new standards in the software development industry.
  • Data Recovery from a Simple NAS

NAS (Network Attached Storage) devices are becoming more and more popular both in home and small to medium size business environments. Compared to PC-based file servers, they are inexpensive, consume less electricity, and are easy to maintain even for a not so experienced person.

Most NAS devices use RAIDs of various types for disk fault tolerance and data consistency. Many NAS vendors offer their customers their proprietary RAID management systems that are able to combine different hard drives into quite complex RAID systems without much knowledge of RAID technology. Those systems allow home or small business users to efficiently utilize their spare hard drives, but they also come with one drawback: when it comes to data recovery, it's not clear how handle such RAID systems.

This article will show you how to use our data recovery program R-Studio to recover files from typical simple NAS configurations.

General notes on data recovery from NAS devices
Most commercial NAS devices differ from regular PCs: quite often they use Intel-incompatible CPUs (usually PowerPC processors), they have no video output ports, and it's impossible to connect a keyboard and mouse to them. Therefore none of the available data recovery tools, R-Studio or R-Studio Agent included, can run directly on such devices. That's why disks should be taken out from such devices and connected to a computer where R-Studio is installed.

Most NAS devices runs on a customized version of the Linux OS. All various proprietary RAID management systems are based on two Linux RAID technologies: mdadm and LVM2. Those systems create more user-friendly interfaces for disk management, whereas the underlying technology remains pure native Linux. R-Studio supports both of these technologies and can assemble such RAIDs automatically in most cases.

We also recommend you to save images of the disks, as data recovery professionals always do, and perform all file recovery from such images. Our article Clone Disks before File Recovery explains why. The drawback of this approach is that such images may be quite large, and if disk space to store those images is a problem, you may recover data directly from the disks, provided that you're absolutely sure that the disks in the NAS device are healthy. You may check this using disks S.M.A.R.T. attributes, which we'll explain later.

You'll also need a free disk space large enough to store recovered files. It may be an internal or external disk, or other storage device visible to the host computer, including connected network disks.

In this article we'll use free OpenMediaVault as our test NAS because it can use the RAID and LVM2 technologies in the most transparent way.

If the NAS volumes were reformatted, you can also use this article to re-create the RAIDs and then follow the instructions in our article Data Recovery from a Re-formatted ext4FS disk.

A mdadm RAID-based NAS
NAS configuration:
We used three 500 GB disks in this configuration. The most efficient way to utilize them is to create a RAID5. This is a good trade-off between storage space and reliability.

Fig. 1 shows the components of such a RAID5 created using the mdadm technology.
mdadm RAID5 components
Fig.1. mdadm RAID5 components.
Click image to enlarge

An ext4fs volume based on this RAID5 was created and made accessible on a local network as the //NAS-TEST/NAS-test/ share. Then some files were written to that share. Fig. 2 shows the file system stored on this NAS device.
File system on the NAS device.
Fig.2. File system on the NAS device.
Click image to enlarge

Then the SF folder containing jpg files was deleted.
File system on the NAS device with the deleted SF folder
Fig.3. File system on the NAS device with the deleted SF folder.
Click image to enlarge

To make the situation much worse, one disk in the RAID5 failed. Its S.M.A.R.T. status went red (a failure) and soon the disk stopped working at all.
A failed disk in the RAID5
Fig.4. A failed disk in the RAID5.
Click image to enlarge

Due to this hardware failure the NAS share became inaccessible on the local network.

Inaccessible NAS share
Fig.5. Inaccessible NAS share.
Click image to enlarge

Data Recovery:
As it was said before in this article, the disks should be taken out of the NAS device and connected to a computer with installed R-Studio and data recovery should take place on that computer.

1. Start R-Studio and locate the NAS mdadm RAID5 and its components:
mdadm RAID5 in R-Studio
Fig.6. mdadm RAID5 in R-Studio.
Click image to enlarge

You may also add RAID5 components manually, if R-Studio cannot automatically identify some of them. See R-Studio help for details: Linux mdadm RAIDs.

2. Then immediately check the S.M.A.R.T. status of the RAID5 components. Select the disk and its S.M.A.R.T. tab.
S.M.A.R.T. attributes of the RAID5 components
Fig.7. S.M.A.R.T. attributes of the RAID5 components.
Click image to enlarge
In our case, all components are healthy, and we can recover data directly from physical disks rather than their images.

3. Double-click the mdadm RAID5 and wait for R-Studio to enumerate files. Locate the deleted folder and go to it to browse its files.
Deleted folder in R-Studio
Fig.8. Deleted folder in R-Studio
Click image to enlarge

4. Check file recovery chances for the deleted files. Right-click a file and select Recheck Recovery Chances on the shortcut menu.
Rechecking recovery chances.
Fig.9. Rechecking recovery chances.
Click image to enlarge

Select Verify consistency of known files on the Recheck Recovery Chances dialog box to improve the accuracy of chance estimate.
Recovery chances
Fig.10. Recovery chances.
Click image to enlarge

5. You may search for specific files and preview them.
For graphic files, you may do it in two ways:

a) By viewing them as icons.
Graphic files as small icons.
Fig.11. Graphic files as small icons.
Click image to enlarge

You may select Small Icons, Medium Icons, or Large Icons tab, whatever is convenient to you.

b) By viewing a particular file in a built-in File Previewer. Double-click the file to view it.
File previewer.
Fig.12. File previewer.
Click image to enlarge

The File Previewer in R-Studio supports many file formats, including almost all graphic, video, and audio files, and Microsoft Office, Open/Libre Office, and pdf documents. It plays/shows them even without their native applications installed.

You may also search for individual files and folders. See R-Studio help for details: Searching for a File.

6. Mark files for recovery
Files marked for recovery
Fig.13. Files marked for recovery.
Click image to enlarge

When all necessary files are marked, click the Recover Marked button and specify place to store recovered files and other recovery parameters.
Files marked for recovery
Fig.14. Recovery parameters.
Click image to enlarge

See R-Studio on-line help for details: Basic File Recovery.

When all parameters are specified, click the OK button, and R-Studio will start file recovery showing its progress.
Recovery progress
Fig.15. Recovery progress.
Click image to enlarge

When the recovery is completed, you may go to the folder the recovered files have been saved to and browse through them.
Recovered files
Fig.16. Recovered files.
Click image to enlarge

A mdadm RAID/LVM2-based NAS
NAS configuration:
In this configuration another set of storage devices will be used: one 1 TB and two 500 GB disks. Fig. 17 shows this disk set.
Disk set for the mdadm RAID/LVM2-based NAS
Fig.17. Disk set for the mdadm RAID/LVM2-based NAS.
Click image to enlarge

In this case the best trade-off between storage space and reliability is to create a liner (sequential) LVM2 volume of two 500 GB disks and then create a RAID1 (mirror) volume of the 1 TB disk and the linear LVM2 volume. Fig. 18 shows this configuration.
Volume configuration of the mdadm RAID/LVM2-based NAS
Fig.18. Volume configuration of the mdadm RAID/LVM2-based NAS.
Click image to enlarge

An ext4fs volume based on this RAID5 was created and made accessible on a local network as the //NAS-TEST/NASTest/ share. Then some files were written to that share. Fig. 19 shows the file system stored on the NAS device.
File system on the NAS device.
Fig.19. File system on the NAS device.
Click image to enlarge

Then the 1 TB disk failed and the share was inaccessible on the network.

A special data recovery procedure has to be performed to get all of the files back.

Data Recovery:
Again, the disks should be taken out of the NAS device and connected to a computer with installed R-Studio, and data recovery should take place on that computer.

1. Start R-Studio and locate the NAS disks and automatically created mdadm RAID1.
 mdadm RAID1 and its components in R-Studio
Fig.20. mdadm RAID1 and its components in R-Studio.
Click image to enlarge

R-Studio should create it detecting the RAID parameters automatically. You may also add mdadm RAID1 components manually, if R-Studio cannot automatically identify some of them, see R-Studio help for details: Linux mdadm RAIDs.

The component of this mdadm RAID1 is another complex disk object - an LVM volume Test_1-Test_1.

2. To check S.M.A.R.T. status of the hard drives from the NAS, we need to locate them in the Device View panel. Select the Test_1-Test_1 object and locate its hard drives.
LVM2 volume and its components in R-Studio
Fig.21. LVM2 volume and its components in R-Studio
Click image to enlarge

Check the S.M.A.R.T. status of those hard drives by selecting the drive in the Device View panel and its S.M.A.R.T. tab.
S.M.A.R.T. attributes of the LVM2 components
Fig.22. S.M.A.R.T. attributes of the LVM2 components.
Click image to enlarge

3. R-Studio has automatically found a valid file system on this mdadm RAID1 (the virt-mdadm-NAS-Test:0 object). Double-click this object and wait for R-Studio to enumerate the files.
File system on the NAS device
Fig.23. File system on the NAS device.
Click image to enlarge

No files were deleted from the NAS device, that is why R-Studio is able to immediately determine chances for successful recovery for the files. So, no need to recheck them again.

4. You may search for specific files and preview them.
For graphic files, you may make R-Studio show them as icons.
Graphic files shown as icons.
Fig.24. Graphic files shown as icons.
Click image to enlarge

Many other files can be displayed in a built-in File Previewer. Double-click the file to play it back.

The File Previewer in R-Studio supports many file formats, including almost all graphic, video, and audio files, and Microsoft Office, Open/Libre Office, and pdf documents. It plays/shows them even without their native applications installed.
Graphic files shown as icons
Fig.25. Movie file played back in Previewer.
Click image to enlarge

You may also search for individual files and folders. See R-Studio help for details: Searching for a File.

5. Mark files for recovery.
Files marked for recovery
Fig.26. Files marked for recovery.
Click image to enlarge

When all necessary files are marked, click the Recover Marked button and specify a place to store recovered files and other recovery parameters.
Files marked for recovery
Fig.27. Recovery parameters.
Click image to enlarge.

In most cases, leave them with their default values. See R-Studio help for more details if necessary: Basic File Recovery.

When all parameters are specified, click the OK button, and R-Studio will start file recovery showing its progress.
File Recovery Report
Fig.28. Recovery progress.
Click image to enlarge

Once the recovery is completed, you may go to the folder the recovered files have been saved to and browse through them.
Recovered files
Fig.29. Recovered files.
Click image to enlarge

Conclusions
In our both NAS recovery cases R-Studio restored the RAID configuration automatically even for complex mdadm/LVM2 volumes, found deleted files and folders, and was able to recover all, even deleted, files.

Linux Recovery Feedback
15 feedbacks
Rating: 4.9 / 5
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.
Hello!
Thank you very much for R-Studio for Linux.
Please pay attention to new Linux package manager `Snappy` => https://snapcraft.io/
Good luck!
Great programm, great service, TOP !A+++
While currently evaluatin R-Studio for Linux i`m quite impressed with how thorough it is.

Regrettably it`s not possible to simply restore the accidently zapped partitions ?

An installer wiped my boot drive without asking and erased LVM and other partitions.
I used R-Linux to recovery my company files after a RAID 1 failure. Not only did it work great in windows 10 but it was free. You guys are awesome!!! A+++++++++++++ I hope I never need your software again:)