Data Recovery Case File · Desktop Externals & Aging Drives · Stop Scanning
When the Software Tells You It Is Hardware
His enquiry describes a thorough and entirely reasonable effort that needs to stop. A 1TB external drive: "I have tried several data recovery software packages but none of these have been able to detect any file or missing partitions, but do report bad sectors. In the disk manager it reports it as unallocated and" a repair utility was run. Several independent tools, one consistent finding. Bad sectors reported by everything is not an inconclusive result — it is a physical read failure, reported by software that has just told him it is the wrong instrument for the job.
| Media | 1TB external hard drive — reported as unallocated by the host; multiple recovery applications detecting no files or partitions and reporting bad sectors; repair utility run |
| Reported situation | Drive inaccessible · several recovery applications run without detecting files or partitions · bad sectors reported consistently by each · disk manager reporting the volume as unallocated · repair utility attempted |
| Fault class | Physical read failure across the leading region — partition structures within unreadable areas; imaging under timeout control indicated |
| Equipment used | All scanning discontinued · Atola Insight Forensic error-rate assessment · imaged write-blocked under per-sector timeouts with weak regions revisited (PC-3000 Express with Data Extractor) · structures rebuilt from the image · losses mapped per file |
The decode: what the finding means, and why to stop now
What a bad sector actually is: a region the drive attempted to read and could not, having exhausted its internal error correction and its retries. It is a report from the drive itself, passed up through the software. So when several unrelated applications independently report bad sectors, they are not disagreeing or failing — they are all correctly relaying the same physical fact. That is a solid finding, not an inconclusive one.
Why they find no partitions: partition structures live in a small region at the very start of the disk. If that region is among the unreadable areas, the tools have nothing to work from — which is also why the disk manager reports the volume as unallocated. The drive is not empty; the description of its contents is in a place that cannot currently be read.
Why more scanning makes it worse, and this is the practical point: a recovery scan reads the whole surface, including the failing areas, repeatedly. Each pass over a weak region means the drive attempting the read, exhausting its retries, and — where the difficulty is a head or a surface defect — the head passing over the damaged area again and again, at full retry, generating heat. Marginal regions that would still return data on a careful attempt are turned into ones that do not. Running a fourth package is not a fresh attempt; it is more of the thing that is causing harm.
Why the repair utility is the more serious concern: repair tools write. Faced with structures it cannot parse, a repair utility forms a conclusion about what the layout should be and writes that conclusion back — and where the reads it based that on were failing, the conclusion is drawn from bad information and overwrites the real structures. On a drive reporting unallocated, that can mean a rebuilt structure written over the one a recovery would have used.
What is actually done instead: the opposite of scanning. Error rates are measured first to establish how the failing regions are distributed. Then the drive is imaged with per-sector timeouts — each difficult sector given a strict budget and deferred rather than allowed to exhaust the drive's retries — with the healthy expanse captured at speed first and weak regions revisited on later passes, where sectors that failed several attempts frequently succeed. Structures are rebuilt from the image, never from the drive.
The instruction: unplug it and run nothing further.
On the bench
All scanning was discontinued, since several independent tools had already reported the same physical finding and each further pass reads the failing regions again at full retry. The Atola Insight Forensic assessed error rates first to establish how the unreadable areas were distributed. Imaging then ran write-blocked under per-sector timeouts on the PC-3000 Express with Data Extractor, healthy regions captured at speed and weak ones revisited on later passes. Structures were rebuilt from the image, and unreadable areas resolved to the individual files they affected.
The outcome
Error rates measured, the drive imaged under timeout control with weak regions revisited, and structures rebuilt from the copy. 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 tools all report bad sectors: that is a solid finding rather than a failure to find anything. A bad sector is the drive reporting a read it could not complete, so several independent tools agreeing means they are all correctly relaying the same physical fact — and telling you software is the wrong instrument. Stop scanning, and above all stop repair utilities, which write their conclusions back.
Recovery software that only reports bad sectors
Unplug the drive and don't run a fourth package. Several unrelated tools all reporting bad sectors isn't an inconclusive result — it's them correctly relaying a physical fact from the drive itself, which is that regions were read and could not be returned. It also explains why none of them find partitions: those structures sit in a small area at the very start of the disk, and if that's among the unreadable regions there's nothing to work from, which is why the disk manager calls it unallocated. Each further scan reads the failing areas again at full retry, turning marginal regions into unrecoverable ones. And be especially careful with repair utilities, since those write their conclusions back — a conclusion drawn from failing reads overwrites the real structures.
Stop scanning — call Newcastle Data Recovery on 0191 406 1051; error rates measured first, imaged under per-sector timeouts with weak regions revisited, structures rebuilt from the copy.
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.