Data Recovery Case File · Desktop Externals & Aging Drives · A Window You Can Waste
A Drive That Works Briefly and Then Locks Everything Up
His enquiry described a pattern that is genuinely maddening to live with and precisely diagnosable. An internal hard drive: "after a few minutes or even seconds of working, it hangs, and any further interaction with it just freezes." Family photographs, not backed up. That behaviour is not a drive intermittently failing — it is a drive that reads perfectly well until it meets something it cannot read, at which point everything stops. So there is a real working window each time it starts, and the natural response to it is the most expensive thing he could do.
| Media | Internal hard drive of an earlier generation — operating normally for seconds to minutes after power-up, then hanging with all subsequent access frozen; family photographs held without backup |
| Reported situation | Drive functioning briefly on each attempt · complete stall following that period · further interaction unresponsive · irreplaceable personal photographs at stake |
| Fault class | Localised unreadable regions causing indefinite retries — drive functional until a defective area is reached; each power cycle providing a limited window |
| Equipment used | Era-appropriate native connection · Atola Insight Forensic surface and error-rate assessment · PC-3000 Express with Data Extractor imaging under per-sector timeouts · weak regions deferred and revisited |
The decode: why it hangs, and how not to spend the window
What is actually happening: the drive is fine until it is asked for something in a damaged region. At that point it retries internally, and the request never returns. Everything above it waits — the storage driver blocks, the file manager freezes, and eventually anything else needing storage queues behind it. So the freeze is not the drive dying at that moment; it is one unanswered request stopping the whole chain. That also explains why the delay varies from seconds to minutes: it depends entirely on when whatever is running happens to touch a bad area.
Why the window is real: before that point, the drive reads normally. It is not slow, not failing, not producing errors — it is working. That is genuinely encouraging, because it means the great majority of the surface is intact and readable, and the fault is localised rather than general.
The worst way to spend it: and this is the natural instinct. Restart, browse to a folder, grab a few files, freeze, restart, repeat. Each cycle spends a start-up — the most demanding thing a drive does — to retrieve a handful of files, and much of the window is consumed by the operating system's own activity, thumbnail generation and folder scanning rather than by the copying. Worse, the hang itself is a prolonged period of the drive retrying the same failing region, which is exactly the ground that should be left alone. A dozen sessions of this can achieve less than one done properly and cost considerably more margin.
What should happen instead: imaging with per-sector timeouts. Each failing sector is given a strict budget and deferred rather than retried indefinitely, so the drive never hangs — the pass simply moves on and returns later. The healthy expanse is captured first at full speed while the drive is at its strongest, and the difficult regions are revisited afterwards on their own terms. That converts his stop-start window into a continuous read, which is the entire difference between the two approaches.
If he must copy something himself first: the practical version. Do not browse. Know the exact folder path before starting, copy that one folder, and disable thumbnail previews so the system is not reading every image to draw icons. Photographs first, in one go, largest priority first. And accept that this is a stopgap rather than a method.
On the bench
The drive was brought up on an era-appropriate native connection and never attached to a general-purpose computer, where a hang would stall the host and prolong the retries. The Atola Insight Forensic mapped surface condition and error rates, establishing where the defective regions actually were rather than discovering them by freezing. Imaging then ran on the PC-3000 Express under Data Extractor with per-sector timeouts enforced — the healthy expanse captured first in one continuous pass, weak neighbourhoods deferred and revisited on later patient attempts — and the photographs validated by rendering.
The outcome
The defective regions mapped rather than encountered, the drive imaged in a continuous pass under timeout control, and the photographs validated and delivered. 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, for anyone whose drive works briefly then freezes: the drive is fine until asked for something in a damaged area, at which point it retries forever and everything waiting on it stops — so the freeze is one unanswered request stalling the chain rather than the drive dying; that means the fault is localised and most of the surface is readable, which is good news; but restarting to grab a few files each time is the worst way to use it, because you spend a start-up per handful and each hang is prolonged retrying of the worst ground.
Drive that works for a minute and then hangs
Resist the restart-and-grab cycle — it feels productive and it's the most expensive way to use what you have. Each restart spends a start-up, which is the most demanding thing a drive does, and most of your working minute goes on the operating system browsing folders and generating thumbnails rather than on copying. The hang itself is worse: it's a long stretch of the drive retrying the exact region that's failing. Understand what's happening — the drive reads perfectly until something asks for a damaged area, then retries indefinitely while everything above it waits, which is why the delay varies from seconds to minutes. That also means most of your disk is fine. If you must grab something yourself, know the exact folder path before you start, turn off thumbnail previews, copy one folder in one go, and don't browse.
Don't spend it restarting — call Glasgow Data Recovery on 0141 404 0294; defective regions mapped rather than encountered, imaged in one continuous pass under per-sector timeouts.
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.