Recover files from a failed drive using a second NAS

A failed hard drive does not always mean your files have disappeared. If the drive belonged to a NAS, the best recovery path often involves a second network-attached storage system with enough capacity to receive an image, a copy of the surviving data, or an exported backup. The key is to protect the original evidence and avoid making the damaged disk work harder than necessary.

This approach suits home users, small businesses and offices that run Synology, QNAP or similar systems. It can also help when a NAS enclosure has failed while its disks remain readable. However, a second NAS is a destination and recovery tool, not a substitute for a current backup. RAID protects availability in some situations, but it does not protect against deletion, corruption, ransomware or a second hardware failure.

Identify the failure before moving data

First determine whether the problem is the disk, the NAS operating system, the network, or the storage pool. A drive that clicks, repeatedly spins up and stops, disappears from the BIOS or reports rapidly increasing bad sectors should be treated as physically failing. Avoid repeated reboots, filesystem repairs and “initialise” prompts, as these can overwrite metadata that a recovery technician may need.

If the NAS still starts, check its storage manager and system logs from a separate computer. Synology Storage Manager and QNAP Storage & Snapshots can show whether a disk is degraded, disconnected or marked as critical. A degraded RAID 1 or RAID 5 volume may still be accessible, while a failed enclosure might leave every disk healthy.

Keep the original drive order and label each disk clearly. Do not remove several disks from a RAID set and test them in random USB docks. If the array is encrypted, record the recovery key and administrative credentials before making changes. For a drive that is making unusual noises, stop using it and consider a professional data recovery service instead of attempting a home repair.

Prepare the second NAS safely

The receiving NAS needs adequate free space for the data you intend to recover, plus working room for temporary files, snapshots and logs. A 12 TB source volume may require substantially more than 12 TB on the destination if you are creating a disk image or preserving several versions. Use a healthy RAID pool on the second unit, preferably with a separate backup afterward.

Update the destination NAS, but avoid upgrading or changing the damaged system until the copy is complete. Create a dedicated recovery account with a strong password and limited permissions. Connect both NAS devices to the same switch using wired Ethernet. Wi-Fi can work for small transfers, but it is unreliable for many terabytes and can make troubleshooting difficult.

Australian home connections are often built around NBN plans whose download speed looks impressive while upload performance is much lower. Keeping both devices on the local network avoids sending data through the internet, reduces transfer time and avoids unnecessary cloud traffic. In a Brisbane storm or during a summer power event, use a UPS for both NAS units and the network switch so a copy is not interrupted halfway through.

Mount the source without making repairs

If the original NAS can still read the volume, mount it in read-only mode where the operating system allows this. Do not run filesystem checks, rebuild the RAID or replace a disk simply because the management interface displays a warning. A rebuild places heavy stress on all remaining drives and can turn a recoverable fault into a complete array failure.

For a software RAID or a NAS that will not boot normally, use a compatible Linux recovery environment or the manufacturer’s recovery procedure. The exact commands depend on the filesystem and RAID layout. Btrfs, ext4, ZFS, QNAP QuTS hero and Synology DSM arrangements should not be treated as interchangeable. If you are uncertain, take photographs of the disk order and capture the NAS configuration before changing anything.

When individual files are visible, copy the most valuable folders first: accounting records, customer documents, photographs, project files and databases. A file browser is suitable for a small, readable dataset. For a large or unstable source, use a resumable tool such as rsync, which can continue after a network interruption and verify file attributes.

Copy files with verification

Create a shared folder on the second NAS specifically for recovered material. Use SMB for straightforward access from Windows and macOS, or NFS where a Linux recovery machine is handling the transfer. Preserve ownership, timestamps and permissions when those details matter. A direct copy through File Station or File Explorer may preserve filenames but lose some metadata.

Rsync is useful because it can compare source and destination files rather than blindly copying everything again. A typical recovery workflow copies in stages, checks the destination, and records errors for later review. Do not delete source files after a successful transfer. If the source disk is deteriorating, prioritise irreplaceable data before media libraries or easily replaced downloads.

