
- Why Regular Data Recovery Tools Can’t Restore Files from RAID
- Key Information About the NAS Asustor LOCKERSTOR 16R Pro
- How to Remove Hard Disks from Your NAS and Connect Them to a PC
Why Regular Data Recovery Tools Can’t Restore Files from RAID
Conventional hard drives store user data by writing it sequentially across the disk surface, which means an entire file is typically located on a single drive. In contrast, when data is written to a RAID array, each file is split into multiple fragments. These fragments are then distributed and written in sequence across all the drives in the array. Depending on the configuration, fragment sizes can range from 2 KB to 2 MB, so every file is physically stored across several disks at once.
This approach significantly increases read and write performance — after all, writing two halves of a 1 GB file to two drives simultaneously is much faster than writing the full 1 GB to a single disk. However, this same mechanism makes file recovery far more complex.
Different RAID levels use different methods to distribute and protect data. On top of that, manufacturers like Asustor often add their own proprietary structures and variations. As a result, data can be written to disks in many different formats, and each requires a specific approach during recovery.
How can the number of drives in a NAS Asustor LOCKERSTOR 16R Pro device's RAID array impact data recovery and potential loss?
The number of drives in a NAS Asustor LOCKERSTOR 16R Pro device's RAID array can impact data recovery and potential loss in the following ways:
- Redundancy: RAID arrays are designed to provide redundancy and protect against data loss. The more drives you have in the RAID array, the higher the level of redundancy. For example, a RAID 1 array with two drives mirrors the data, so if one drive fails, the other still contains a complete copy. In contrast, a RAID 5 array with three or more drives uses parity to distribute data across the drives, allowing for recovery even if one drive fails.
- Fault tolerance: With more drives in the RAID array, there is a higher level of fault tolerance. If a drive fails, the remaining drives can continue to function and the data can be recovered from the redundancy or parity information. However, if there are fewer drives in the array, the failure of a single drive can result in data loss if there is no redundancy or parity to recover from.
- Rebuilding time: When a drive fails in a RAID array, the array needs to be rebuilt by redistributing the data across the remaining drives. The more drives there are in the array, the longer it may take to rebuild the array. During this rebuilding process, the array is at risk of another drive failure, which can lead to data loss if there is not enough redundancy or parity.
- Capacity and performance: The number of drives in the RAID array also affects the overall capacity and performance of the NAS device. More drives can provide higher storage capacity and potentially better performance due to increased read and write speeds. However, if you have a larger number of drives, the risk of drive failure and potential data loss also increases.
In summary, having more drives in a NAS Asustor LOCKERSTOR 16R Pro device's RAID array generally provides better data protection and recovery options. However, it is important to consider the trade-offs in terms of cost, capacity, performance, and the potential risks associated with multiple drive failures during the rebuilding process.
How to Remove Hard Disks from Your NAS and Connect Them to a PC
Although the NAS LOCKERSTOR 16R Pro can be accessed over the network, you still need to remove its hard disks and connect them directly to a Windows PC. Only then can the recovery software properly scan and analyze the drives. Follow these steps:
-
Power off the NAS and disconnect it from the power source.
WARNING! Before removing any drives, carefully read the device manual. Improper actions may damage both the NAS enclosure and the hard disks in the RAID array.
-
Remove the hard disks one by one, gently sliding each drive out of its slot. Remember that hard disks are highly sensitive: any impact or drop can cause serious physical damage.
-
Label each hard disk according to its position inside the NAS. The order of the drives is crucial for correct RAID reconstruction.
-
Connect the drives to your computer. In this video, we explain which ports you can use to connect hard disks and what to do if your PC does not have enough free connectors.
Go to view
Step-by-Step Data Recovery with Hetman RAID Recovery

This program restores data from damaged RAID arrays and is fully compatible with Asustor LOCKERSTOR 16R Pro. Each hard disk in the array contains technical metadata describing how files were written. When launched, Hetman RAID Recovery analyzes this metadata, automatically reconstructs the damaged array, and provides access to its contents. After that, you can browse the recovered disk and save your files. The program can also restore files that were accidentally deleted from the network drive.
How to recover data from a Asustor
LOCKERSTOR 16R Pro has 16 HDD slots, and it supports the following array types:
- RAID 0;
- RAID 1;
- RAID 5;
- RAID 6;
- RAID 50;
- RAID 60;
- RAID 10;
- JBOD;
NAS supports:
- Ext2;
- Ext3;
- Ext4;
How to Safely Recover Data from Disk Images
This utility allows you to create a complete copy of a disk and work with the disk image instead of the physical drive. This approach helps protect your data from:
- Overwriting during the recovery process;
- Additional data loss caused by bad sectors;
- User errors.
To create a disk image, follow these steps:
-
Ensure you have enough free space to store the image. Its size will typically match the size of the original disk.
-
In the main window, select the target disk and choose Tools - Save Disk. You can also select multiple disks if needed.
-
When the Image Creation Wizard opens, select whether you want to save the entire disk or only a specific region. Adjust the settings and click Next.

-
Choose the directory where the image will be saved. You may select any available disk connected to your PC or upload the image via FTP.

Where Are the User’s Files Actually Stored?
The Asustor LOCKERSTOR 16R Pro network-attached storage keeps OS Linux operating system files on a separate RAID 1 (mirrored) array. Usually, all NAS systems create several volumes on every hard disk, and the first of them takes up to 2 Gb of space. This is where operating system files are stored. Other volumes are united into a RAID array where user’s data is written.
RAID Recovery Software: Detailed Comparison
| Product | Operating system | RAID controller support | Supported file systems | Virtual RAID controller support | Data recovery from damaged RAID | File preview |
|---|---|---|---|---|---|---|
| Hetman RAID Recovery | Windows, Linux, MacOS | Yes, over 100 controllers | FAT, exFAT, NTFS, ReFS, APFS, HFS+, Ext4, Ext3, Ext2, ReiserFS, Btrfs, VMFS, Hikvision, XFS, UFS, ZFS | Yes | Yes | Yes |
| DiskInternals RAID Recovery | Windows | Yes, over 10 controllers | FAT, NTFS, Ext2/3/4, HFS+ | No | Yes | Yes |
| R-Studio | Windows, Mac, Linux | Yes, over 20 controllers | FAT, NTFS, Ext2/3/4, HFS+ | Yes | Yes | Yes |
| UFS Explorer RAID Recovery | Windows, Mac, Linux | Yes, over 100 controllers | FAT, NTFS, Ext2/3/4, HFS+ | Yes | Yes | Yes |
| EaseUS Data Recovery | Windows | Yes, over 20 controllers | FAT, NTFS, Ext2/3/4, HFS+ | No | Yes | Yes |
| ReclaiMe Free RAID Recovery | Windows | Yes, over 100 controllers | FAT, NTFS, Ext2/3/4, HFS+ | Yes | Yes | Yes |


Yes, data recovery from a NAS Asustor LOCKERSTOR 16R Pro device can still be possible even if the device is experiencing intermittent connectivity issues. However, the process may be more challenging and time-consuming compared to recovering data from a fully functional device.
Here are a few steps you can take to attempt data recovery:
Remember, it is crucial to avoid further damage to the NAS device and its data during the recovery process. It is advisable to consult with professionals who specialize in data recovery to ensure the best possible outcome.