Data Recovery Case File · Desktop Externals & Aging Drives · The Software Was the Load
A Full Scan Reads Every Sector, Which Is Far Harder Than Anything Ordinary Use Demands
His enquiry records a change that happened during his own attempt to fix things. A drive prompting to be formatted where he "tried recovery software but the drive starts making noises", with a component visibly loose on the board and a suspicion the board is at fault. The sequence is the important part: the drive was quiet until it was asked to read everything, and a full scan is the heaviest demand any drive faces.
| Media | 1TB hard drive prompting for formatting — mechanical sounds developing during a full-surface software scan; a component visibly detached from the circuit board |
| Reported situation | Drive prompting the host to format it before use · recovery software run against the drive by the owner · mechanical sounds beginning during that scan · component observed loose on the circuit board · board fault suspected by the owner · content sought |
| Fault class | Surface or head degradation surfacing under sustained full-coverage reading — board component loss to be assessed separately; scanning contraindicated |
| Equipment used | Onset of sounds during scanning interpreted as load-induced rather than coincidental · scanning halted and no further host access permitted · board examined at component level under magnification with the detached position identified · imaged write-blocked under strict per-sector timeouts with healthy regions taken first · difficult regions revisited across later passes |
The decode: what a scan asks of a drive, and what the sounds mean
What ordinary use asks of a drive: very little. Opening documents and browsing folders touches a small fraction of the surface, mostly in regions that are read frequently and therefore known to be good.
What a recovery scan asks instead: everything. It reads every sector from beginning to end, including regions that have not been touched in years, and it does so continuously for hours.
Why that is the heaviest load a drive ever experiences: it combines full coverage with sustained duration. Heads sweep the entire surface repeatedly and the motor runs without pause, which nothing in normal operation approaches.
Why sounds appearing during it is diagnostic: the drive was managing until it was asked for more. A mechanism that operates quietly under light demand and becomes audible under full coverage is one at the edge of its capability.
What the sounds themselves indicate: repeated attempts. A head encountering a region it cannot read retries, repositioning between attempts, and that repositioning is what becomes audible.
Why continuing the scan is the worst available option: it will keep demanding those regions. Every retry on a degrading surface is another pass of the head over it, and the scan has no reason to stop.
Why the software cannot be expected to know: it reads what it is told to read. Recovery tools are built to be persistent, which is exactly wrong for a drive that is failing mechanically.
What the loose component is, and why it is probably separate: a detached part on the board is a real finding and an unlikely explanation for mechanical noise. Board faults prevent a drive working; they do not make it retry.
Why the format prompt fits the mechanical picture: unreadable regions within the filesystem's structures make a volume uninterpretable. The system offers the only remedy it has, and it is the wrong one.
What is done instead of scanning: imaging with strict per-sector timeouts, healthy regions captured first at speed, and difficult areas deferred. The opposite of a scan, which insists on everything in order.
On the bench
The onset of sounds during scanning was interpreted as load-induced rather than coincidental — ordinary use touching a small and frequently-read fraction of the surface, whereas a recovery scan reads every sector continuously for hours, combining full coverage with sustained duration beyond anything normal operation demands. Audible retries indicate a head repositioning between failed attempts. Scanning was halted; imaging took healthy regions first with difficult areas revisited across later passes.
The outcome
Sounds during scanning read as load-induced, scanning halted and host access stopped, and healthy 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 software was the load. A scan reads every sector for hours, which is far harder than anything ordinary use demands — so a drive that only becomes audible under it is at the edge of what it can do.
When a drive starts making noises during a scan
Stop the scan immediately and don't restart it. Recovery software is built to be persistent, which is exactly wrong for a drive failing mechanically — it reads every sector continuously for hours, combining full coverage with sustained duration in a way nothing in ordinary use approaches. So a drive that was quiet until you scanned it isn't coincidence: it was managing light demand and cannot manage full coverage. The sounds are retries, and each one is another pass of the head over a region that's already struggling.
Stop the scan — call Manchester Data Recovery on 0161 871 0788; sounds during scanning read as load-induced, imaged under strict per-sector timeouts, healthy regions taken first and difficult areas deferred.
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.