Data Recovery Case File · Mac & Apple Systems · Not Completely Died
Appearing in a Disk Utility With an Error Places the Fault Above the Device
Her enquiry contains a phrase worth agreeing with. A drive formatted for one platform that no longer opens, but which "is being recognised in my disk utility with an error, so it's not completely died." That reasoning is sound: a device listed by a disk utility has enumerated successfully, and an error reported about its volume is a different and much smaller problem than a device that is not there.
| Media | External hard drive in a platform-native format — enumerating and listed by the host disk utility with a reported volume error; not mounting for access |
| Reported situation | External drive formatted for the host platform · drive no longer opening for access · drive appearing in the host disk utility · an error reported against it by the utility · photographic content held · recovery sought |
| Fault class | Device enumerating with volume failing verification — filesystem structures inconsistent or partially unreadable; content unreferenced rather than absent |
| Equipment used | Utility listing accepted as confirmation of successful enumeration · no repair offered by the utility permitted · imaged write-blocked under strict per-sector timeouts before any interpretation · filesystem structures interpreted with their duplicate copies · content carved independently where structures did not reconcile |
The decode: what the utility's two statements each mean
What being listed establishes: the device works. Power arrived, the drive spun up, identified itself, and the host accepted it as present — an exchange a failed device does not complete.
Why that eliminates the expensive possibilities: board faults, firmware-stage failures and mechanical problems all prevent enumeration. A drive listed by a utility has passed the point at which those would have stopped it.
What the error is about instead: the volume rather than the device. A disk utility verifies the structures describing a filesystem and reports when they do not agree, which is a statement about what is written on the drive.
Why the volume then fails to open: the system will not mount a filesystem it cannot verify. Refusing is safer than proceeding on structures that may describe the wrong locations, so it declines.
Why her conclusion is exactly right: not completely died is a good description. The device is fine and its description of itself is not, which is among the more recoverable positions.
What must not be accepted, and it is offered immediately: the utility's repair function. A first aid or repair option rewrites the structures rather than reading them, and where regions are unreadable it discards references it cannot reconcile.
Why that offer is so hard to refuse: it appears alongside the error, it is described as a fix, and the drive is otherwise unusable. Everything about the interface encourages it, and it is the action most likely to make this worse.
What is done instead: the drive is imaged first, and every repair attempted against the copy. A reconstruction that fails on an image costs nothing, where the same attempt on the original is irreversible.
Why the structures can usually be rebuilt: filesystems keep duplicate copies of their key records elsewhere on the volume. Where the duplicate is intact the arrangement returns whole, with folders and names as they were.
Why she should not keep reconnecting it: if the underlying cause is developing unreadable regions, each mount attempt reads the same structures again. Repeated reading of a marginal area is what turns it unreadable.
On the bench
The utility listing was accepted as confirmation of successful enumeration — a listed device having powered, spun up, identified itself and been accepted by the host, an exchange that board, firmware-stage and mechanical faults all prevent. The reported error concerns the volume rather than the device, a utility verifying filesystem structures and refusing to mount what it cannot verify. No repair offered by the utility was permitted; structures were interpreted with their duplicate copies.
The outcome
The listing accepted as confirmation of enumeration, no utility repair permitted, and structures interpreted from an image 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: not completely died is the right reading. Being listed proves the device works, and the error is about the description written on it rather than the drive itself.
A drive listed in a disk utility with an error
Refuse the repair or first aid option, however plainly it presents itself as the fix — it rewrites the structures rather than reading them, and where regions are unreadable it discards references it can't reconcile. Your instinct is right that this isn't a dead drive: being listed at all proves it powered, spun up and identified itself, which is exactly what board, firmware and mechanical faults prevent. The error concerns the description written on the drive rather than the device. Stop reconnecting it too, since each mount attempt re-reads the same structures.
Don't run the repair — call Manchester Data Recovery on 0161 871 0788; listing accepted as confirmation of enumeration, imaged before any repair, 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.