Data Recovery Case File · Mac & Apple Systems · Setting It Aside Was Right
A Drive Removed and Kept Is a Drive Nothing Has Written to Since
His enquiry describes a good instinct acted on years ago. An old drive from a machine that crashed and would not restart, which "I removed at the time, as I have a lot of family photos on the drive." Taking the drive out and keeping it was exactly the right thing to do. Whatever the fault, nothing has been written to it since the day it was removed — so the photographs are in the state they were, waiting rather than deteriorating.
| Media | Hard drive removed from an older desktop Mac following a crash — set aside unused; photographic content held |
| Reported situation | Older Mac experiencing a crash and failing to restart · drive removed by the owner at the time · drive kept unused since · substantial photographic content held · contents required |
| Fault class | Undetermined behind a crash symptom — preserved by removal from service; filesystem or device cause to be established without time pressure |
| Equipment used | Removal from service credited as preservation of state · drive read independently on a matched adapter · Apple filesystem structures interpreted with their duplicate copies · imaged write-blocked before any reconstruction · photographic content validated by rendering |
The decode: why the instinct was correct, and what it means now
Why removing the drive helped: a drive left inside a machine that is still in use is exposed to everything that machine does — restarts, repair attempts, an operating system reinstall, or simply being written to. A drive taken out and set aside is exposed to none of that, and its contents are frozen at the moment it was removed.
Why the delay costs nothing here: the drive has sat unused for years, and on a spinning drive that changes nothing about the recording. Magnetic storage holds its data for decades, so the photographs are exactly as they were — the passage of time is not the enemy people assume it to be.
What the original crash could have been: two broad categories. A logical fault — the filesystem left inconsistent by the crash, with the drive itself healthy — or a physical fault, where the drive was failing and the crash was a symptom. Both are addressable, and which it is decides the approach.
Why the logical case is common and hopeful: a machine that crashes and will not restart is frequently a filesystem interrupted mid-write, leaving its structures inconsistent. The data is intact and the map is damaged, and reading the drive elsewhere sidesteps the machine that could not start.
What helps with an older Mac drive specifically: the filesystems used keep duplicate copies of their key structures. Damage to the primary set at the point of a crash is routinely repaired from the duplicates, which is exactly the situation a crash produces.
Why reading it elsewhere is the right route: the original machine's inability to start is not the drive's problem to solve. The drive comes out, connects to another system through an adapter, and is read directly — the crash that stopped the Mac is irrelevant once the drive is examined on its own.
Why photographs are favourable content: even where structures cannot be fully rebuilt, image files have recognisable openings and are recovered by signature. A folder of family photographs is among the more recoverable things a drive can hold.
What must not happen now: no putting it back into a working machine to "see if it reads," and no repair attempts. The drive's preserved state is its great advantage, and it is kept that way until imaged.
On the bench
Removal from service was credited as preservation of state — a drive taken out and set aside being exposed to none of the writing, restarts or repair attempts an in-service drive faces, so its contents are frozen at removal, with magnetic storage holding data for decades irrespective of the intervening years. The drive was read independently on a matched adapter, and Apple filesystem structures interpreted with their duplicate copies, damage at a crash point being routinely repaired from those duplicates.
The outcome
Removal credited as preservation, the drive read independently on a matched adapter, and Apple structures interpreted with their duplicate copies. Free assessment, one fixed written figure including VAT; where a drive has to be opened, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode: taking it out was the right instinct. Nothing has been written to the drive since, so the photographs are preserved rather than deteriorating — and an old Mac filesystem keeps duplicate structures that a crash is routinely repaired from.
A drive you pulled from a dead machine and kept
You did the right thing, and the years haven't cost you anything — a drive taken out and set aside is exposed to none of the writing, restarts or repair attempts an in-service drive faces, so its contents are frozen at the moment you removed it, and magnetic storage holds data for decades regardless. A crash that stopped the machine is usually a filesystem interrupted mid-write, which leaves the data intact and the map damaged, and an older Mac filesystem keeps duplicate structures that exactly this is repaired from. Read it on another system rather than putting it back to test it — the preserved state is its advantage, so keep it that way.
Don't put it back to test it — call Easy Data Recovery on 028 9002 0144; removal credited as preservation, read independently on a matched adapter, Apple structures interpreted with their duplicate copies.
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.