Large Australian households can generate substantial photo and video libraries from iPhones, GoPro cameras and security systems. Those files often contain duplicate versions, but deleting duplicates during recovery adds risk. Make a complete readable copy first, then sort and deduplicate on the second NAS or another backup device.

Handle RAID, snapshots and encryption carefully

RAID level determines what the NAS may still be able to expose. RAID 1 can continue from one surviving mirror, while RAID 5 generally tolerates one failed disk and RAID 6 can tolerate two. RAID 0 offers no redundancy. SHR, storage pools and nested RAID arrangements require the original configuration and should not be reconstructed from guesswork.

Snapshots can provide a clean version of files affected by accidental deletion or ransomware. On Synology, Snapshot Replication may allow recovery from a Btrfs snapshot; QNAP systems may offer snapshots and version management through Storage & Snapshots. A snapshot is useful only if the underlying pool remains readable, and snapshots stored on the same failed NAS are not an independent backup.

Encrypted shares and full-volume encryption require their keys, passwords or recovery files. Keep those credentials offline and never paste them into an untrusted recovery utility. If the NAS was used by a business covered by Australian privacy obligations, treat recovered customer, employee and health information as sensitive. The Australian Privacy Act and Notifiable Data Breaches scheme may require an assessment if personal information was exposed.

Check the recovered data before trusting it

A transfer that reaches 100 per cent is not necessarily a successful recovery. Open representative documents, play photographs and videos, extract archives and test databases on a separate computer. Compare file counts and sizes between source and destination. Hash checks can confirm that a file copied without alteration, although a matching hash cannot repair a file that was already corrupt.

Review permissions and ownership before returning the data to staff. A shared folder that is readable by every household account or office workstation may expose confidential material. Keep the recovered data offline or read-only until you have confirmed that ransomware or malware was not copied with it.

For teams that need to keep working while recovery continues, a NAS can host collaborative services alongside file storage. Planning a collaborative document server can reduce the temptation to edit files directly inside an uncertain recovery share. Give active users a separate working location and preserve the recovered copy as an untouched reference.

Choose the right recovery method

The second NAS method is most effective when the source is readable and the problem is limited to an enclosure, configuration or one accessible disk. It is less suitable when drives are clicking, the RAID metadata is damaged, or the NAS cannot maintain a stable connection. In those cases, imaging the disk with specialised hardware or engaging a data recovery laboratory is safer.

Local support can be worthwhile for a business in Melbourne, Sydney, Perth or regional New South Wales, particularly when downtime affects invoices, clinical records or production work. Ask a provider whether it works from disk images, whether it charges for an assessment, and whether recovered data is stored securely. A cheap replacement NAS from an Australian retailer may solve the hardware problem, but it will not fix physically damaged platters.

Recovery situation	Best first action	Role of the second NAS	Main risk
NAS enclosure has failed but disks are healthy	Use a compatible enclosure or recovery system	Receive a complete file copy	Wrong disk order or filesystem
RAID volume is degraded but readable	Copy critical files immediately	Store the recovered dataset	Rebuild stress causes another failure
One disk has bad sectors	Image or clone the disk first	Hold the image or extracted files	Continued reads worsen the damage
Files were deleted recently	Check snapshots and backups	Receive a restored version	New writes overwrite recoverable data
NAS was encrypted or hit by ransomware	Preserve keys, logs and snapshots	Hold clean offline copies	Copying malware or losing credentials
Disk clicks or will not spin	Stop powering it on	Usually not the first tool	DIY recovery can reduce laboratory options

After the files are verified, create at least one additional backup that is not permanently connected to the NAS. A USB disk stored separately from the equipment is practical for a home, while a business may use cloud object storage, a second site or rotating encrypted disks. Follow a 3-2-1 pattern: three copies, on two types of storage, with one copy kept away from the primary NAS.

Use the second NAS as a controlled recovery destination, document what was copied and retain the original disks until the new backup has been tested. Acting carefully can turn a frightening drive failure into a manageable restoration, while disciplined backups make the next incident far less disruptive.