Data Recovery Case File · Desktop Externals & Aging Drives · The Attribute Is Specific
Pending Sectors Are Ones the Drive Has Failed to Read and Not Yet Given Up On
His enquiry quotes an attribute by name, which makes it far more useful than a general warning. An external drive refusing to start and asking to be formatted, carrying a health caution for "pending sector count", with a consistency check unable to run — and holding a full backup. That attribute has a precise meaning: sectors the drive could not read, queued for reallocation, still holding whatever was written to them.
| Media | External hard drive holding a full system backup — health reporting raising a pending sector count caution; volume prompting for formatting and consistency check unable to run |
| Reported situation | External drive refusing to present its volume · host prompting for the drive to be formatted · health reporting raising a caution for pending sector count · consistency check attempted and unable to run · drive holding a complete backup · recovery sought |
| Fault class | Sectors failing verification and awaiting reallocation — content in affected sectors retained pending successful rewrite; structural damage preventing volume presentation |
| Equipment used | Pending sector count interpreted as unresolved read failures rather than confirmed loss · no repair or rewrite permitted on the drive · imaged write-blocked under strict per-sector timeouts with healthy regions taken first · pending regions revisited across later passes · filesystem structures interpreted with their duplicate copies |
The decode: what pending means, and why it is better than the alternative
What the drive does when a read fails: it marks the sector as questionable. The sector is not yet declared bad, because the drive cannot be certain until it tries to write to it — and it will not write to it uninvited.
Why it waits: reallocation means moving the sector's content to spare capacity and retiring the original. Doing that requires the content, and the content is what could not be read — so the drive holds the sector in a pending state rather than discarding it.
What resolves a pending sector: a successful write to it. If new data is written and verifies, the sector returns to normal service; if it does not, the sector is reallocated and the count of confirmed bad sectors rises.
Why that makes pending the more hopeful of the two counts: a pending sector still holds its original content. It has failed a read attempt, not been erased, and repeated attempts frequently succeed where one did not.
Why the count rising indicates an active process: sectors accumulate in that state as reads fail. A rising pending count means the surface is degrading now, rather than having degraded at some point in the past.
Why the format prompt follows from the same cause: pending sectors within the filesystem's structures make the volume uninterpretable. The system reads what it can, fails to make sense of it, and offers the only remedy it has.
Why the check being unable to run is fortunate: a consistency check writes. Writing to pending sectors is exactly what converts them to confirmed bad ones, discarding whatever they held — and the check not running has preserved them.
Why the drive must not be written to at all: any write may land on a pending sector. The distinction between pending and reallocated is the distinction between content retained and content gone, and only writing crosses it.
What is done instead: imaging under strict per-sector timeouts with pending regions deferred and revisited across later passes. Reading a pending sector repeatedly costs nothing and frequently succeeds, where a single attempt did not.
Why the content being a backup changes the priority: the original may still exist. Establishing whether the source machine still holds this material is worth doing before anything else, and it costs nothing.
On the bench
The pending sector count was interpreted as unresolved read failures rather than confirmed loss — a drive marking sectors questionable on read failure without declaring them bad, since reallocation requires moving content that could not be read, so the sector is held pending and retains what was written to it. A successful write resolves it either to normal service or to confirmed reallocation. No repair or rewrite was permitted; pending regions were revisited across later passes.
The outcome
Pending sectors read as unresolved rather than lost, no writing permitted on the drive, and pending regions revisited across passes. 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: pending is the better of the two counts. Those sectors failed a read and still hold what was written to them — and only a write turns pending into gone, which is why the check refusing to run helped you.
A drive reporting a pending sector count
Don't write anything to it, don't run a repair, and be glad the check wouldn't start. Pending has a precise meaning: the drive failed to read those sectors and has marked them questionable without declaring them bad, because retiring a sector means moving its content and the content is what it couldn't read. So they still hold what was written to them, and repeated reads often succeed where one didn't. A write is what resolves the state — either back to normal or to confirmed bad, discarding the content. Check whether the source machine still holds this material too.
Don't write to it — call Manchester Data Recovery on 0161 871 0788; pending read as unresolved rather than lost, imaged under capped timeouts, pending regions revisited across later 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.