Data Recovery Case File · Desktop Externals & Aging Drives · An Inference Worth Copying
He Used a Working Part to Prove Something About a Shared Resource
His enquiry contains a piece of reasoning most people never think to apply. An old machine kept offline deliberately, which would not boot "although the disc drive light flashed on, showing power to the case." The optical drive had nothing to do with the fault — and its behaviour proved that the power supply was working, which eliminated an expensive possibility without any test equipment at all.
| Media | Legacy internal hard drive on an earlier interface generation — host not completing start-up; supply confirmed functional by proxy; drive removed and connected to an alternative machine |
| Reported situation | Machine of considerable age maintained offline · machine not booting · optical drive indicator active on power, confirming supply to the case · hard drive removed by the owner · drive connected to an alternative machine by adapter · contents required |
| Fault class | Host start-up failure with supply eliminated — legacy interface configuration and adapter compatibility to be established before drive condition is assumed |
| Equipment used | Proxy inference accepted as elimination of the supply · legacy interface configuration checked before connection · adapter compatibility confirmed for the interface generation · imaging on a controlled bench supply under strict per-sector timeouts |
The decode: why the inference works, and what it leaves
What he actually did: observed a component he was not interested in, and drew a conclusion about something they share. The optical drive and the hard drive both take power from the same supply — so an optical drive that responds proves the supply is delivering.
Why that is a genuinely good piece of diagnosis: a machine that will not boot has several candidate causes, and the power supply is among the commonest and most expensive to guess at. Eliminating it with an observation rather than a purchase is exactly the right move, and it requires only noticing that one component is alive.
Why the principle generalises: any working component tells you something about everything it depends on. A fan spinning proves the supply; a keyboard light proves the board is initialising; a screen backlight proves the display circuit — and each of those eliminations is free.
What his inference leaves as candidates: the board, the memory, or the drive. And he removed the drive and tried it elsewhere, which is the correct next step and separates the machine's future from the data's entirely.
What the interface generation complicates: drives of that era are configured by small jumpers that set their role on a shared cable. A drive set for one arrangement and connected through an adapter expecting another may be recognised without being readable, or not appear at all — and the settings are unlabelled without the diagram once printed on the drive itself.
Why almost nobody checks this now: the practice ended two decades ago. People connecting old drives through adapters have no reason to know those pins exist, and a drive that seems dead may simply be configured for a machine that no longer exists.
What else to exclude before assuming the drive: the adapter and its supply. Drives of that generation draw more than some adapters deliver, particularly on spin-up, and an underpowered drive behaves like a failing one.
Why a machine kept deliberately offline is worth asking about: it is being maintained because it runs something that cannot be replaced. Which raises the same question as any legacy installation — what does it depend on that is not on the disk.
On the bench
The proxy inference was accepted as elimination of the supply — an optical drive responding on power confirming delivery to components sharing that supply, which eliminates a common and expensive candidate without test equipment. Legacy interface configuration was checked before connection, drives of that generation being configured by jumpers whose settings determine readability and which are unlabelled without the original diagram. Adapter compatibility was confirmed for the interface generation.
The outcome
The supply eliminated by his own inference, legacy configuration and adapter compatibility checked before connection, and imaging performed on a controlled bench supply. Free assessment, one fixed written figure including VAT, 50% of parts and labour upfront with the balance only on successful recovery. The decode: that was good reasoning. Components sharing a supply tell you about each other, so an optical drive responding proves the supply works — which eliminates a common and expensive candidate for nothing.
Diagnosing a machine that will not start
Look at whatever still works and ask what it proves. Components share resources, so a responding optical drive, a spinning fan or an illuminated keyboard all confirm the power supply is delivering — which eliminates one of the commonest and most expensive candidates without buying anything. That reasoning generalises across most hardware faults. If you're then connecting an old drive to a modern machine, two things catch people out: drives from the earlier interface generation are configured by jumpers whose settings decide whether they're readable, and adapters frequently can't supply what a drive draws on spin-up. Both make a working drive look dead.
Note what still works — then call Easy Data Recovery on 028 9002 0144; proxy inference accepted as elimination, legacy configuration and adapter compatibility checked, imaged on a controlled bench supply.
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.