PC-based recovery planning
When the Synology chassis malfunctions but the drives may still contain usable data, Synology documents a Linux PC recovery procedure for DSM 6.2.x and later Btrfs or ext4 volumes. The method requires enough drive connections for the array members and mounts the reconstructed storage read-only. It is not a universal path: read-write SSD cache configurations are excluded, and encrypted storage requires the correct keys.
Quick answer
A PC recovery attempt should preserve the source disks
The goal is to assemble and mount the existing array read-only so files can be copied to another destination. Do not format the disks in Windows or accept prompts to initialize them.
Current Amazon listings
Replacement and migration DiskStation options
Product cards are supporting purchase references only; they do not determine whether your failed drives are recoverable or whether a specific migration pairing is supported.
Technical decision
Check applicability before removing drives from the NAS
Confirm filesystem, DSM generation, cache configuration, number of RAID/SHR members and encryption state. If those conditions do not match the official procedure, stop rather than improvise.
Interactive recovery tool
Recovery Readiness Checker
This tool routes the symptoms you select to a safer next step. It does not issue destructive commands. Before initializing a disk, deleting a pool, reinstalling DSM or moving the only copy of important data, verify the exact live Synology procedure for your model and DSM build.
Recovery safety checklist
Four rules before you change a failing Synology system
Preserve readable data first
If unique files can still be opened, copy or back them up before changing storage metadata, reinstalling DSM or running stressful diagnostics.
Record drives and bays
Capture drive serial numbers, bay positions, health states and DSM messages before swapping disks or moving them to another chassis.
Match the action to the failure layer
A degraded pool, crashed volume, failed system partition, bad drive and failed bay have different supported recovery paths.
Keep a rollback path
During migration or recovery, do not erase the source system until the destination data, permissions, applications and backups have been verified.
Use PC recovery when the chassis is the blocker
This path is most relevant when the NAS hardware cannot provide access but the member drives may still be readable. If DSM is running and files can be copied normally, an ordinary network backup is simpler and less invasive.
For PC-based Synology recovery, use pc recovery when the chassis is the blocker must stay within the boundaries of the published read-only Linux workflow. Confirm Btrfs or ext4 applicability, the complete RAID/SHR member set, cache configuration and encryption material before removing drives. Reject operating-system prompts to initialize unfamiliar disks, and never use the source array as the destination for recovered files. This checkpoint should preserve the ability to stop and escalate if the array will not assemble cleanly or any member begins producing severe hardware errors.
The documented filesystem scope is Btrfs and ext4
Synology specifies Btrfs and ext4 volumes under DSM 6.2.x and later for this recovery workflow. Do not assume the same commands apply to every historical Synology storage format.
For PC-based Synology recovery, the documented filesystem scope is btrfs and ext4 must stay within the boundaries of the published read-only Linux workflow. Confirm Btrfs or ext4 applicability, the complete RAID/SHR member set, cache configuration and encryption material before removing drives. Reject operating-system prompts to initialize unfamiliar disks, and never use the source array as the destination for recovered files. This checkpoint should preserve the ability to stop and escalate if the array will not assemble cleanly or any member begins producing severe hardware errors.
All required array members need PC connections
RAID and SHR depend on multiple member disks. The PC must have sufficient SATA or controller connectivity to present the complete required set without USB bridges that hide or alter device behavior.
For PC-based Synology recovery, all required array members need pc connections must stay within the boundaries of the published read-only Linux workflow. Confirm Btrfs or ext4 applicability, the complete RAID/SHR member set, cache configuration and encryption material before removing drives. Reject operating-system prompts to initialize unfamiliar disks, and never use the source array as the destination for recovered files. This checkpoint should preserve the ability to stop and escalate if the array will not assemble cleanly or any member begins producing severe hardware errors.
Preserve drive order and serial numbers
Before removing anything, photograph bays and record serials. Even when Linux can discover array metadata, an exact inventory protects against accidental reuse or confusion during a difficult recovery.
For PC-based Synology recovery, preserve drive order and serial numbers must stay within the boundaries of the published read-only Linux workflow. Confirm Btrfs or ext4 applicability, the complete RAID/SHR member set, cache configuration and encryption material before removing drives. Reject operating-system prompts to initialize unfamiliar disks, and never use the source array as the destination for recovered files. This checkpoint should preserve the ability to stop and escalate if the array will not assemble cleanly or any member begins producing severe hardware errors.
Do not initialize disks when another OS prompts
Windows or another operating system may offer to initialize unfamiliar Synology drives. Decline. Initialization writes new metadata and can destroy information needed to assemble the original array.
For PC-based Synology recovery, do not initialize disks when another os prompts must stay within the boundaries of the published read-only Linux workflow. Confirm Btrfs or ext4 applicability, the complete RAID/SHR member set, cache configuration and encryption material before removing drives. Reject operating-system prompts to initialize unfamiliar disks, and never use the source array as the destination for recovered files. This checkpoint should preserve the ability to stop and escalate if the array will not assemble cleanly or any member begins producing severe hardware errors.
The recovered volume should be mounted read-only
Synology’s commands culminate in mounting the assembled device with the read-only option. That choice minimizes changes to the source filesystem while files are being copied elsewhere.
For PC-based Synology recovery, the recovered volume should be mounted read-only must stay within the boundaries of the published read-only Linux workflow. Confirm Btrfs or ext4 applicability, the complete RAID/SHR member set, cache configuration and encryption material before removing drives. Reject operating-system prompts to initialize unfamiliar disks, and never use the source array as the destination for recovered files. This checkpoint should preserve the ability to stop and escalate if the array will not assemble cleanly or any member begins producing severe hardware errors.
Read-write SSD cache is an explicit exclusion
The current Synology article says the PC procedure is not applicable to volumes using read-write SSD cache. That configuration can make the array depend on cache state that is not captured by the HDD members alone.
For PC-based Synology recovery, read-write ssd cache is an explicit exclusion must stay within the boundaries of the published read-only Linux workflow. Confirm Btrfs or ext4 applicability, the complete RAID/SHR member set, cache configuration and encryption material before removing drives. Reject operating-system prompts to initialize unfamiliar disks, and never use the source array as the destination for recovered files. This checkpoint should preserve the ability to stop and escalate if the array will not assemble cleanly or any member begins producing severe hardware errors.
Encrypted volumes require the recovery key
Volume encryption adds a cryptsetup step using the correct recovery key. Without that key, assembling the underlying RAID does not automatically make the protected files accessible.
For PC-based Synology recovery, encrypted volumes require the recovery key must stay within the boundaries of the published read-only Linux workflow. Confirm Btrfs or ext4 applicability, the complete RAID/SHR member set, cache configuration and encryption material before removing drives. Reject operating-system prompts to initialize unfamiliar disks, and never use the source array as the destination for recovered files. This checkpoint should preserve the ability to stop and escalate if the array will not assemble cleanly or any member begins producing severe hardware errors.
Encrypted shared folders use a different layer
Shared-folder encryption is distinct from full volume encryption and uses its own key and mount procedure. Identify which encryption mechanism protected the data before planning recovery.
For PC-based Synology recovery, encrypted shared folders use a different layer must stay within the boundaries of the published read-only Linux workflow. Confirm Btrfs or ext4 applicability, the complete RAID/SHR member set, cache configuration and encryption material before removing drives. Reject operating-system prompts to initialize unfamiliar disks, and never use the source array as the destination for recovered files. This checkpoint should preserve the ability to stop and escalate if the array will not assemble cleanly or any member begins producing severe hardware errors.
Copy recovered files to separate storage
Do not use the source Synology disks as the destination for recovered data. A separate disk or NAS preserves the original array in case the first copy is incomplete or professional recovery later becomes necessary.
For PC-based Synology recovery, copy recovered files to separate storage must stay within the boundaries of the published read-only Linux workflow. Confirm Btrfs or ext4 applicability, the complete RAID/SHR member set, cache configuration and encryption material before removing drives. Reject operating-system prompts to initialize unfamiliar disks, and never use the source array as the destination for recovered files. This checkpoint should preserve the ability to stop and escalate if the array will not assemble cleanly or any member begins producing severe hardware errors.
Stop when assembly produces unexpected errors
If drives click, disappear, report severe I/O errors or the array cannot be assembled as expected, more retries can worsen a failing device. That is the point to image drives professionally or engage a recovery specialist.
For PC-based Synology recovery, stop when assembly produces unexpected errors must stay within the boundaries of the published read-only Linux workflow. Confirm Btrfs or ext4 applicability, the complete RAID/SHR member set, cache configuration and encryption material before removing drives. Reject operating-system prompts to initialize unfamiliar disks, and never use the source array as the destination for recovered files. This checkpoint should preserve the ability to stop and escalate if the array will not assemble cleanly or any member begins producing severe hardware errors.
PC recovery is not a migration strategy
Once files are safe, build a clean pool on known-good hardware and restore them. Synology warns that drives moved through recovery may not mount normally again in a new NAS, so do not design the next system around reusing the emergency array unchanged.
For PC-based Synology recovery, pc recovery is not a migration strategy must stay within the boundaries of the published read-only Linux workflow. Confirm Btrfs or ext4 applicability, the complete RAID/SHR member set, cache configuration and encryption material before removing drives. Reject operating-system prompts to initialize unfamiliar disks, and never use the source array as the destination for recovered files. This checkpoint should preserve the ability to stop and escalate if the array will not assemble cleanly or any member begins producing severe hardware errors.
Questions people ask
Recover Synology Data Using a PC questions
Can I connect Synology drives to a PC and read them?
Synology documents a Linux-based recovery procedure for applicable Btrfs and ext4 arrays from DSM 6.2.x and later.
PC recovery should remain read-only on the source and should be attempted only when the filesystem, cache and encryption conditions match Synology's supported workflow.
Can Windows read Synology RAID drives directly?
Not normally. Do not initialize the disks when Windows offers to do so; use the supported Linux recovery procedure instead.
Do I need every drive from the Synology RAID?
For RAID or SHR recovery, you need the required member drives available to the PC so the array can be assembled.
Can I use USB drive docks?
Direct, reliable disk connectivity is preferable. Bridges can hide SMART information or behave poorly with multiple RAID members.
Should the recovered Synology volume be mounted writable?
No. Synology's recovery procedure mounts the source read-only to reduce the chance of altering damaged storage.
Does this work with read-write SSD cache?
Synology specifically excludes volumes using read-write SSD cache from this PC recovery workflow.
What if my Synology volume is encrypted?
You need the correct recovery key and must follow the documented decryption steps before the volume can be mounted.
What if only a shared folder is encrypted?
Use the shared-folder encryption key and the appropriate eCryptfs-style recovery process rather than the volume-encryption path.
Where should I copy recovered files?
To a different storage device with enough capacity. Never recover back onto the source array.
What if the array will not assemble?
Stop repeated attempts when drives or metadata are unstable and consider professional recovery, especially when the data is unique.
Official references and methodology
Verify the live DSM state before any destructive recovery step
This PC-recovery guide follows Synology's Linux-based read-only recovery prerequisites for supported Btrfs/ext4 layouts. It calls out the requirement to have all member drives for RAID/SHR, preserve encryption keys where relevant, and avoid the method for volumes that use read-write SSD cache. The process is framed as extraction from original media, not repair of that media, with professional recovery as the stop point when the documented mount path fails.
- Synology: Recover NAS data using a PC
- Synology: What can I do if one of my volumes crashed?
- Synology: Determine whether errors come from the drive or slot
As an Amazon Associate, Cloudzat may earn from qualifying purchases. Failure states, DSM behavior, migration compatibility and recovery options can change by model and DSM build. Preserve readable data and verify Synology's current Knowledge Center instructions before initializing drives, deleting pools, reinstalling DSM or changing the only copy of important data.