QNAP RAID Degraded? Don't Rebuild Yet.
UK NAS recovery specialists since 2002. QTS, ext4, ZFS and Btrfs. RAID 5/6/10 and JBOD. Trusted by UK enterprises including the BBC, Tesco, HSBC and Williams F1.
What this means and what to do next
A QNAP NAS in degraded state is a moment to slow down, not speed up. QTS (QNAP's operating system) does an excellent job of warning you that something is wrong — typically with an email alert and an amber status indicator on the unit — but the next step matters far more than the speed at which you take it. The instinctive reaction is to slot a fresh disk in, click "Rebuild", and let the NAS sort itself out. In a perfect world that works. In the real world, the rebuild process is the single most stressful thing you can do to your remaining disks, and if any of them have latent bad sectors (which become more common as drives age), the rebuild will fail and the array can drop offline entirely.
QNAP NAS units use Linux MD-RAID under the hood, layered with LVM and a filesystem (ext4 on most older models, Btrfs or ZFS on newer ones). When a disk fails, MD-RAID drops it from the array and continues serving data from the survivors using parity or mirror redundancy. As long as the array is in degraded mode, your data is online — but you've used up your safety margin. A RAID 5 array with one failed disk is now effectively a RAID 0; one more disk failure and the whole array goes offline. That's why it feels urgent. The solution to that urgency, however, is not to do something risky.
What changes the calculation is how long the failed disk had been showing trouble before it was dropped, and what the SMART data on the survivors looks like. If the failed disk had been throwing reallocated-sector errors for weeks before it died, there's a strong chance the survivors are in similar shape. A rebuild on those conditions is gambling. The right move is a free assessment first — we'll image all the disks individually, look at the SMART data, and tell you whether a rebuild on your existing hardware is safe to attempt. If it isn't, we recover from the images instead.
The three most common QNAP "Degraded" scenarios
1. Single disk failed in RAID 5/6 — array still online. The textbook degraded scenario. One disk is showing as failed in the QNAP UI, the volume is still mounted and serving data, and the NAS is asking you to replace the failed disk. This is the safest version of the situation, but only if the surviving disks are healthy. Recovery approach: image all disks individually first (including the "failed" one — it usually has more data on it than QNAP thinks), check SMART, and only then decide whether to rebuild on the original NAS or recover from images to a fresh array. The image-first approach takes longer but is bulletproof.
2. Multiple disk failure — RAID inactive or volume offline. Two disks have failed in a RAID 5, or three in a RAID 6, and the array is offline — QNAP shows "Inactive" or "Volume not mounted". This is past the point that QTS can fix on its own, and the rebuild option may be greyed out. Don't despair: MD-RAID's metadata is on every disk, and the data is striped across all disks, so a forensic reconstruction is usually possible. We image every disk, including the failed ones (which often have most of their data still readable), and reconstruct the array virtually. Recovery rates are typically 95%+.
3. Filesystem-level damage after a QTS update or power cut. The disks are healthy but the filesystem on top has been damaged — typically because a QTS update was interrupted, or a power cut hit during a write, or a disk was hot-swapped without unmounting first. Symptoms: array shows healthy at the RAID layer but the volume won't mount, or mounts read-only with errors. Recovery requires forensic filesystem analysis on copies of the disks (we never operate on the originals) using tools that understand ext4 journals, Btrfs metadata trees, or ZFS uberblocks. Recovery rates here are also typically very high.
How Data Clinic recovers a degraded QNAP RAID
First and most important: we work from images, not the original disks. Each disk is imaged individually using a PC-3000 or Atola DiskSense imager, with bad-sector handling tuned for the specific drive model. The original disks are never written to during recovery and are returned to you untouched at the end of the process. This is the single most important rule of NAS recovery and it's the one that's most often broken — usually by an in-house IT team trying to fix the array on the running NAS.
Once we have full images, we reconstruct the RAID array in software. QNAP RAID is standard Linux MD-RAID with QNAP-specific metadata, so we read the array geometry directly from the on-disk superblocks: stripe size, disk order, parity layout, chunk count. We then virtually assemble the array from the images and expose the underlying logical volume. From there, we mount the filesystem (ext4, Btrfs or ZFS) read-only and extract your files.
When the filesystem is also damaged, we use forensic tools that bypass the normal mount path. ext4 has a journal that can be replayed from a copy; Btrfs has redundant metadata trees that we can fall back to; ZFS has uberblocks that give us multiple filesystem snapshots to choose from. We pick the most complete consistent state and extract everything we can from it. More about our RAID/NAS process →.
Get a free initial diagnosis in 60 seconds
In the tool below, choose RAID / NAS → QNAP → RAID degraded or inactive for the right escalation path.
What our customers say
"Three years of family photos on a drive that suddenly failed. Data Clinic collected next day, kept me updated through the cleanroom work, and got everything back. Worth every penny."
"Honest, fixed-price, no-fix-no-fee. Quoted by another lab at three times the price. Recovered 100% of my files."
"Reasonable cost, clear communication, and they were straight with me about what was recoverable and what wasn't. Recommended."
Frequently asked questions
Can I just hot-swap the failed disk and let QTS rebuild?
If the surviving disks are demonstrably healthy (clean SMART, no recent reallocated sectors, no recent read errors) and your data is critical, a rebuild on the original NAS can work — but it's a gamble. The safe version is to image all disks first, then if the images look clean, do the rebuild. The reckless version is to slot a new disk and click rebuild without looking. We've seen both outcomes more times than we'd like.
How much does QNAP NAS data recovery cost in the UK?
Most QNAP recoveries fall into our standard NAS tier: typically £695–£1,495 including VAT depending on the number of disks, total capacity, filesystem and damage extent. Emergency turnarounds and very large arrays (10+ disks, multi-terabyte) are quoted individually. Free diagnosis. No fee if we cannot recover your data.
Do I need to send the whole NAS or just the disks?
Just the disks is fine — but label them clearly with their bay numbers (1, 2, 3, 4, etc.) before removal. If you're unsure which disk was in which bay, send the whole NAS. Don't change disk order; the recovery depends on knowing which disk holds which RAID stripes.
What about ZFS QNAP units (the QuTS hero range)?
ZFS-based QNAP recovery is more complex but well within our process. ZFS's copy-on-write design means earlier consistent states of the filesystem are preserved on disk even after a more recent state is corrupted, which often gives us more recovery options than ext4 or Btrfs. We work with QuTS hero arrays regularly.
How long does QNAP recovery take?
Standard turnaround is 5–20 working days from receipt of the disks. Two-disk RAID 1 cases often complete in under a week. Large arrays (8+ disks) can take 2–3 weeks. Emergency turnarounds available — call 0800 151 2207 to discuss.
My business is offline because of this. Can you do this faster?
Yes — emergency NAS recovery turns work around in 48–72 hours for an additional fee. We also offer remote recovery in some cases (where we ship images and pre-built recovery profiles to your IT team to mount on a recovery server). Call us first thing in the morning and we'll talk you through the options.