Synology Volume Crashed: What to Do While Files Are Still Readable
Our founder and lead technician, Joseph Montanti, handles cases personally.
If Synology reports a crashed volume but File Station can still read your files, do not power the NAS off before protecting them. Synology's documented advice is to keep that readable system running and copy data to a client computer on the local network. If the files are unreadable, the next step is assessment, not removing the pool. First distinguish a crashed volume from a merely degraded pool, and do not apply a generic unplug-first recovery checklist to this situation.
On this page
The first decision is whether files are still readable
Read the actual status in Storage Manager and check whether existing files can be accessed through File Station. Do not start by rebuilding, replacing disks, or rebooting to see whether the warning disappears. The present access state determines what can be protected now.
Synology's crashed-volume guidance, updated March 31, 2026, separates readable and unreadable scenarios. For a still-readable crashed volume, it specifically advises keeping the system powered on and backing up first. This is the central instruction for that scenario.
Being able to sign into DSM is not the same as being able to read the volume. The management interface may work while the data is unavailable. Conversely, a serious status warning does not necessarily mean every currently accessible file is already lost.
- DSM works and files read: preserve accessible data to separate storage before system changes.
- DSM works but files do not read: stop attempts to recreate the pool and seek data-focused guidance.
- The NAS cannot start: the immediate access path is unavailable; do not treat it as the readable-volume case.
- A drive was accidentally removed: use Synology's specific version-dependent scenario rather than improvising a general rebuild.
Electrical danger, smoke, or a damaged power supply requires immediate safety judgment. The keep-running advice is about a readable crashed volume, not permission to operate hazardous equipment.
Crashed and degraded are different storage states
A degraded redundant pool may still operate with reduced fault tolerance. A crashed volume is a different condition and should not be handled as a routine replacement-disk task solely because both show a warning.
Synology's Storage Manager overview describes pool maintenance and degraded-pool repair features. Those are not evidence that the same procedure repairs every crashed filesystem. Match the documentation to the reported state and DSM version.
Distinguish the physical drives, storage pool, volume, and shared folders. A drive health label applies to one component. A volume status describes another layer. Seeing a drive reported as healthy does not by itself prove that the volume's filesystem is consistent.
Synology's causes-of-volume-crash article lists both drive-related and filesystem-related causes, including excessive missing members and filesystem errors. That range is why the word “crashed” should not be translated automatically into “replace disk two.”
Record the NAS model, DSM version, RAID or SHR arrangement, drive count, volume and pool status, and any SSD cache. Preserve screenshots and existing logs if they are accessible. Do not run additional stress tests just to fill every field in a checklist before protecting readable files.
Copy readable files to a separate destination now
Prepare a client computer on the local network with enough healthy storage. Use a destination that does not depend on the same affected pool. Another shared folder on that pool is not an independent backup, even if it has a different name.
Prioritize what is missing from existing backups. Begin with irreplaceable documents, current projects, and application data whose loss would prevent work. A complete archive may be the eventual goal, but a deliberate order can preserve the most important material first.
Copy rather than move, and keep a record of skipped or failed items. Avoid starting several competing bulk transfers just to maximize activity. The useful measure is verified data preserved, not the number of simultaneous copy windows.
Some applications need more than a folder of visible files. A database may require its supported export or backup method to produce a consistent copy. A virtual machine may have several related files. Coordinate with the person who maintains those applications before treating a raw folder copy as a complete business recovery.
Synology advises skipping an individual file that cannot be copied from the crashed volume and continuing with other files. Keep that file on the unresolved list. A failed copy is not a reason to erase the pool or repeatedly retry the same item while accessible data remains unprotected.
Do not schedule a reboot, firmware update, pool removal, or exploratory disk swap during this preservation work. If the system's behavior worsens or broad access fails, stop and reassess rather than blindly continuing the same plan.
Verify the backup before removing or recreating storage
The dangerous point is mistaking “the transfer finished” for “the needed data is safely recoverable elsewhere.” Before any pool removal, check that the destination contains the intended folders, dates, and file types. Open relevant samples from the destination itself.
Review the exceptions. If the files that failed were precisely the ones you needed, a large successful transfer of other material does not settle the recovery question. Keep the original storage preserved while deciding whether those missing items justify further work.
Check application usability as well as file presence. A photo catalog with missing originals, an accounting database that cannot open, or a project with absent linked files may not meet the intended goal. Verification should match how the data will be used.
Removing a pool is not a way to retrieve its contents. Synology's rebuild-and-restore sequence follows backup in the readable scenario. Do not jump to the destructive part before the separate copy has been checked and any missing data decision is complete.
Once preservation is complete, the platform's documented diagnostic and recreation process can be considered with appropriate support. Keep the scope clear: restoring the NAS to service is now a separate task from recovering whatever remains missing.
If backup capacity is insufficient, solve the destination problem rather than deleting source files to simplify the job. Another healthy destination or an agreed prioritization plan is preferable to changing the evidence you are trying to preserve.
If files are unreadable or a drive was removed
When DSM can start but File Station cannot read the data, Synology directs users toward data-rescue assistance. A pool that cannot supply files is not made safe by creating a new pool over the same disks.
Preserve every original drive, its bay position, and the sequence of events. Record any replacements, rebuild attempts, scrubs, power losses, and cache changes. Do not wipe a member marked failed or assume a replacement drive contains all of its predecessor's information.
For accidental removal, Synology documents different assembly behavior for DSM 7 and DSM 6.2. Identify the actual version and event before following that scenario. Do not take a version-specific restart instruction and apply it to a different, still-readable crashed-volume case.
Connecting a NAS member to Windows can introduce another trap: Windows may not recognize the storage layout and offer to format it. See why a NAS drive may appear RAW in Windows before treating that prompt as a diagnosis.
The original NAS and its configuration information can matter alongside the disks. Preserve details of encryption, recovery keys, and storage layout through a secure process. A disk that can be read at the hardware level does not automatically yield a usable decrypted shared folder.
Set a precise recovery goal before further intervention
Tell the support provider whether any files are still accessible and what has already been copied. That distinction should lead the discussion. It prevents an otherwise sensible generic instruction from interrupting your current working access path.
List the remaining target data and available backups. Include important date ranges and application dependencies without disclosing private file contents in the first inquiry. Explain whether the goal is a few missing files, a complete share, or a consistent business application.
Our Synology recovery guide provides broader context, while RAID and NAS assessment addresses cases where the original storage needs examination. Neither the NAS brand nor the word “crashed” can establish a guaranteed result.
After recovery or restoration, review why the previous protection was insufficient. Redundancy, snapshots, separate backups, and power protection cover different problems. A new pool with a green status is not a substitute for a backup you can access and restore independently.
Frequently Asked Questions
Should I shut down a crashed Synology volume immediately?
Not if it is the still-readable scenario in Synology's guidance. Keep the system running and protect accessible data first. Unreadable storage and electrical hazards require different decisions.
Can I remove the pool and recover the files afterward?
Do not use that as a recovery plan. Verify a separate backup before removing storage, and preserve the original if important files remain missing or unreadable.
Is a degraded pool the same as a crashed volume?
No. They describe different states and can require different procedures. Record the exact pool and volume messages rather than relying on the warning color alone.
What if a few files fail during backup?
Record the failures, continue preserving other readable files where the system remains stable, and evaluate the missing items separately. Do not call the backup complete merely because most files copied.
Get help with data recovery
Bring your device to our Lincroft lab during opening hours, or mail it in.
How to mail your deviceThe $100 diagnostic is non-refundable once diagnostics start, and donor drives or replacement parts you approve are non-refundable once ordered, even if recovery fails.
Published by MDrepairs
MDrepairs is a data recovery and electronics repair lab in Lincroft, New Jersey. Our founder and lead technician Joseph Montanti films real cases for our YouTube channel, showing tools, repair steps and recovery outcomes.
Keep reading
- Windows Storage Spaces Failure: Preserve the Pool Before Resetting Disks
- RAID 1 Recovery: Why a Mirror Does Not Save Every Deleted File
- RAID 0 Drive Failure: Why Replacing the Disk Does Not Rebuild Your Files
