Data Recovery Case File · Portable Drives · Appearing Is Not Recovering
A Drive Brought Back Into View by a Diagnostic Has Not Been Repaired by It
Her enquiry describes a change she reasonably reads as progress. An external drive holding a photo library that was not appearing at all, until "I ran a diagnostic on it and it appeared, but was incredibly slow and non responsive" — and all she wants is to "save my photos to a new hard drive." The appearance is real and it is not an improvement: the drive is now presenting and struggling, which is a narrow window rather than a recovery.
| Media | External hard drive holding a photo library — not presenting initially, presenting after a diagnostic was run, responding extremely slowly thereafter |
| Reported situation | External drive not appearing on the host · diagnostic utility run by the owner · drive appearing subsequently · drive responding extremely slowly · drive largely unresponsive to access attempts · transfer of photographic content to replacement media sought |
| Fault class | Marginal presentation with sustained retry activity — drive reachable but degraded; working window limited and consumed by continued access attempts |
| Equipment used | Presentation treated as a limited window rather than as improvement · further access through the host stopped immediately · drive addressed with imposed timeouts outside any operating system storage stack · imaged incrementally under capped timeouts with photograph regions located and taken first · progress retained across drops |
The decode: what the diagnostic did, and why time is now the constraint
What a diagnostic tool does that a normal connection does not: it waits longer. Where an operating system gives up on a device that does not answer promptly, a diagnostic keeps asking.
Why that can make a drive appear: persistence succeeds where patience runs out. A drive that eventually identifies itself will present to something willing to wait for it.
Why that is not a repair: nothing changed in the drive. It is answering slowly now because it was answering slowly before, and the tool simply outlasted it.
What the extreme slowness reports: retries. Every request is being attempted repeatedly before it succeeds or fails, and each attempt costs a full rotation.
Why that makes the current state a window rather than a condition: retrying is work. A drive spending its time repositioning heads on marginal regions is consuming what remains of it.
Why her instinct to copy the photographs off is right in principle: that is the objective. Getting content onto other media is exactly what should happen.
Why doing it through the computer would fail: a copy stalls. An ordinary file copy meeting a region that will not read waits indefinitely, and when it is cancelled the file is abandoned entirely.
Why that wastes the window specifically: nothing accumulates. Repeated attempts each start over, spending the drive's remaining working time without retaining progress.
What is done instead: incremental capture with limits. Imaging with imposed timeouts abandons a difficult region quickly, records where it was, and keeps everything taken so far.
Why the photographs are located first: priority follows the working time available. The regions holding what she wants are identified from the structures and captured before anything else.
On the bench
Presentation was treated as a limited window rather than as improvement — diagnostic utilities waiting longer than an operating system will, so a drive that eventually identifies itself presents to something persistent without anything having changed within it. Extreme slowness reflects retries, each costing a full rotation and consuming remaining working time. Ordinary file copying stalls indefinitely and abandons files when cancelled, retaining nothing. Imaging proceeded incrementally with progress retained.
The outcome
Presentation treated as a window, host access stopped, and photograph regions captured first under capped timeouts. Free assessment, one fixed written figure including VAT, 50% of parts and labour upfront with the balance only on successful recovery where the drive is opened. The decode: the diagnostic outlasted your drive rather than fixing it. It appears now because something was willing to wait — and the slowness you are seeing is it retrying, which is spending what is left.
When a tool makes a drive reappear
Treat it as a window, not a recovery, and stop copying files through the computer. A diagnostic makes a drive appear by waiting longer than the operating system will — nothing about the drive changed, and the extreme slowness you're seeing is it retrying every request, which consumes what working time remains. An ordinary copy stalls on a bad region and abandons the file when cancelled, so repeated attempts spend that window and accumulate nothing.
Don't start copying — call Cambridge Data Recovery on 01223 655015; presentation treated as a limited window, addressed outside the operating system stack, photograph regions captured first with progress retained.
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.