Data Recovery Case File · Mac & Apple Ecosystem · Two Different Questions
Healthy Hardware, Unreadable Volume
Her enquiry describes three separate diagnostic attempts that between them produced confusion rather than an answer. A laptop showing a flashing folder at start-up: "I did disk repair but it's saying the system appears to be okay. An IT friend checked the drive with his Windows software and found it to be healthy. But he tried to get into it with an emulator and couldn't access anything. I got someone else from IT to connect my drive to their Mac and she couldn't access anything either." Three tests, three results, and no conclusion. In fact they agree completely — the hardware is fine and the volume is unreadable, which is the more recoverable of the two failures.
| Media | Laptop internal hard drive formatted for macOS — no startup volume found; hardware health reported as good by third-party testing; volume not mounting on a separate machine of the same platform |
| Reported situation | Machine displaying a missing-system indicator at start-up · built-in repair utility reporting the system as apparently fine · drive tested with Windows software and reported healthy · access attempted through emulation without success · drive connected to a separate machine of the same platform and not mounting |
| Fault class | Filesystem structure damage on mechanically sound media — content intact beneath unmountable structures |
| Equipment used | Drive imaged write-blocked before any repair · no repair utility permitted against the original · structures rebuilt on the image including surviving backup copies · signature carving alongside · files validated by opening |
The decode: what each test actually measured
What the Windows software was reporting, and this is the crux: Windows cannot read a Mac-formatted volume at all — it has no understanding of that filesystem and will typically offer to initialise such a disk rather than open it. So software running there was not examining her files, her folders or her filing structures. It was reading the drive's own self-monitoring data: reallocated sectors, error rates, spin-up time, hours in service, temperature. That is a report on the mechanism and electronics. Healthy means the hardware is fine and says nothing whatever about the data. Her friend answered a question about the drive; she was asking a question about the volume.
What the emulator attempt was worth: nothing, unfortunately, and it is an understandable idea. An emulator runs software; it does not give a Windows machine the ability to read a filesystem the host cannot parse. It was never going to work and its failure means nothing.
What the second Mac established, and it is the most useful test of the three: a machine that can read that filesystem, connected to the drive, and could not mount it. Since the hardware is healthy, the only remaining explanation is that the structures describing the volume are damaged. That is a real finding and it came from the right test.
What the repair utility's answer meant: a pass on the checks it ran, not a clean bill overall. These tools verify particular structures and report on those; a volume can pass one check and be unmountable for a reason outside it. A repair reporting "appears to be okay" while the machine will not start is not a contradiction — it is a narrow answer being read broadly.
Why the combination is good news: healthy mechanism plus unmountable volume is the recoverable case. The files sit where they were written, untouched; what is damaged is the catalogue describing where they are. The filesystem keeps backup copies of its key structures at known positions, so rebuilding from one frequently returns everything with folders and names intact.
The one thing to stop: running the repair utility again. Those tools write their conclusions back, and a conclusion drawn from damaged structures can overwrite the very records a rebuild would use. A repair that fails is far better than one that succeeds.
On the bench
The drive was imaged write-blocked before any repair, and no repair utility was permitted against the original — since those tools write their conclusions back, and a conclusion drawn from damaged structures overwrites the records a rebuild depends on. Structures were rebuilt on the image, including the backup copies the filesystem maintains at known positions, which is what returns files with folders and original names rather than as an unnamed set. Signature carving ran alongside, and files were validated by opening.
The outcome
The drive imaged before any repair, structures rebuilt from their surviving backup copies and files validated by opening. 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, for anyone told their drive is healthy while it still will not work: those answers agree. Windows software cannot read a Mac-formatted volume at all, so it was reporting the drive's own self-monitoring data — a statement about the mechanism and electronics, not about your files. Healthy hardware plus a volume that will not mount on a machine that understands it means damaged structures over intact content, which is the recoverable case. Stop running repairs.
Told your drive is healthy but you still can't get in
Those two things aren't in conflict, and together they're encouraging. Software running on Windows can't read a Mac-formatted volume at all — it has no understanding of that filesystem and will usually offer to initialise the disk rather than open it. So when it reports a drive as healthy, it's reading the drive's own self-monitoring data: error rates, reallocated sectors, hours in service. That's a statement about the mechanism and electronics, and it says nothing about your files. Connecting it to another Mac and finding nothing mounts is the useful test, and it points at damaged filing structures over intact content — the recoverable failure. Stop running the repair utility, though. Those tools write their conclusions back, and a repair that succeeds on damaged structures often does more harm than one that fails.
Stop running repairs — call Newcastle Data Recovery on 0191 406 1051; imaged write-blocked before anything, structures rebuilt from their backup copies on the image, files checked by opening.
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.