Data Recovery Case File · Home NAS · Triage Done Right

NAS fine, drive silent: a dropped Synology's 16TB disk, isolated by its owner and recovered beneath the software floor

This enquiry arrived with the diagnosis already three-quarters done, and done well. The owner had dropped his entire Synology unit — a single-bay-populated DS423+ carrying one 16TB drive — while it was powered off. His response was a clinic in isolation: he tested the NAS itself with a clean spare drive and confirmed the unit still works; he tried the 16TB drive in his external enclosures, where it wasn't recognised at all; and, knowing Synology volumes aren't ordinary Windows disks, he downloaded specialist Btrfs software to read it — which also saw nothing. "Are you able to help me with this please?" Yes — and the first help is explaining why that carefully-chosen last step was never going to work.

Grading the triage — and the jurisdiction line his last step crossed

Two of his three steps were textbook. Testing the chassis with a sacrificial drive cleanly split the question — NAS or disk? — and answered it: disk. Trying enclosures established the silence followed the drive everywhere. The third step failed for a reason worth a paragraph, because it's a subtle version of a boundary this archive keeps mapping: filesystem software — however specialist — can only read a drive that presents itself. Btrfs tooling was exactly the right idea for the next problem (a Synology volume's Linux-native layers are unreadable to Windows, and he'd correctly anticipated that); but his drive wasn't presenting a confusing filesystem — it wasn't presenting at all. No enumeration means software of every kind is looking at an empty doorway; the fault sat below its floor, in the mechanics a fall disturbs. The one mercy in his account: the unit was powered off when it fell — heads parked on their ramp, platters stationary — which is the survivable version of a drop, typically costing mechanical alignment or head health rather than the scored surfaces a spinning fall risks. His drive's total silence fitted that profile: a mechanism jolted past its ability to start its own conversation, over platters that never took a direct hit.

The recovery — hardware first, then the layers he'd anticipated

Under laminar airflow the impact's bill was confirmed and paid: the drive's mechanical fault addressed with donor attention, and the 16TB brought up on the PC-3000 for full imaging at post-impact tempo — patient, complete, nothing left for a second session. Then his Btrfs instinct got its vindication, one level up: on the image, the Synology's layered architecture was assembled exactly as the DS423+ would have built it — the system partitions, the storage-manager layer, and the Btrfs volume innermost — and his data rose whole: the household's files, verified by opening them across the set, delivered on a plain external drive readable by any computer, no NAS required. The DS423+ he'd proven healthy goes back into service with a new drive — and, per the delivery note, ideally a second bay populated this time, since the drop also proved the single-disk configuration's whole risk profile in one short fall.

Outcome

Full recovery — and a template this page happily promotes: his triage sequence is exactly what to do, with one amendment at the end. Isolate with a spare drive; confirm the fault follows the disk; and when a drive won't even enumerate, stop downloading tools — no software reaches below that line, and repeated connection attempts across enclosures ask a wounded mechanism to keep failing its start-up. The amendment costs nothing: after the isolation, power nothing further, and let the hardware conversation happen on a bench. He'd done the thinking; the drive just needed the one kind of help thinking can't provide.

Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.