Data Recovery Case File · Desktop Externals & Aging Drives · A Test Worth Doing
Connecting the Drive Directly Removed the Commonest Cause in One Step
His enquiry reports a test performed correctly and asks a practical question that deserves a direct answer. An external drive that stopped working, where he "tried removing the actual drive and attaching that directly to our PC, but it isn't recognised" — and he asks whether they should supply another drive for the recovered content. The test he ran is the right one, and the answer to his question is yes, with three specifics.
| Media | External hard drive removed from its enclosure and connected directly to a host — not enumerating either way; destination media to be supplied |
| Reported situation | External drive ceasing to work · drive removed from its enclosure by the owner · drive connected directly to a computer · drive not recognised when connected directly · physical damage suspected by the owner · guidance sought on cost and on supplying destination media |
| Fault class | Device not enumerating with the enclosure eliminated — fault confirmed as drive-side; board, firmware-stage and mechanical causes open |
| Equipment used | Enclosure eliminated by the owner's direct connection test and not repeated · current draw measured across the start-up cycle on a controlled bench supply · service area read under strict timeouts · imaged write-blocked once enumeration was achieved · content delivered to supplied destination media |
The decode: what his test proved, and what to send with the drive
Why removing the drive from the enclosure is the single most useful thing an owner can do: it eliminates a whole category. Enclosure electronics, the connector and the supply are the commonest reason an external drive stops presenting, and they are also the cheapest to fix.
What his result establishes: the fault travels with the drive. Connected directly, without the enclosure's conversion board in the path, it still does not present — so nothing about the housing explains it.
Why that saves time rather than merely tidying up: it is a test that would otherwise be performed on the bench. He has removed the good outcome and the cheap one, which is worth knowing before quoting.
Why physical damage is not the only remaining explanation: three causes produce this. A board fault, a firmware-stage failure, and a mechanical fault all present as a drive that does not announce itself — and only the third involves physical damage.
Why that matters for expectations: two of the three leave the recording untouched and need no donor parts. His suspicion of physical damage is the least likely of the three rather than the most, and it costs nothing to establish which applies.
The first specific about destination media — capacity. It should comfortably exceed the source. A recovery of a full drive needs somewhere to put all of it, and margin for structures that expand.
The second — it must be empty and stay empty. A destination drive should hold nothing else. Using a drive that already carries data introduces a second thing to lose, and it should not be a drive with the only copy of anything.
The third — format is worth agreeing rather than assuming. A destination prepared for one platform may not be readable on another. It is better settled at the outset than discovered at collection, and a drive need not be formatted in advance at all.
Why supplying media is generally worth doing: it is cheaper than buying one as part of the work, and he keeps it afterwards. A new drive is the sensible choice, since a used one of unknown history is a poor place to put recovered content.
What must not happen meanwhile: no repeated connection attempts, and no further disassembly. He has done the useful part, and the next step is measurement rather than another connection.
On the bench
The enclosure was eliminated by the owner's direct connection test and not repeated — enclosure electronics, connector and supply being the commonest reason an external drive ceases to present and the cheapest to address, so a drive not enumerating when connected directly confirms the fault as drive-side. Three causes remain open: board fault, firmware-stage failure and mechanical fault, of which only the last involves physical damage. Current draw was measured across the start-up cycle.
The outcome
The enclosure eliminated by the owner's own test, draw measured across the start-up cycle, and content delivered to supplied destination media. 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: your test removed the commonest cause in one step. Three explanations remain, and physical damage is the least likely of them rather than the most.
Supplying a drive for your recovered files
Send a new one, and check three things: that its capacity comfortably exceeds the source, that it is empty and holds the only copy of nothing, and that its format suits the machine you'll read it on — settle that at the outset rather than discovering it at collection. It needn't be formatted in advance. Meanwhile, taking the drive out of its enclosure and connecting it directly was the right test: it eliminates the enclosure electronics, connector and supply, which are the commonest and cheapest cause. Stop reconnecting it now.
Send a new empty drive with it — call Manchester Data Recovery on 0161 871 0788; enclosure eliminated by your own test, draw measured across the start-up cycle, content delivered to supplied media.
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.