Data Recovery Case File · NAS & RAID · The Inherited Rig

Two drives, one dead box, twenty-four striped terabytes: a theatre's AV archive, extracted and — as requested — verified

This enquiry came from the head of sound and broadcast at a historic theatre, and it carried the particular burden of inherited infrastructure: a two-bay enclosure holding 2 × 12TB drives configured — "I understand," he wrote, with an inheritor's careful hedge — as RAID 0. The box had been damaged in transport once before; a predecessor had coaxed it back to life; now it greeted power-up with a warning tone, and after methodical troubleshooting with their IT support — the management software couldn't even detect the empty casing with the drives removed — the verdict was a dead enclosure. Their request had three parts, and the third was the wise one: quote for the troubleshooting, quote for replacing the case, and check that the data on the drives is still intact, please.

Reordering the shopping list — data before box

Their three requests arrived in hardware order; the job ran them in data order, for a reason worth stating. Replacing a dead enclosure is cheap and easy — afterwards. Doing it first means seating a 24TB striped pair, with no redundancy and an unverified history that includes physical trauma, into a new controller and asking it to adopt them: a step where a wrong assumption about the stripe, or a "new array" initialisation accepted in a hopeful moment, costs everything the box was bought to hold. So the pair came out first, bays labelled, and both members were imaged write-blocked on the TaskForce 2 — from which point nothing in the case could go backwards. Their team's diagnosis, for the record, graded well: testing whether the software could see the empty casing was a genuinely clever isolation step, and it had correctly convicted the enclosure while sparing the drives every further experiment.

The extraction — and the verification they specifically asked for

In Data Extractor the inherited hedge was resolved from the evidence: the pair's own configuration records confirmed RAID 0, stripe geometry read rather than guessed, and the 24TB volume reassembled offline from the two images — the archive of a working venue rising whole: show recordings, broadcast masters, session files, years of a sound department's output. Then the request most enquiries never think to make, honoured as a deliverable in its own right: verification. Not "it mounts" — the folder tree was walked, file counts and sizes reconciled, and media sampled by actually playing it across the archive's span, oldest to newest, so the written report could say what they'd asked to know: the data is intact, and here is how that was established. Delivery completed the reordering: the archive handed over on plain, redundancy-friendly storage — with the honest note that the striped configuration they'd inherited had been carrying a venue's institutional memory on a no-spare-copy design across at least one transport accident, and that the replacement setup deserved mirroring or backup as a condition of service, not an upgrade for later.

Outcome

Twenty-four terabytes extracted, verified as requested, and re-housed with redundancy — plus a page for everyone who has ever inherited a predecessor's storage. Inherited rigs deserve an audit, not just continued use: establish what the configuration actually is (records beat recollection — this one's owner was right to hedge), what its failure would cost, and whether its design matches those stakes. RAID 0 across two large drives is a performance choice with a specific bill attached, and institutions change postholders more often than they change habits. This customer's instinct — check it's intact before anything else — is the whole audit in one sentence. It just usually needs asking before the warning tone.

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.