Data Recovery Case File · Mac & Apple Ecosystem · The Drive Comes Out Regardless
Age Explains Why It Was Likely, Not What Actually Happened
Her enquiry supplies its own explanation and it is not one. A machine that "has just died a death — it gets stuck in a start-up loop and never manages to load. Because it was so old, and the operating system so out" of date. Machines do not fail because they are old. They fail because a specific component fails, and age raises the odds without ever being the cause — which matters, because "it was old" is how a recoverable machine gets written off.
| Media | Internal drive from an all-in-one desktop machine of considerable age — host entering a repeating start-up cycle without completing; operating system several generations behind |
| Reported situation | Machine of considerable age no longer starting · start-up beginning and restarting repeatedly without completing · operating system substantially out of date · contents required |
| Fault class | Start-up failure with storage responding — loop indicating partial load; drive removable and readable independently of the host |
| Equipment used | Age recorded as context rather than accepted as diagnosis · loop behaviour interpreted as evidence the drive is being read · drive removed and read independently of the machine · imaged write-blocked on a matched adapter · structures rebuilt from surviving copies |
The decode: what a loop proves, and why the machine stops mattering
Why age is not a fault: a machine that has run for a decade and one that has run for a year both fail in the same ways — a drive, a supply, a board component. Age changes how likely each of those is and not what any of them are, so "it was old" describes the context rather than the problem.
Why that matters practically: because attributing a failure to age leads to writing the machine off, and writing the machine off leads to writing the contents off with it. Those are separate decisions and only one of them is forced.
What a start-up loop actually establishes: the machine powers, initialises, begins loading the operating system, meets something it cannot proceed past, and restarts. Loading requires reading — so the drive is powering up, responding, and returning data, right up to the point where the system gives up.
Why that is a considerable amount of good news: a drive that will not respond at all produces a very different symptom. Hers is working well enough to load part of an operating system, which places this among the recoverable situations rather than the difficult ones.
What the loop is likely to be: a damaged system file or filesystem inconsistency that halts the load at the same point every time. The restart is the system's own response to failing to proceed, and it will repeat indefinitely because nothing changes between attempts.
Why the machine's future is irrelevant to the data: the drive is a separate component. It comes out and reads on another computer entirely, and whether this machine ever starts again has no bearing on that. She can retire it and keep the contents.
What the design adds on a machine of that type: the drive is removable, and reaching it means dismantling the display assembly. That is a workshop operation rather than a kitchen-table one, and the panels are glass — which is why it is worth having done rather than attempted.
What must not happen meanwhile: no repeated restarting to see whether it will get further. It will not, and each cycle is another set of reads on a drive that has already failed to satisfy one.
On the bench
Age was recorded as context rather than accepted as diagnosis — machines failing through specific component failures whose likelihood age alters without age constituting the fault, so attributing loss to age leads to writing off contents that remain intact. Loop behaviour was interpreted as evidence the drive is being read, loading requiring successful reads up to the point of failure. The drive was removed and read independently of the machine and imaged write-blocked on a matched adapter.
The outcome
Age treated as context, the loop read as evidence of a responding drive, and the contents recovered independently of the machine. 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: age is why it was likely, not what happened. And a start-up loop means the machine reads the drive far enough to begin loading — so your storage is responding, and it reads elsewhere whether or not this machine ever works again.
Old machine that has stopped starting
Stop restarting it, and separate two decisions that feel like one. Retiring the machine and losing what's on it aren't the same choice — the drive is a component, it comes out, and it reads on another computer regardless of whether this one ever works again. Age isn't a diagnosis either: machines fail through specific component failures, and age changes how likely those are without being the cause, so "it was old" describes context rather than a problem. Take encouragement from the loop, too. Loading requires reading, so a machine that starts and restarts is one whose drive is responding.
The drive is a separate question — call Oxford Data Recovery on 01865 593000; loop read as evidence of a responding drive, storage read independently of the machine, structures rebuilt from surviving 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.