Data Recovery Case File · Working Professionals · Four Years of Career
Registering on nothing, blamed on formatting: the layer confusion decoded in his favour — and the sessions, stems and mixes recovered with their project structure intact
He got to the point, as promised. A Seagate Expansion 1TB that "doesn't register on Mac or Windows at all" — despite living on "a format that supported both" — which left him "really confused on how it just started failing on me." The stakes were his profession: "I'm a music producer and mixing engineer and it has my four to five years' worth of career on there" — just under 500GB, and a priority list any triage bench appreciates: "I mainly want/need my .logic/.logicx/.wav and .mp3 files. I don't really care about any of the other things at all — just my music." And then the sentence that shapes this page: "I understand how these processes work, so I know I'm quite unlikely to have it all recovered." Brave, informed, humble — and, happily, miscalibrated. His pessimism was built on his own diagnosis of "a format issue," and the evidence he supplied argues against that diagnosis. A format problem produces a drive that appears and confuses; his drive wasn't appearing at all — and that distinction runs entirely in his favour.
| Media | Seagate Expansion 1TB — ~500GB in use: four to five years of production sessions, project files, recordings and mixes |
| Reported symptoms | Drive no longer registers on Mac or Windows — no device appears at all · previously on a cross-platform format serving both systems · no incident recalled; sudden onset |
| Fault class | Hardware-layer failure (drive or enclosure electronics) — below the filesystem entirely; the format never on trial |
| Equipment used | Enclosure bypass and native-interface diagnosis · hardware imaging · session-first triage of project files with their bundle structure preserved · verified extraction to new media |
The decode: the layer his diagnosis skipped — and why his humility had the odds upside down
Formats live upstairs: a computer meets a drive in stages. First the device must present itself — hardware announcing "I exist" through the connection. Only then does the system read what's written on it and ask what format is this? A format problem — corruption, incompatibility, a scrambled volume — produces a drive that shows up and then disappoints: visible in the system's disk tools, refusing to mount, offering to be initialised. A drive that registers nowhere on two operating systems is failing downstairs, at the hardware layer, before formats enter the conversation. His cross-platform formatting was never the suspect; it was an alibi the evidence provided for him.
The pessimism, inverted: his "I know I'm quite unlikely to have it all recovered" reads like realism, and the instinct behind it — respect for how these processes work — is genuinely admirable. But the odds run the other way around: it is logical damage (deletions, formats, overwrites) that produces the partial, Swiss-cheese recoveries he was bracing for. Hardware-layer failures on an otherwise unprovoked drive are where this archive's complete recoveries come from — the data sitting untouched behind a component that stopped talking. Expecting the worst is a healthy way to arrive; it's also, in this genre, usually wrong.
The producer's priority list, taken seriously: his file types carry a technical wrinkle worth naming. Project files of the kind he works in aren't single files at all but bundles — folder-structures wearing a file's name, holding audio, edits and settings in a precise internal arrangement. Recover them as loose fragments and the sessions break; recover them structure-intact and years of work reopen exactly as saved. That requirement — structure, not just bytes — decided the method below.
The recovery: past the silent hardware, sessions first
Diagnosis went straight below the format layer: out of the enclosure, onto native connections — where the fault localised to the drive's interface electronics rather than its mechanism, and the platters proved full and healthy behind the silence. The drive was imaged in full, and triage honoured his list in his order: the project bundles first, extracted with their internal structure preserved and spot-opened to confirm sessions loaded; the recordings and mixes behind them; the "things I don't really care about" bringing up the rear anyway, because they were there. Verification was done the way a mixing engineer would want: files opened, sessions launched, audio played.
The outcome
Four to five years of career delivered intact — all of it, in polite defiance of his forecast — with the sessions opening and the masters playing. His cost question received the standing structure: free assessment, one fixed written figure including VAT, no recovery, no fee. The report's closing line was written for the professional he is: a career that fits on one drive deserves to exist on two, and from delivery day onward, his did.
Drive not appearing anywhere — and you suspect the format
Check which layer is actually failing: a format problem shows up and misbehaves; a hardware problem doesn't show up at all. Total non-registration means stop — no reformat offers to accept, no recovery software to run against a device the system can't even see, and no repeated replugging across machines. And if your working files are bundle-type projects, say so when you send the drive in: structure-preserving recovery is a different discipline from file-scraping, and it's the difference between an archive and a career.
That's hardware, not formatting — and the odds are better than you fear. Call Edinburgh Data Recovery on 0131 202 0491; sessions first, one written figure, no recovery, no fee.
Request a quote online →
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.