Data Recovery Case File · Second Fixes & Trade Handoffs · The Name Describes the Wrong Thing
A Repaired Sector Is a Sector Whose Contents Were Replaced
This enquiry came from a computer business handling a client's drive, and it reports an intervention whose consequences the name conceals. A disk that "spins up, no strange noises, but does not mount. It has paging errors and bad blocks. We've used a sector repair utility on the disk, which fixed a number of blocks." Those blocks were fixed by being overwritten — which is the only way such a tool can fix anything, and it means whatever they held is gone.
| Media | Laptop hard drive from a third-party client — rotating without abnormal acoustics; volume not mounting; sector repair utility executed with blocks reported as repaired |
| Reported situation | Drive received from a client by a computer business · drive achieving rotation · no abnormal acoustics · volume not mounting · read errors and unreadable blocks reported · sector repair utility executed against the drive · a number of blocks reported as repaired · contents required |
| Fault class | Read failure with write activity already applied — repaired sectors overwritten or reallocated; remaining margin consumed by sustained utility operation |
| Equipment used | Extent of utility operation established before any assessment · repaired sector locations mapped against filesystem structures · no further write activity permitted · Atola Insight Forensic error-rate assessment · imaging under strict per-sector timeouts with retries capped |
The decode: how such a tool works, and what fixing means
What the utility actually does: reads a sector, and where the read fails, writes to it. That is the entire mechanism. Writing either succeeds — because the sector was marginal rather than dead, and a fresh write refreshes the magnetic pattern — or it fails, at which point the drive reallocates the address to a spare sector held in reserve.
What happens to the original contents in each case: in the first, they are replaced by whatever was written. In the second, the address now points somewhere else entirely and the original location is abandoned. Both outcomes lose the data that was there, which is not a side effect of the tool working badly — it is the tool working.
Why the vocabulary misleads: "repair", "regenerate", "fix" all suggest restoration — that something broken has been made whole. What has been made whole is the sector's ability to accept future writes, which is a completely different thing from recovering what it held.
So "fixed a number of blocks" means: a number of blocks that previously held data now hold something else, or point somewhere else. And the blocks a drive cannot read are not randomly distributed — they are disproportionately in regions that have been read heavily, which includes filesystem structures.
Why that may explain the volume not mounting: if repaired sectors fell within the filing structures, those structures now contain written-over regions. The mount failure may predate the utility or may have been caused by it, and establishing which requires knowing where the repairs landed.
The second cost, separate from the data: such tools operate across the whole surface, for hours, reading and writing continuously. That is the heaviest sustained load a failing drive can be given, and it consumes exactly the margin a capture would have used.
When these tools are appropriate, because they do have a use: on a drive being prepared for reuse, where the question is whether the surface is sound and the contents are irrelevant. Never on a drive whose contents are wanted. The distinction is the whole of it.
What must happen now: no further utility operation, and imaging with a tool that reads without writing under capped timeouts.
On the bench
The extent of utility operation was established before any assessment — sector repair tools reading and, on failure, writing to the sector, which either refreshes it in place or causes the drive to reallocate the address to a spare, both of which lose the original contents by design rather than by malfunction. Repaired sector locations were mapped against filesystem structures, unreadable blocks clustering in heavily-read regions. No further write activity was permitted, and imaging ran under strict per-sector timeouts with retries capped.
The outcome
The extent of prior operation established, repaired locations mapped against the structures, and the drive imaged without further writing. 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: those blocks were fixed by being written to. That is the only mechanism such a tool has — a fresh write either refreshes a marginal sector or forces reallocation, and both lose what was there.
Before running a sector repair utility
Only use one on a drive whose contents you don't want. Those tools work by reading a sector and, when the read fails, writing to it — that's the entire mechanism. The write either succeeds, refreshing a marginal sector in place, or fails, at which point the drive reallocates the address to a spare held in reserve. Both outcomes replace or abandon whatever was there, by design rather than malfunction. The words mislead: "repair" and "regenerate" suggest restoration, when what's been restored is the sector's ability to accept future writes. They also run for hours across the whole surface, which is the heaviest load a failing drive can take.
Stop there — call Oxford Data Recovery on 01865 593000; extent of operation established first, repaired locations mapped against the structures, imaged under capped timeouts without further writing.
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.