Data Recovery Case File · Formatted & Logical Faults · The Wrong Layer
A Volume You Cannot Reach Is Not the Same as Files That Are Damaged
Her enquiry contains a reasonable guess at the wrong level. A 2TB drive holding well over a terabyte that "has recently come up with an error of no longer being accessible", with the cable ruled out, and where "it seems that the files might be corrupt but I'm not sure." An inaccessible volume and corrupt files are different failures, and the message she is seeing describes the first.
| Media | 2TB external hard drive holding approximately 1.3 to 1.8TB — volume returning an access failure; connection eliminated by the owner |
| Reported situation | External drive returning an access error at volume level · error stating the location is no longer accessible · cable inspected and eliminated · owner uncertain whether file content is affected · substantial content held |
| Fault class | Volume structures unreadable with file content unassessed — access failure occurring before any file is opened; content condition independent of the message |
| Equipment used | Access failure located at volume level rather than file level · imaged write-blocked before any interpretation · filesystem structures interpreted with their duplicate copies · recovered files validated individually by opening · content reconciled against expected volume occupancy |
The decode: which layer failed, and why it matters what she does next
What the message reports: the system could not reach the location. That happens before any file is involved — the volume itself could not be presented, so nothing was ever asked of the content.
Why that makes corrupt files an unlikely explanation: damaged files produce errors when those files are opened. They do not prevent a volume from being reached, and a drive full of unopenable files would still list them.
Why the distinction is not academic: it changes what should be done. A volume-level failure is addressed by reconstructing structures; a file-level one by recovering individual items — and the remedies people reach for differ accordingly.
What most commonly produces this at volume level: the structures describing the filesystem cannot be read or do not parse. They occupy a small area at the volume's start, and their loss makes everything behind them unreachable while leaving it entirely intact.
Why her cable check was worth doing: a marginal connection produces intermittent access failures that look identical. Eliminating it means the behaviour belongs to the drive rather than to the path to it.
What is worth knowing about the size figure she gives: she reports the drive as holding well over a terabyte. If that occupancy figure is still being read, the allocation record survives — which confirms content is present and is a useful check on any reconstruction.
Why the filesystem type matters here: it determines where the duplicate structures are kept. Filesystems maintain secondary copies of their key records elsewhere on the volume, and knowing which one is in use means going straight to them.
Why a repair utility is the wrong response: the system will offer to check and fix the volume. A repair that cannot reconcile entries discards them, and content those entries described becomes unreferenced — turning a structural problem into a recovery problem.
Why continued connection is worth avoiding even though the drive seems well: the cause of the structural damage is not yet known. If the drive is developing read failures in that early region, each attempt is retry cycles on the part that matters most.
What the likely outcome is: good. Volume structures are the most duplicated part of a filesystem and the most reconstructible, and a drive that is otherwise healthy usually gives its content back whole, with folders and names intact.
On the bench
The access failure was located at volume level rather than file level — an inaccessible-location error arising before any file is involved, whereas damaged files produce errors on opening and do not prevent a volume being reached. Structures describing the filesystem occupy a small area at the volume's start, so their loss makes intact content unreachable. Filesystem structures were interpreted with their duplicate copies, filesystems maintaining secondary records elsewhere on the volume.
The outcome
The failure located at volume level, the drive imaged before any interpretation, 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: your files are probably not the problem. An inaccessible location means the volume could not be presented, which happens before any file is asked for — and volume structures are the most duplicated part of a filesystem.
An access error on a whole drive
Don't let a repair utility check and fix the volume — a repair that can't reconcile entries discards them, and content those entries described becomes unreferenced, turning a structural problem into a recovery one. Read the message at the right layer: an inaccessible location means the volume itself couldn't be presented, which happens before any file is involved, so damaged files aren't a likely explanation — those produce errors when opened and would still list. If the drive still reports how much space is in use, that's worth noting, since it confirms your content is present.
Don't let anything repair it — call Manchester Data Recovery on 0161 871 0788; failure located at volume level rather than file level, imaged before interpretation, 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.