Data Recovery Case File · Mac & Apple Ecosystem · A Proper Substitution
They Ran the Right Test and They Are Returning the Evidence
His enquiry describes a service visit that did everything correctly. A laptop crashing and failing to recognise its internal drive, where "the store were able to successfully install another drive as a test. I am collecting the machine back tomorrow with the original faulty drive put back in." That is a controlled substitution and a returned component — which together answer the diagnosis and preserve the only thing that matters.
| Media | Internal solid-state drive from a 2012 laptop — not recognised by the host; replacement drive demonstrated working in the same machine by a service provider; original returned |
| Reported situation | Machine crashing and failing to recognise its internal drive · service provider fitting an alternative drive as a test · machine operating normally with the alternative fitted · original drive refitted and returned with the machine · contents required from the original |
| Fault class | Device-level failure confirmed by substitution — host eliminated; drive removable and readable independently of the machine |
| Equipment used | Service provider's substitution accepted as elimination of the host · drive removed and read independently on a matched adapter · enumeration state read under strict timeouts · chip-level read past the controller where indicated |
The decode: why the test was the right one, and why the return matters more
What the substitution established: that the machine works. Its connector, its controller, its power delivery and its firmware all function — demonstrated, not assumed, by fitting a known-good drive and watching it work. That eliminates the entire host in one step, which is the cleanest diagnostic result available.
Why it matters that they did it rather than inferring it: a machine that will not recognise a drive could be failing at either end, and no amount of reasoning separates those. Only substitution does, and it requires a spare drive and the willingness to fit it.
Why returning the original is the important part: a service exchange would have kept it. The standard outcome of a repair is that the faulty component is retained — returned to the manufacturer, refurbished or scrapped — and from a repair perspective that is entirely reasonable, because a failed drive is scrap. It is also the only place the data exists.
So what he is collecting tomorrow: a working laptop is not the point. The point is the drive in the bag, and it is worth confirming before he leaves that it is the original rather than a replacement, and that it has come back rather than been disposed of.
Why this generation is favourable: a machine of that year carries a removable drive on a module connector, so it comes out and reads independently on an inexpensive adapter. The machine's condition stops mattering entirely, which is not true of later designs where storage is soldered and bound to the board.
What the fault is likely to be: a drive that a machine cannot recognise has failed at controller level — the component that presents the storage and holds the mapping between addresses and physical blocks. The memory itself is a separate part and is usually untouched, which is why reading past the controller is the established route.
What must not happen between now and then: no further attempts to boot from it. A drive that fails to enumerate is not improved by being asked again, and each start-up is another opportunity for a controller in difficulty to make things worse.
What is worth asking the store: whether they attempted any repair, initialisation or firmware operation on the original. Anything written to it changes the position.
On the bench
The service provider's substitution was accepted as elimination of the host — an alternative drive demonstrated working in the same machine confirming connector, controller, power delivery and firmware, which reasoning alone cannot establish. The drive was removed and read independently on a matched adapter, that generation carrying removable storage on a module connector so the machine's condition ceases to matter. Enumeration state was read under strict timeouts, with chip-level reading past the controller where indicated.
The outcome
The host eliminated by the store's own substitution, the drive read independently on a matched adapter and the memory read past the controller where required. Free assessment, one fixed written figure including VAT; where a chip has to be removed, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode: their test was the right one and returning the drive matters more. A repair exchange keeps the failed component as scrap — and that component is the only place your data exists.
Collecting a machine after a service diagnosis
Check before you leave that the drive you're getting back is the original — repairs are usually exchanges, the failed component is retained as scrap, and from a repair point of view that's entirely reasonable, except that it's the only place your data exists. The test they ran was the right one: fitting a known-good drive and watching the machine work eliminates the connector, controller, power delivery and firmware all at once, which no amount of reasoning can do. Ask whether they attempted any repair or initialisation on your original, since anything written to it changes the position. And don't try to boot from it again.
Confirm it's the original — then call Oxford Data Recovery on 01865 593000; their substitution accepted as elimination, drive read independently on a matched adapter, memory read past the controller.
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.