Data Recovery Case File · Mac & Apple Ecosystem · Seen Is Not Mounted

Visible in Target Mode and Will Not Mount

His enquiry described a test most people never get as far as running, and the result is close to a diagnosis. "The iMac has crashed and I can't get the disk to mount, so that even when I can see it on another machine in transfer mode, I can't access the data on the hard drive." Connecting one Mac to another so the first behaves as an external drive is the right thing to try and it produced a genuinely informative result. Seeing the disk and being unable to mount it are two different stages, and the gap between them places the fault precisely — above the hardware, below the files, in the layer that has failed most often in this archive.

The decode: what target mode proves, and what refusing to mount means

What the target connection establishes: a great deal, and all of it good. For the disk to appear on the second machine, the first machine's storage must have received power, spun up, identified itself, reported its capacity and responded to being addressed — and the connection between the two machines must be working. So the drive is alive and answering. That single observation eliminates the seized, stuck, clicking, dead-board and unidentifiable categories in one go, which between them account for most of the expensive faults in this trade.

What refusing to mount means: the next stage failing. Mounting is where the operating system reads the volume's own filing structures and decides whether they are coherent enough to present. When those structures are damaged or contradict one another, macOS declines to mount rather than mounting an inconsistent filesystem and risking further damage. That refusal is protective, and it means the fault is in the bookkeeping rather than in the disk or the files. His data is sitting intact behind a catalogue that will not currently parse.

Why this is the recoverable category: because nothing has been erased and nothing is physically failing. Reconstruction on a write-blocked image rebuilds the damaged structures until the volume mounts from the copy, typically returning the folder tree, filenames and dates as they were — not a carve.

The offer to refuse: having a disk visible and unmountable puts a very tempting button in front of him. Disk Utility will offer First Aid, which repairs filesystems by writing corrections — choosing between records that disagree, discarding entries it cannot reconcile, and moving orphaned data into recovery folders with generic names. On lightly inconsistent volumes it works. On a badly damaged one it converts something reconstructable into permanent structural loss and strips filenames along the way. There may also be an offer to erase, which is final. Neither should be accepted, and the disk should not be left connected while he thinks about it.

Why the crash matters: a machine that crashed and left a volume unmountable was very likely writing to the filesystem at the moment it stopped — which is exactly how these structures are left mid-update. That is consistent with everything he describes and points away from hardware trouble.

On the bench

The disk was imaged write-blocked in one pass before any repair was contemplated, which is the discipline a repair utility fundamentally cannot offer — everything afterwards happened against a copy, and the original was never modified. On the image the structures were examined in order, the partition records first and then the filesystem, establishing which layer the crash had damaged and how far it extended. That layer was reconstructed until the volume mounted from the copy with its folder tree, filenames and dates intact, and signature carving swept alongside for anything beyond structural repair. The contents were verified by opening.

The outcome

The volume rebuilt from a write-blocked image with folders and filenames intact, verified and delivered. Free assessment, one fixed written figure including VAT, no recovery, no fee. The decode, for anyone whose disk appears and will not open: those are two different stages, and the gap between them is informative — being seen at all proves power, spin-up, identification and capacity reporting have all succeeded, which eliminates the expensive mechanical and electronic faults; refusing to mount means the operating system found the filing structures incoherent and declined rather than risking further damage, which is protective and places the fault in the bookkeeping with your files intact behind it; a crash is the usual cause, because the structures were being written when the machine stopped; and First Aid is the one thing that can make it permanent.

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.