Data Recovery Case File · Desktop Externals & Aging Drives · Put the Number in Proportion
Thirty Thousand Bad Sectors Is a Large Number and a Very Small Fraction
Her enquiry carries a figure that has understandably alarmed her. A laptop reported as having failed catastrophically, where "the hard drive has thirty thousand damaged sectors" and it holds all of her business and personal work. The number is real and the word catastrophically is doing too much work: on a drive of that capacity, thirty thousand sectors is a fraction of a percent, and where they sit matters far more than how many there are.
| Media | Laptop hard drive of approximately five years' service — reported as carrying approximately 30,000 damaged sectors; machine no longer operating |
| Reported situation | Laptop failing during ordinary use · replacement drive stated to be required · approximately thirty thousand damaged sectors reported by a third party · business and personal content held on the drive · assessment of likelihood and cost sought |
| Fault class | Surface degradation with defect count established — proportion of capacity affected small; recoverability governed by distribution rather than by total count |
| Equipment used | Defect count assessed as a proportion of capacity and by distribution rather than in isolation · imaged write-blocked under strict per-sector timeouts with healthy regions taken first · defective regions mapped and revisited across later passes · filesystem structures interpreted with their duplicate copies · recovered content reconciled against expected occupancy |
The decode: what the number means, and the question that matters more
What a sector is: the smallest unit a drive reads or writes, holding a few kilobytes. A drive of ordinary laptop capacity contains on the order of a billion of them, which is the context the figure needs.
What thirty thousand represents against that: a few thousandths of one per cent. Expressed as capacity it is a matter of megabytes on a drive holding hundreds of gigabytes — a real defect and a very small one proportionally.
Why it nonetheless sounds catastrophic: the number is large in absolute terms and it is rising. Nobody quoting it is being misleading; the figure simply needs a denominator to be interpretable.
Why the count is the wrong question: what determines the outcome is where the defects are. Thirty thousand sectors clustered in empty space costs nothing; the same number across the filesystem's own structures could make the whole volume unreadable.
Why the distribution also indicates the mechanism: defects clustered tightly suggest localised surface damage, while defects spread evenly suggest a head reading marginally everywhere. Those are different faults with different prospects, and the pattern distinguishes them.
Why the rising count matters more than the current one: a drive relocating sectors is consuming reserved capacity. A count still climbing means the process is ongoing, and the useful reading is the rate rather than the total.
Why the machine stopping is a separate event: a drive with defects continues working until something essential falls in one. A machine that fails suddenly has usually lost a structure it needs rather than a proportion of its capacity.
Why that is encouraging for her specifically: essential structures are small and duplicated. A filesystem keeps second copies of its key records precisely because losing them is fatal, and a reconstruction from the duplicate frequently returns everything.
What is done about the defective regions: imaging under strict per-sector timeouts with healthy areas taken first at full speed, and defective ones mapped and revisited across later passes. Sectors that fail on one attempt frequently return on another.
What must not happen: no attempts to run the machine, and no repair or check on the volume. A drive with defects spread across it is exactly the case where a consistency check discards references to content it cannot verify.
On the bench
The defect count was assessed as a proportion of capacity and by distribution rather than in isolation — a sector holding a few kilobytes and a laptop drive containing on the order of a billion, so thirty thousand represents a few thousandths of one per cent. Outcome is governed by location rather than count, defects in unused space costing nothing while the same number across filesystem structures may render a volume unreadable, and clustering versus even distribution distinguishing localised damage from marginal head performance.
The outcome
Defect count assessed proportionally and by distribution, healthy regions captured first under capped timeouts, and structures interpreted with their duplicate copies. 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 number is large and the fraction is tiny. A drive of that size holds around a billion sectors, so what decides this is where the defects sit rather than how many there are.
When you are told how many bad sectors a drive has
Ask for the number as a proportion, because it needs a denominator to mean anything — a laptop drive holds on the order of a billion sectors, so tens of thousands is a few thousandths of one per cent. Then ask the question that actually decides the outcome: where they are. Defects sitting in unused space cost nothing, while the same count across the filesystem's own structures can make a volume unreadable. Ask whether the count is still rising, too, since the rate matters more than the total. Don't run the machine or any repair meanwhile.
Ask for it in proportion — call Manchester Data Recovery on 0161 871 0788; count assessed against capacity and by distribution, imaged under capped timeouts, structures interpreted with their duplicate copies.
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.