Data Recovery Case File · Creative Professionals · The Veteran Scratch Drive

Nine years of service, one closing error: a Thunderbolt workhorse's -36 refusals, and the last 522GB brought out

The drive in this enquiry had earned its retirement several times over: an 8TB LaCie Thunderbolt, around nine years old, a working footage store for most of a decade. Its decline was the slow-then-sudden kind — it still booted "without issue," but opening folders had gone slow-to-unresponsive, and every attempt to copy files off died partway with the Finder's bluntest storage refusal: "The Finder can't complete the operation because some data can't be read or written (error code -36)." Its owner had responded with an editor's pragmatism: everything already backed up elsewhere, he'd deleted — leaving, by his own careful arithmetic, 522GB of footage that needed saving and existed nowhere else. All of it visible, none of it copyable. A veteran drive, a bounded rescue list, and one error code standing between them.

Decoding -36 — and grading the triage

The error. Code -36 is macOS reporting, in its terse old dialect, an input/output failure: mid-copy, the drive returned reads it couldn't complete, and the Finder — which has no machinery for partial success — abandoned the whole operation. On a nine-year veteran with slowing folder access, the translation is unambiguous: surfaces worn past reliable service, failed reads scattered across the estate, each -36 another patch of tired media meeting a copy that couldn't route around it. The Finder's all-or-nothing temperament is actually the decode's key: files were failing not because they were gone but because whole-file copying has no tolerance for a single bad read — exactly the gap between desktop copying and managed imaging. The triage, graded honestly. His instinct — thin the drive to the sole-copy 522GB so the rescue has a defined target — was editorially sound and operationally generous to us: a stated, bounded priority is worth days. The method carries an asterisk this page must print: deleting from a failing drive is itself writing to it — every removal reworks the same tired filing structures the browsing slowdowns were already reporting — so the ideal version of his move is a list, not a purge: note what's expendable, touch nothing, and let the priorities be honoured at imaging time. His purge did no visible harm, and his arithmetic did visible good; the asterisk stands for the next editor.

The recovery — the 522GB, read the tolerant way

On the PC-3000, the drive got the reading its Finder never offered: error-managed imaging with the 522GB of footage territory prioritised first — mapped from the filesystem and captured ahead of everything else — the equipment doing precisely what -36 announces desktop copying can't: recovering around failed reads, retrying the marginal, bounding the truly dead, and never abandoning a file for a bad sector. The footage came off effectively whole, the honest residue confined to scattered frames' worth of the worst-worn patches, itemised; every clip was verified the way footage must be — played, through its span, not just listed — and delivered on new storage. The wider drive was imaged behind the priority set for completeness, and the nine-year veteran retired formally, its last 522GB delivered where its last error code had held them.

Outcome

The sole-copy footage saved in full — and two closing notes for every creative running veteran scratch storage. First, the error's lesson: -36 and its cousins mean the drive is failing reads, and desktop copying will keep dying at each one — the response is managed imaging, not repeat attempts, and certainly not "try smaller batches," which just discovers the bad patches one abandoned copy at a time. Second, the calendar's: nine years is a magnificent innings for a working drive and roughly twice a sensible one — production storage deserves scheduled retirement while copies are boring, because the slow-folder afternoon always arrives, and it always arrives during a project. His arrived with 522GB uncovered. The next drive gets replaced at year five, he tells us, with the footage's own recovery report as the reminder on the calendar entry.

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.