Yes — crashed and inaccessible NAS volumes are usually recoverable, including Synology SHR and QNAP thin volumes where one or more drives have degraded. We reconstruct the array and filesystem from the member disks in our lab. The single most important thing: do NOT reinitialise, reset, repair or rebuild the NAS — that's what turns a recoverable volume into a lost one.
NAS "volume crashed"? Your data is probably still there.
A Network Attached Storage (NAS) unit is more than a box of disks — it runs a proprietary operating system (DSM on Synology, QTS on QNAP) layered over RAID and an advanced filesystem like SHR, Btrfs or ext4. When it reports a "crashed volume" or a drive failure, the panic is understandable — but in most cases the underlying data is intact and recoverable.
The danger is the NAS interface itself: it will happily offer to "repair", "reinitialise" or "rebuild" the volume — and any of those can overwrite the very data we need. CBL reconstructs the SHR/Btrfs/ext4 structures from the member disks in our lab, without relying on the failed NAS, so your shared folders, backups and business files come back safely.
Do not reinitialise, reset to factory, rebuild the volume, or run the NAS's repair tools. If a drive has failed, power the unit down and label the disk order. Then book a free diagnosis.
NAS brands we recover
Every major NAS platform and filesystem — with dedicated expertise for the two most common in Singapore.
Synology data recovery
The platform we see most often here. DSM runs SHR or SHR-2 — Synology's own layout over Linux RAID — with Btrfs or ext4 above it. The classic failure is a "Volume 1 has crashed" warning after a second disk degrades, or Btrfs metadata damage DSM refuses to mount while every member disk still reads. Both are usually recoverable, provided nothing was rebuilt first.
QNAP data recovery
QTS layers ext4 over thick or thin LVM volumes; QuTS hero uses ZFS. The usual symptom is "the volume is not active", or a pool that comes back read-only after a firmware update. Thin-provisioned pools are the fiddly ones: the mapping between pool and volume must be rebuilt before a single file appears.
Other NAS platforms we handle
- Asustor (ADM). Btrfs or ext4 over Linux RAID — volume metadata damage after a power cut or a failed upgrade.
- TerraMaster (TOS). ext4 on standard mdadm — often a member that dropped out months earlier, unnoticed until a second followed.
- Buffalo LinkStation and TeraStation. XFS or ext4 with proprietary partitioning — the unit boots into EM mode and will not mount the array.
- WD My Cloud. ext4 on single-bay and mirrored EX2/EX4 units — a corrupt system partition, or one dead disk in a mirror.
- Netgear ReadyNAS. X-RAID with Btrfs — commonly a volume expansion that stalled and is afterwards reported as a dead volume.
Whatever badge is on the box, the lab work is the same: image every member disk, then rebuild the array and file system from those images. If your array sits in a server or a plain enclosure rather than a NAS, see our RAID recovery Singapore guide.
How NAS differs from a single drive or RAID
A NAS combines three layers, and a fault in any of them makes your data inaccessible — but each is recoverable in the lab.
- The disks & RAID layer — usually SHR (Synology) or standard RAID, striping data across bays for redundancy.
- The filesystem — Btrfs or ext4, which can develop corruption independent of the disks.
- The NAS OS — DSM or QTS, which can fail or misreport a healthy volume as "crashed".
Because these layers are proprietary, generic RAID or drive-recovery approaches often fail. We reconstruct them specifically. Related: RAID data recovery.
NAS data recovery, network drive recovery, volume crashed — what people actually mean
People describe this in a dozen ways — the network drive, the shared drive, the office file server, "the Synology". The words matter far less than what is actually inside the box. Here is the plain version.
A NAS is not a big external drive, and it is not quite a server
An external drive is one disk carrying one file system, spoken to by one computer over USB. A NAS is several disks joined into a RAID array, with a Linux file system laid on top, served to your whole network by a small computer inside the enclosure. A server goes further again: it runs applications and user accounts as well as storage. That extra structure is exactly why NAS data recovery differs from single-drive work — there is no one disk you can pull out and read.
"Degraded", "volume crashed", "volume not active" — which is which?
- Degraded. The array has lost a disk but is still running on the rest. Your data is present and readable right now. This is the moment to copy it off — not the moment to rebuild.
- Volume crashed / volume not active. The array, or the file system above it, can no longer be mounted. It reads like a death notice. Usually it is not one: the member disks are typically intact, and it is only the layer above them that needs putting back together.
- Reinitialised or already rebuilt. This is the state that genuinely destroys data, because fresh parity or a new file system has been written across the members. Recovery becomes partial at best.
A NAS is not a backup
RAID protects against one disk dying. It does nothing about a shared folder deleted by accident, a firmware update that goes wrong, a surge that takes the whole unit, or ransomware encrypting every share it can reach over the network. If the only copy of your files lives on the NAS, what you have is redundancy, not a backup.
Common NAS failure causes
Most NAS losses are not one dramatic event. They are a small fault that sat unnoticed for months, followed by something that finally exposed it.
What actually goes wrong
- A second disk fails during the rebuild. The rebuild forces every surviving disk to read end to end for hours — precisely when a tired one gives up.
- Silent bad blocks, found only at rebuild time. Sectors nothing had read since they were written. The array looked healthy because no one had asked for them.
- A firmware, DSM or QTS update gone wrong. The volume becomes unmountable while the data underneath is untouched.
- Accidental volume delete or reinitialise. A share removed during a migration, or a volume reinitialised on forum advice.
- Power loss during a write. Corrupts file system metadata — Btrfs and ZFS are not immune.
- Controller or board failure. The disks are fine; the NAS is dead. Often the easier case, since we read the members outside the enclosure.
- Ransomware over the network. A mapped share is just another drive letter to malware. Snapshots help only if they were out of reach too.
What NOT to do with a crashed NAS
The NAS interface will suggest actions that destroy recoverable data. Please avoid these.
Power the NAS down, label each disk with its bay number, and call us. Preserving the current state gives the highest chance of a full recovery.
Our NAS recovery process
Free diagnosis
We assess each member disk and the array/filesystem, identify the fault, and confirm recoverability — at no cost.
Image every disk
We clone each drive individually first — repairing any physically failed disk in the cleanroom — so the originals are never risked.
Reconstruct the array
We rebuild the SHR/RAID layout and the Btrfs/ext4 filesystem virtually from the images — no reliance on the failed NAS unit.
Extract & verify
We mount the reconstructed volume, extract your shared folders and files, and provide a list to verify.
Secure return
Verified data returned on fresh media, confidentially.
See the full lab walkthrough: how professional data recovery works →
What we can recover — NAS scenarios
Honest ranges, not promises. What decides a NAS case is rarely the brand on the front — it is whether anything was rebuilt before the disks reached us.
| Scenario | Approach | Typical outcome |
|---|---|---|
| Synology SHR, one/two disks degraded (not rebuilt) | SHR + Btrfs reconstruction | High |
| QNAP volume crashed (thin/thick LVM) | QTS/LVM reconstruction | High |
| Btrfs / ext4 filesystem corruption | Filesystem repair from image | High |
| Deleted shared folder | Structure recovery | Good |
| Reinitialised / rebuilt NAS | Assessed individually | Reduced |
Two things move a case down that table. The first is a rebuild or reinitialise attempted before diagnosis — whatever the NAS overwrote while it ran is gone, and how much that costs you depends on how far it got before someone stopped it. The second is volume encryption with the passphrase or key file lost: we can reconstruct the container, but not open it.
Everything else is ordinary lab work. Where members are physically failed, we repair them one at a time in the cleanroom, image each, and rebuild from the images. If a full recovery looks unlikely, we say so at diagnosis.
Dedicated guides: Synology recovery · QNAP recovery.
How much does NAS recovery cost?
NAS recovery is multi-disk, filesystem-level work; cost reflects the number of bays and failure severity.
| Case type | Examples | Indicative range (SGD) |
|---|---|---|
| Simple / single-volume | Single-bay NAS, accidental deletion, lost shares or config, no physical damage | $400 – $900 |
| Logical NAS | Volume crash, filesystem corruption, no physical damage | $1,000 – $2,000 |
| NAS + failed disk(s) | One or more disks need cleanroom repair | $1,600 – $3,200 |
| Large / complex arrays | 4+ bays, encrypted volumes, priority turnaround | $2,800 – $4,000 |
Where a case lands depends on the number of bays, which file system is involved, and whether any disk needs cleanroom work. Anything in the top band is quoted individually after your free diagnosis — we will talk you through exactly what is driving the figure before you commit to anything.
Exact fixed price before work begins. Full detail: data recovery cost guide →
NAS recovery case studies
Representative examples from typical laboratory cases. Anonymised.
Synology SHR — volume crashed
A 4-bay Synology running SHR reported a crashed volume after two disks degraded. The owner nearly reinitialised it. We reconstructed the SHR/Btrfs array from the member disks without touching the original data.
✓ 98% recoveredQNAP thin volume offline
A QNAP QTS thin-provisioned volume dropped after a firmware update. We rebuilt the LVM thin pool and ext4 filesystem from images and restored the shared project drive.
✓ Full recoveryDeleted shared folder under NDA
A finance shared folder was deleted during a migration. We recovered the Btrfs structure and returned the records under NDA within the priority window.
✓ Records recoveredReal NAS recoveries
From verified 5★ reviews on our Google Business Profile. Names as published on Google.
Both mirrored drives failed at the same time
A 2-drive Synology NAS, the drives mirroring each other as backup, holding photos of the owner's children. Both drives died at once — the situation a mirror is supposed to prevent.
Only copy, quoted within half a day
A NAS became inaccessible suddenly and would not come back after a reboot. It was the only copy of the data, so it was taken on as an urgent case, with a quote back within half a day.
Photos and videos off a spoilt NAS
Photos and videos recovered from a spoilt NAS, with service staff described as patient and understanding throughout.
✓ Successful recoveryThese are real reviews from our customers on Google (4.9★ from 909), shown as testimonials.
CBL vs a reseller vs DIY software
Where the disks are actually handled matters more than the number quoted on the first phone call.
| What matters | CBL (in-house lab) | Typical reseller | DIY software |
|---|---|---|---|
| Every member disk imaged first | ✓ Always | Varies | ✗ Reads the live array |
| SHR / Btrfs and ZFS pool rebuild | ✓ In-house | ✗ Outsourced | ✗ Generic RAID only |
| Handles a degraded array safely | ✓ Read-only | Varies | ✗ Can force a rebuild |
| Rebuild attempted on your original disks | ✓ Never | Sometimes | ✗ Routinely |
| Cleanroom repair for failed members | ✓ On-site in Singapore | ✗ Sent away | ✗ |
| Fixed written quote before work | ✓ Yes | Varies | Not applicable |
| Best for | Any crashed NAS or RAID array | Simple single-disk swaps | Healthy NAS, one deleted file, backup exists |
Free diagnosis & a fixed written quote
Free Diagnosis
We assess your NAS and confirm recoverability — no cost, no obligation.
Work Stays In-House
Recovered in our in-house Singapore lab — never shipped overseas.
NDA & Confidential
Business-grade confidentiality, NDAs and proper invoicing.
NAS recovery FAQ
Can you recover a crashed NAS volume?+
Should I reinitialise or repair the NAS?+
Can you recover Synology SHR?+
My Synology says the volume has crashed — is my data gone?+
Should I let the NAS rebuild the array?+
Can you recover a QuTS hero ZFS pool?+
Can you recover a QNAP thin volume?+
Do you need the NAS unit, or just the disks?+
One or two NAS drives failed — is it recoverable?+
How much does NAS recovery cost?+
Do you sign NDAs for business NAS recovery?+
Do I pay if the NAS volume cannot be recovered?+
The bottom line
A crashed NAS is recoverable far more often than the interface makes it seem — but only if the first response is right. Power it down, don't reinitialise, label the bays, and call CBL. With Synology, QNAP and filesystem-level expertise, NDAs, we give your NAS its best chance.