Data Recovery Case File · Desktop Externals & Aging Drives · It Starts and Stops
Activity That Begins and Stalls Is a Drive Reading Until It Reaches Something It Cannot
His enquiry contains a detail that settles a great deal. A laptop drive removed and mounted externally, which "tries occasionally but never reaches the end before freezing", is sometimes not detected at all, and where "the indicator flashes whilst data is being read." That last observation is the valuable one: data is genuinely moving, which means the drive works and stops at a particular place.
| Media | 500GB laptop hard drive removed from its host and connected externally — enumeration intermittent, read operations commencing and stalling before completion; activity indication observed during reads |
| Reported situation | Laptop drive failing in its host · drive removed and connected externally by USB · device not reading reliably · read attempts commencing and stalling before completion · device sometimes not detected at all · indicator flashing during read activity · photographic content required |
| Fault class | Partial readability with stalling at difficult regions — data returning until a failing area is reached; enumeration intermittent alongside |
| Equipment used | Observed activity indication accepted as confirmation of data return · repeated host attempts stopped · imaged write-blocked under strict per-sector timeouts with readable regions taken first · stalling regions deferred and revisited across later passes · recovered content validated by opening |
The decode: what each of his three observations contributes
What the flashing indicator establishes: data is being transferred. Activity indication responds to actual traffic between the drive and the host, so it is direct evidence that the drive is returning content rather than merely being powered.
Why that is the most useful thing in his account: it separates a drive that cannot read from one that reads and then stops. A device returning nothing at all shows no activity, and his does.
What the stalling adds: the reading reaches a limit. A read that begins normally and freezes has encountered a region the drive cannot return — and it stops there rather than skipping and continuing.
Why an ordinary copy behaves that way: it has no mechanism for giving up on a region and moving on. It waits indefinitely for a response that is not coming, which presents as the whole operation freezing.
Why that is the single most costly behaviour on a failing drive: everything beyond the difficult region is never attempted. Hours are spent on one area while readable content further on is left untouched, and the drive's remaining life is consumed at the worst possible point.
What the intermittent detection adds: the drive does not always complete its introduction. Sometimes it presents and sometimes it does not, which points at a device that is marginal at start-up as well as during reading.
Why that makes the window finite: periods of presentation are the opportunity, and they typically become less frequent. Each attempt spent watching it freeze is one not spent capturing.
What is done instead: imaging under strict per-sector timeouts, so a region that does not answer within a set period is deferred rather than waited on. Readable areas are captured first at full speed while the drive is presenting, and difficult ones revisited across later passes.
Why revisiting works: marginal regions are not consistently unreadable. A sector that fails on one attempt frequently returns on another, so several patient passes recover material a single pass cannot.
Why removing the drive was the right step: it separated the drive from the failing laptop and confirmed the fault travels with it. He established that himself and it need not be repeated.
On the bench
The observed activity indication was accepted as confirmation of data return — indication responding to actual traffic between drive and host, so flashing during reads is direct evidence of content being returned rather than mere powering, which separates a drive that cannot read from one that reads and stops. Stalling indicates a region the drive cannot return, with ordinary copying having no mechanism to defer and continue. Imaging ran write-blocked under strict per-sector timeouts.
The outcome
Activity indication accepted as confirmation of data return, repeated host attempts stopped, and readable regions captured first under capped timeouts. 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: the flashing indicator is the useful part. It means data is genuinely moving, so the drive reads until it reaches something it cannot — and an ordinary copy waits there indefinitely.
A drive that starts reading and freezes
Stop retrying, and note what the activity indicator told you: flashing during reads means data is genuinely moving between the drive and the computer, which separates a drive that can't read from one that reads and then stops. The freezing is an ordinary copy waiting indefinitely for a region that will never answer — it has no way to give up and continue, so hours are spent on one difficult area while readable content further on is never touched. If detection is also intermittent, the periods when it does present are the opportunity, and they become less frequent.
Stop retrying — call Manchester Data Recovery on 0161 871 0788; activity accepted as confirmation of data return, imaged under capped timeouts with readable regions first, stalling regions revisited across passes.
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.