Data Recovery Case File · Portable Drives · The Error Is a Safeguard
The Drive Recalculated, Found a Mismatch, and Declined to Pass It On
His enquiry names an error most people treat as a malfunction and which is a deliberate protection. An external drive with "an integrity error on a folder that contains all my work documents. This is now preventing me from accessing the data and files contained within that folder." Every sector is stored with a checksum, and when the recalculated value disagrees, the drive reports an error instead of handing over data it knows to be wrong.
| Media | 2TB external hard drive — cyclic redundancy check failure on read within a specific directory; remainder of the volume accessible |
| Reported situation | External drive in normal service · integrity check error reported on a specific folder · folder contents not accessible · remainder of the drive reported as usable · work documents required |
| Fault class | Physical read degradation at specific sectors — integrity check preventing return of corrupted data; directory record affected rather than file content |
| Equipment used | Integrity error interpreted as detected physical degradation rather than filesystem fault · no repair or consistency check permitted · Atola Insight Forensic error-rate assessment across the affected region · imaged write-blocked with multiple passes over failing sectors · directory record reconstructed on the image |
The decode: what the check does, and why a folder went rather than a file
How the check works: every sector written to a drive is stored alongside a value calculated from its contents. On reading, the drive recalculates that value and compares — and if the two agree, the data is what was written. If they disagree, something has changed on the surface.
What the drive does then, and this is the point: it refuses. Rather than returning data it knows to be wrong, it reports an error — because handing back silently corrupted content would be far worse than admitting failure.
Why that makes the error good news of a sort: without it, degradation would arrive as documents that open with mangled content, images with corrupted regions, and files that seem fine and are not. The error is the mechanism that stops that happening, and it is working exactly as designed.
What it tells us about the fault: the problem is physical. An integrity failure means the magnetic pattern at that location no longer matches what was recorded — degradation of the surface, not a filesystem inconsistency. That distinguishes it from most of the logical faults in this archive.
Why an entire folder became inaccessible over what may be a few sectors: folders are records too. If the affected sectors hold part of the directory record describing that folder's contents, everything inside becomes unreachable — not because the files are damaged, but because the list of them cannot be read.
Why that is encouraging: the documents themselves are very likely intact and sitting exactly where they were. The damage may be measured in a handful of sectors and the visible consequence is an entire folder, which makes the loss look far larger than it is.
What must not happen, and it is what everybody does next: run a consistency check. Those repair by writing, and a check meeting an unreadable directory record resolves the problem by removing or truncating it — which converts an unreadable list into no list at all.
What works instead: imaging with multiple passes over the failing sectors, since a marginal sector that fails once may succeed on a later attempt under different conditions. The directory record is then rebuilt on the image, where nothing is at risk.
On the bench
The integrity error was interpreted as detected physical degradation rather than a filesystem fault — every sector being stored alongside a value calculated from its contents and compared on reading, so a mismatch indicates the recorded pattern has changed and the drive refuses rather than returning corrupted data. No repair or consistency check was permitted, such utilities resolving unreadable directory records by removing them. Imaging ran write-blocked with multiple passes over failing sectors.
The outcome
The error read as physical degradation, no repair permitted, and the directory record reconstructed on a multi-pass image. 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: that error is the drive protecting you. Sectors are stored with a checksum, and when the recalculation disagrees the drive refuses rather than returning data it knows is wrong — which is why an unreadable directory record hides a whole folder of intact files.
Integrity or redundancy check error on a folder
Don't run a consistency check on it — that's the standard next step and it does the specific damage here, because such tools repair by writing, and one meeting an unreadable directory record resolves the problem by removing it. What you have is the drive protecting you: every sector is stored with a value calculated from its contents, recalculated on reading, and a mismatch means the surface has degraded, so the drive reports an error rather than handing back data it knows is wrong. A whole folder disappearing over a few bad sectors is normal — the folder's own record became unreadable while the files inside it are fine.
Don't run a check — call Oxford Data Recovery on 01865 593000; error read as physical degradation, error rates measured across the affected region, imaged with multiple passes and the record rebuilt on the image.
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.