NAS Symptom Recovery
QNAP Dead Chassis Data Recovery
You pressed the power button and nothing happened. The fans stay silent, the front LEDs never light, and the unit never appears on the network. It is a brick with your archive inside it.
Your files sit on partition 3 of every drive in the array. The firmware lives somewhere else, on a separate flash chip on the mainboard.
The danger in this failure is not the dead box. It is what happens in the next hour, when the drives get dropped into a replacement chassis that offers to initialize them.
Is my data gone if my QNAP won't power on?
Your data and the firmware live in different places. QNAP stores your files on partition 3 of every member drive and its firmware on a Disk on Module flash chip on the mainboard. We image every member read-only, then reassemble the array offline. Do not connect the drives to a Windows PC and do not click through a setup wizard in a replacement chassis.
What Fails When a QNAP Chassis Goes Dark
A QNAP is a small Linux computer bolted to a drive cage. When it stops powering on, the computer died. The storage is a separate set of parts that the dead computer can no longer talk to.
DOM flash holds the firmware, not your files
QNAP boots from an internal Disk on Module: a flash chip on the mainboard. It is physically separate from the drives in the bays.
A DOM that fails on its own is a different symptom with a different starting point. If your unit died during or right after a firmware update rather than going dark on its own, read what a firmware update that never wrote cleanly to the DOM does to a QNAP instead. That path starts at the boot device; this one starts at the power rails.
A dead unit is not a unit that boots badly
Figure out which of these two you're looking at before you do anything, because they call for different first moves.
A unit that stays completely dark, with no fan spin and no POST, is the case this page covers.
A unit that boots, reaches the web interface, and then drops a bay or reports an empty pool is a QNAP that still runs but stopped recognizing its drives.
Where Your Files Actually Live on a QNAP Member Drive
QNAP splits every member drive into system partitions and one large data partition. Partition 1 holds the configuration database that maps your storage pools to the underlying arrays. Partition 3 holds your files.
Those two layers fail independently, which is documented on the other end of the same architecture: a corrupted partition 1 desynchronizes the management interface while the user data on partition 3 stays completely intact.
| Where it lives | What it holds | Effect of a dead chassis |
|---|---|---|
| Partition 1 of each member | Configuration database mapping storage pools to the underlying mdadm arrays. | We don't need it to reassemble the array. |
| Partition 3 of each member | Your data. An mdadm array under LVM under ext4 on QTS. | On QTS, the mdadm superblocks here are enough to assemble the array without the chassis. |
Array metadata is written to the member drives themselves, not held hostage inside the enclosure. On QTS that metadata is the mdadm superblock on partition 3, carrying the RAID level, chunk size, layout, member order, and data offset. On QuTS hero it is the ZFS vdev labels. Either way it travels with the disks.
Initializing a QNAP Member in Windows Erases It
Never let Disk Management initialize a QNAP member drive. Microsoft says initializing a disk erases all the data on it.
The instinct is reasonable. The drives are healthy, you own a computer with SATA ports, and the obvious move is to skip the middleman.
What to do if you already clicked Initialize
A drive's partition table is what marks where partition 3 begins and ends. The mdadm superblock for your data array lives inside partition 3, not on the raw drive outside it.
If you already clicked it, stop there. Do not format, do not run a repair tool, and do not write anything else to those drives. Power the machine down and get in touch before anything else lands on the disk.
Consumer scanners aim at the wrong layer
Software that scans a single drive for file signatures is looking at one member of a striped or parity set. On a striped or parity QTS array, any given file is spread in chunks across several members according to a layout and rotation recorded in the mdadm superblock. Reading one member in isolation returns fragments.
RAID 1 is the exception. Every member of the mirror holds the same data.
Moving QNAP Drives Into a Replacement Chassis Risks Initialization
A simple chassis power supply failure with healthy members is where moving drives into another unit can genuinely work. It stops working the moment the destination unit does not recognize what it found, because the flow it offers you next is the one that overwrites the array.
Forum advice to buy a new box and move the disks is not wrong in every case. It is wrong in the cases where the original crash came from metadata corruption, and it is dangerous in every case where the user clicks whatever the wizard suggests.
That hazard is not specific to QNAP, and if the dead enclosure in front of you carries a different badge, start from our recovery service for NAS arrays from other brands.
Which prompts in a migration flow end an array?
The prompts that end arrays are the ones that offer to initialize the disks or create a new storage pool.
QTS members do not migrate into a QuTS hero unit
These are two different filesystems, not two settings of one. QTS writes an mdadm array with LVM and ext4 on partition 3. QuTS hero replaces that entire stack with a native OpenZFS pool.
A QuTS hero unit handed a set of QTS members has nothing it can import. What it does have is a setup flow, and that flow ends in the initialization prompt. Buying a replacement without checking which operating system your dead unit ran is how people arrive at that screen.
The reverse direction fails for the same structural reason. If you are not certain which side you are on, our QuTS hero ZFS page covers the pool-side stack in detail, and the QNAP recovery hub covers the split across both product lines.
A safer order of operations if you own a second chassis
Image the members first, then try the chassis. Once there are read-only clones, the worst a migration attempt costs you is an afternoon. It doesn't cost you the archive. The wizard can only write to the drives sitting in the chassis, and it can't touch the images.
If you go ahead without images and the destination unit shows the array as degraded, as unrecognized, or offers any prompt to initialize, restore, or create: power the unit off at that screen. Do not click through to see what happens next.
QTS and QuTS hero Take Different Recovery Paths
Which operating system your dead unit ran decides every command that follows. QTS reconstruction is an mdadm and LVM job.
QTS offline assembly on mdadm and LVM
Working from clones rather than originals, we read the superblock on partition 3 of each member with mdadm --examine. That single read reports the RAID level, chunk size, layout, member order, and data offset.
The array then comes up read-only with mdadm --assemble --readonly.
When event counts disagree between members and mdadm refuses to auto-assemble, the geometry is reconstructed with Data Extractor Express RAID Edition on the PC-3000 Express rather than forced together with a create command. We do not write new superblocks onto a recovery target.
Safe Handling Steps Before You Ship the Drives
Leave the unit off and pull the drives cold, with the bay numbers written on them before they move.
- Unplug it and leave it unplugged.
- Label every drive with its bay number. Masking tape and a marker, written before the drive leaves the cage. Member order is recorded in the metadata, so this is belt and braces rather than the only record, but it removes ambiguity from the reconstruction and from any attempt to reinstall the set later.
- Do not attach the drives to a Windows PC. If Disk Management ever offers to initialize one, say no. Initializing erases all the data on the disk.
- Do not click through a setup wizard in another chassis. If you have already put the drives in a replacement unit and it is asking to initialize, restore, or create a storage pool, power it off at that screen without answering.
- Ship the drives, not the enclosure. Wrap each drive individually in antistatic packaging and pack them so nothing shifts in transit. Our mail-in instructions cover packing, and every step of the work happens at our Austin, TX lab.
The array in that chassis was never a backup. RAID provides hardware availability and uptime. It doesn't provide data protection. Once your files are back, a discrete offline copy somewhere else is the part that was actually missing.
How We Recover a QNAP That Never Powers On
We image every member drive before we attempt any assembly, and all reconstruction runs against those images. Your original drives are never mounted read-write.
- Free evaluation and stack identification. We record the model, the member count, the bay order you labelled, whether the unit ran QTS or QuTS hero, and anything already attempted on the drives. Prior attempts change the plan, so tell us about them rather than around them.
- Read-only imaging of every member. We clone each drive with DeepSpar Disk Imager or PC-3000 Portable III. A member that turns out to have bad sectors gets handled with the appropriate tier of work before it holds up the array.
- Metadata capture from partition 3. For QTS we read the mdadm superblocks off the clones to capture RAID level, chunk size, layout, member order, and data offset.
- Offline assembly on a Linux workstation. We assemble QTS arrays read-only.
- Extraction, verification, and delivery. We copy your files out, check them against what you told us to look for, and write them to your target media. Working copies are securely purged on request.
All of it happens in one building. Rossmann Repair Group was founded in 2008. We work out of a single lab in Austin, Texas, with no franchises and no outsourcing. If a member drive does turn out to need platter or head work, it gets that work here, on our own clean bench, rather than being forwarded somewhere.
How Much Does Dead-Chassis QNAP Recovery Cost?
Cost is per member drive for imaging, multiplied by the number of drives imaged, plus a $400-$800 array reconstruction fee for the offline assembly. A member drive that reads healthy falls in the Simple Copy tier: From $100 per drive.
Each evaluated member gets its own line item at the tier its condition earns, so a set where one drive has bad sectors and the rest read clean is priced accordingly rather than at a single flat rate. Helium-filled enterprise members start at $200 per drive instead. +$100 rush fee to move to the front of the queue.
- Low complexity
Simple Copy
Your drive works, you just need the data moved off it
Functional drive; data transfer to new media
Rush available: +$100
$100
3-5 business days
- Low complexity
File System Recovery
Your drive isn't recognized by your computer, but it's not making unusual sounds
File system corruption. Accessible with professional recovery software but not by the OS
Starting price; final depends on complexity
From $250
2-4 weeks
- Medium complexity
Firmware Repair
Your drive is completely inaccessible. It may be detected but shows the wrong size or won't respond
Firmware corruption: ROM, modules, or translator tables corrupted; requires PC-3000 terminal access
CMR drive: $600. SMR drive: $900.
$600–$900
3-6 weeks
- High complexity
Head Swap
Bench diagnosis found the read/write heads have to be replaced. Clicking can also come from firmware, the preamp, or the spindle
Head stack assembly failure. Transplanting heads from a matching donor drive on a clean bench
50% deposit required. CMR: $1,200-$1,500 + donor. SMR: $1,500 + donor.
50% deposit required
$1,200–$1,500
4-8 weeks
- High complexity
Surface / Platter Damage
Your drive was dropped, has visible damage, or a head crash scraped the platters
Platter scoring or contamination. Requires platter cleaning and head swap
50% deposit required. Donor parts are consumed in the repair. Most difficult recovery type.
50% deposit required
$2,000
4-8 weeks
Hardware Repair vs. Software Locks
Our "no data, no fee" policy applies to hardware recovery. We do not bill for unsuccessful physical repairs. If we replace a hard drive read/write head assembly or repair a liquid-damaged logic board to a bootable state, the hardware repair is complete and standard rates apply. If data remains inaccessible due to user-configured software locks, a forgotten passcode, or a remote wipe command, the physical repair is still billable. We cannot bypass user encryption or activation locks.
No data, no fee. Free evaluation and firm quote before any paid work. Full guarantee details. Head swap and surface damage require a 50% deposit because donor parts are consumed in the attempt.
- Rush fee
- +$100 rush fee to move to the front of the queue
- Donor drives
- Donor drives are matching drives used for parts. Typical donor cost: $50–$150 for common drives, $200–$400 for rare or high-capacity models. We source the cheapest compatible donor available.
- Target drive
- The destination drive we copy recovered data onto. You can supply your own, or we'll provide one. For larger capacities (8TB, 10TB, 16TB and above), target drives cost $400+ extra. All prices are plus applicable tax.
Sealed helium drives are on their own price list, $200–$5,000+. When a head swap or platter repair opens one, we refill it with helium. That adds $400–$800, and the donor has to be an exact match. Helium drive prices
Donor drives are matching drives used for parts. Typical donor cost: $50–$150 for common drives, $200–$400 for rare or high-capacity models. We source the cheapest compatible donor available.
There is no diagnostic fee to evaluate the array, and there is no recovery fee if we recover nothing. Pricing is published rather than quoted after the fact.
Data Recovery Standards & Verification
Our Austin lab operates on a transparency-first model. We use industry-standard recovery tools, including PC-3000 and DeepSpar, combined with strict environmental controls to maintain drive integrity. This approach allows us to serve clients nationwide with consistent technical standards.
Localized Clean Zone
Open-drive work is performed in a 0.02 micron ULPA-filtered laminar clean bench.
Transparent History
Serving clients nationwide via mail-in service since 2008. Our lead engineer holds PC-3000 and HEX Akademia certifications for hard drive firmware repair and mechanical recovery.
Media Coverage
Our repair work has been covered by The Wall Street Journal and Business Insider, with CBC News reporting on our pricing transparency. Louis Rossmann has testified in Right to Repair hearings in multiple states and founded the Repair Preservation Group.
Aligned Incentives
Our "No Data, No Charge" policy means we assume the risk of the recovery attempt, not the client.
Technical Oversight
Louis Rossmann
Our engineers review all lab protocols to maintain technical accuracy and honest service. Since 2008, his focus has been on clear technical communication and accurate diagnostics rather than sales-driven explanations.
We believe in showing the bench rather than just describing it. Open-drive work runs on a 0.02 micron ULPA-filtered laminar clean bench, and we filmed it.
See the particle counter test at the benchQNAP Dead Chassis Recovery FAQ
My QNAP won't power on at all. Is my data gone?
Your files and the firmware live in different places. The files sit on partition 3 of every member drive, and the firmware lives on a separate Disk on Module flash chip on the mainboard.
Can I just plug my QNAP drives into a Windows PC and copy the files off?
Don't attach them to a Windows PC. On QTS, partition 3 holds Linux software RAID (mdadm), with LVM on top of that and an ext4 filesystem on top of LVM. If a drive does end up attached and Disk Management offers to initialize it, say no. Microsoft says initializing a disk erases all the data on it.
Can I move the drives into a replacement QNAP chassis?
A straight power supply death with healthy members is where a chassis move can work, and QNAP publishes a migration path for it. It is disastrous where metadata corruption caused the crash. What ends arrays is the wizard that appears when the destination unit does not recognize what it found. That wizard offers to initialize the disks or create a new storage pool. If the array matters more than the convenience, image the members first and treat the chassis move as optional.
Will drives from a QTS unit work in a QuTS hero unit?
No. QTS writes an mdadm array with LVM and ext4 on partition 3. QuTS hero writes a native OpenZFS pool. They are different on-disk formats, so a QuTS hero unit has nothing to import from a QTS member set. A destination unit that finds a layout it cannot read is exactly the unit that offers to initialize.
Do I need another QNAP to read my array?
The metadata that describes a QNAP array is written to the member drives themselves, not held inside the chassis. On QTS we read the mdadm superblocks on partition 3 and assemble the array read-only.
Should I keep pressing the power button to see if it comes back?
Stop. If the unit came up once and then died again, that is not encouragement. Leave it off, unplugged, and pull the drives with the unit cold.
Does it matter which bay each drive came out of?
Yes. Label every drive with its bay number before it leaves the chassis. Member order is recorded in the mdadm superblock on QTS and in the ZFS vdev labels on QuTS hero, so order is recoverable from the metadata, but a labelled set removes an entire class of ambiguity from the reconstruction and from any later attempt to put the drives back. Masking tape and a marker are enough.
My QNAP powers on but never finishes booting. Is that the same failure?
No, and it changes what we look at first. When a failed firmware update leaves the unit showing empty or uninitialized storage pools, it's the configuration database on partition 1 that got corrupted. Your data on partition 3 is still intact.
My drives are encrypted. Does a dead chassis change that?
It changes nothing about the encryption and everything about who can unlock it. QTS can encrypt individual shared folders with eCryptfs or whole volumes with AES-256. You still need your passphrase or the exported key material to unlock it. Tell us the unit was encrypted before you ship it, because the reconstruction and the unlock are separate steps.
Did RAID not protect me from this?
RAID protects against a member drive dying while the array keeps serving. It provides availability and uptime, not data protection. A dead chassis, a deleted directory, ransomware, or a batch of drives that all age out together will take every member of the array at once. Redundancy inside one enclosure was never a backup. An offline copy stored somewhere else is.
What does recovery from a dead QNAP chassis cost?
Imaging is priced per drive, and you pay it for each drive we image. On top of that there's a $400-$800 array reconstruction fee for the offline assembly. A member drive that reads healthy falls in the Simple Copy tier: From $100 per drive. Helium-filled enterprise members start at $200 per drive instead. +$100 rush fee to move to the front of the queue. Donor drives are matching drives used for parts. Typical donor cost: $50–$150 for common drives, $200–$400 for rare or high-capacity models. We source the cheapest compatible donor available.. There is no diagnostic fee, and there is no recovery fee if we recover nothing.
How do I ship a NAS full of drives to you?
Ship the drives, not the box. Label each one with its bay number, wrap each drive individually in antistatic packaging, and pack them so nothing shifts in transit. The dead chassis stays with you unless we ask for it. Mail-in instructions and packing guidance are on our mail-in page, and every step of the work happens in our Austin, TX lab.
Since 2008
Established
As Featured In
Related services
Need Recovery for Other Devices?
QTS, QuTS hero, ZFS pools
Unit boots but a bay drops out
Unbootable after a DOM flash write
Solid red status LED on the chassis
All NAS brands and RAID types
RAID 0, 1, 5, 6, 10 arrays
QNAP won't power on?
Leave it off, label the bays, and ship the drives. Free evaluation. No data, no fee.