Is a QNAP hard to recover from?

Less than people expect. Underneath the interface it is standard Linux storage — mdadm, LVM and ext4 — so once the disks are imaged the reconstruction is conventional and the appliance becomes irrelevant.

What is thin provisioning and why does it matter?

A thin volume reports a size it has not actually reserved, allocating space only as data is written. If the underlying pool fills, writes fail while the volume still shows free space — and the file system can be left with structures half-written.

Our QNAP will not mount its volume after a power cut. Is the data gone?

Usually not. That is normally ext4 damage from an interrupted write, which is conventional logical damage rebuilt from the file system’s own backup superblocks. The disks themselves are typically fine.

The unit died but the disks look fine. Can they be read elsewhere?

Yes. Because every layer is standard Linux storage, the array can be assembled and the volume mounted entirely outside the appliance. A dead QNAP with healthy disks is one of the better outcomes.

Should we let it rebuild after replacing a disk?

Copy your data off first. A rebuild reads every sector of every surviving member for hours — the heaviest load the array ever sees, applied to disks the same age as the one that just failed.

What does QNAP recovery cost?

From £500 plus VAT after a free 48-hour diagnostic, with a 50% deposit where a member needs physical drive-level work. Send the disks labelled by bay or the complete unit.

QNAP · NAS recovery

A QNAP is four storage layers stacked on each other.

Linux software RAID underneath, an LVM thin pool above it, then the file system, then the shares. A fault at any level surfaces as nonsense several levels up, which is why the error you see rarely names the layer that actually failed.

NAS recovery →01223 655015

RAID 0, 1, 5, 6 & 10

Thin pools & snapshots

From £500 +VAT

// the short version

The disks are rarely the problem.

QNAP stacks a storage pool, and often thin provisioning, on top of the RAID. A volume can disappear entirely while every disk underneath is in good health, so recovery means unwinding those layers in order.

mdadm

Underlying RAID

LVM

Pool layer

48 hr

Free diagnostic

£500

From, +VAT

×Don’t let the QNAP re-initialise the pool or start a rebuild. Recovering a volume is straightforward while the underlying metadata is intact; once the unit has written a fresh pool over it, a great deal of that advantage is gone. Power it off and send the disks in bay order.

// qnap

Thin provisioning is the complication.

QNAP units run mdadm software RAID like most NAS hardware, but with an important addition: LVM thin provisioning sits between the array and the file system on most configurations. That extra layer is where QNAP recoveries differ from Synology ones.

Thin provisioning means storage is allocated on demand rather than up front, and a mapping table records which physical extents belong to which logical volume. When that table is damaged, the array can be perfectly healthy and the volume still unmountable — the blocks are all there and nothing knows what belongs where.

So a QNAP job frequently has two stages: reassemble the array, then rebuild the thin provisioning map before the file system is reachable at all.

// families we see

The ranges that reach this bench.

TS-251D, TS-253D Two-bay consumer and small office units. The most common QNAP we see.

TS-453D, TS-464 Four-bay business units. Usually the whole company file store, frequently with no offsite copy.

TS-h series ZFS-based models. A different underlying layout requiring every vdev member present.

TVS series Higher-end multi-bay with SSD caching. The cache tier adds a further layer to reconstruct.

TR expansion units JBOD enclosures attached to a head unit. Send both together — the configuration lives on the head.

Rackmount TS-x83 and TS-x77 Business rack units out of science park and estate server rooms.

// what not to do

Three prompts worth declining.

QTS will offer to recover, rebuild or initialise a degraded volume, and each of those writes to the array. On a unit whose thin provisioning metadata is damaged, an initialise is final.

Do not remove and reinsert disks to test them either. Bay order is part of the array structure, and a reinsertion can trigger a rebuild you did not intend. Power the unit down, photograph the front, label each disk with its bay, and send every member including any that were already showing as failed.

// questions

Answered.

Frequently thin provisioning metadata rather than disk failure. The array may be entirely healthy. Do not let QTS attempt a repair.

Usually recoverable. The second has often been ejected on timeout rather than failing outright. Send every disk labelled by bay.

Sometimes, and it can also trigger an initialisation that ends the matter. Not worth the risk if the data matters.

The disks are readable without it. QNAP arrays reassemble on other hardware, so a dead chassis is rarely a lost volume.

From £500 +VAT for multi-bay units, fixed in writing after the free 48-hour diagnostic.