
- Why Regular Data Recovery Tools Can’t Restore Files from RAID
- Key Information About the NAS Raidon InTANK iR8022
- 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 Raidon 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 use of specific file-sharing protocols impact data loss risks on NAS Raidon InTANK iR8022 devices?
The use of specific file-sharing protocols can impact data loss risks on NAS Raidon InTANK iR8022 devices in several ways:
- Security vulnerabilities: Different file-sharing protocols have varying levels of security. Some protocols may have known vulnerabilities that can be exploited by attackers to gain unauthorized access to the NAS device and potentially cause data loss.
- Authentication and access control: File-sharing protocols have different methods for authentication and access control. Weak or inadequate authentication mechanisms can increase the risk of unauthorized access to the NAS device, leading to data loss.
- Encryption: Some file-sharing protocols support encryption of data during transmission, while others may not. If sensitive data is being shared over an insecure or unencrypted protocol, it can be intercepted and accessed by unauthorized parties, leading to data loss.
- Data integrity: Certain file-sharing protocols have built-in mechanisms to ensure data integrity during transmission. These mechanisms can detect and correct errors or corruption in the data. Using protocols without such mechanisms can increase the risk of data loss due to undetected errors or corruption.
- Compatibility and interoperability: Different file-sharing protocols may have varying levels of compatibility and interoperability with different operating systems and devices. Using protocols that are not fully compatible with the NAS device or client systems can lead to data loss or corruption during file transfers.
To mitigate data loss risks, it is important to choose file-sharing protocols that prioritize security, authentication, access control, encryption, data integrity, and compatibility. Regularly updating the NAS device's firmware and applying security patches can also help minimize vulnerabilities and protect against potential data loss. Additionally, implementing proper backup strategies and disaster recovery plans can further safeguard data in case of any unforeseen events or data loss incidents.
How to Remove Hard Disks from Your NAS and Connect Them to a PC
Although the NAS InTANK iR8022 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 Raidon InTANK iR8022. 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 Raidon
InTANK iR8022 has 2 HDD slots, and it supports the following array types:
- RAID 0;
- RAID 1;
- JBOD;
NAS supports:
- APFS / HFS+;
- 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 Raidon InTANK iR8022 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, it is possible to recover data from a NAS Raidon InTANK iR8022 device that has been affected by a controller card failure or interface problem. However, the success of data recovery depends on the extent of the damage and the expertise of the data recovery service provider.
In such cases, it is recommended to contact a professional data recovery service that specializes in NAS devices. They will have the necessary tools and expertise to diagnose the issue and recover the data from the affected device. It is important to note that data recovery from RAID systems can be complex and time-consuming, so it is advisable to seek professional help rather than attempting to recover the data yourself, as improper attempts may further damage the data or make recovery more difficult.