Data Recovery Case File · Formatted & Logical Faults · The Drive That Tells Two Stories

Missing on the Mac, visible-but-unreadable on Windows: why two systems disagree about one damaged volume — the blocked chkdsk counted as luck, and the one truth rebuilt from the image

Her report read like a small mystery, precisely observed. Browsing her external drive on a Mac for training-course materials: "half of the information was not there." The same drive on a partner's Windows work laptop: "I could see the missing folders — but when I tried to open them, I got an error that the file or directory is corrupted or unreadable." They then tried the textbook move — chkdsk /f — and it refused to run: the disk reported as write-protected, and without admin rights on a managed work machine, the protection couldn't be lifted. Her closing bafflement — "it's even stranger that I can't see the folders on my Mac but I can on Windows?" — deserves a proper answer, and it gets one below: two operating systems reading one damaged volume through different eyes will genuinely tell different stories. Along with a reassurance she couldn't have known: the chkdsk that wouldn't run was the luckiest failure of her week.

The decode: two readers, one torn book — and the repair that mercifully never ran

Why the Mac and Windows disagree: the drive is one book; the operating systems are two readers, each with its own tolerance for torn pages. A cross-platform external is formatted in a shared filesystem both systems speak, but they speak it through different driver implementations — and when directory structures are damaged, those implementations diverge exactly as she saw. The Mac's driver, meeting entries that fail its consistency checks, tends to omit what it can't validate: half the tree silently absent, no error, just gone from view. The Windows driver reads more permissively — it will list entries it can partially parse, and only error at the moment of use: folders visible, contents "corrupted or unreadable." Neither system is lying and neither is right; each is rendering its own partial reading of the same torn structures. The folders aren't "on Windows but not the Mac" — they're damaged on the drive, and each system draws its own line through the damage. Which is why the cure is neither system's view, but a reconstruction beneath both.

The blocked chkdsk, counted as luck: here's the part to be genuinely glad about. Chkdsk /f is a repair that writes — it amends structures to make the volume self-consistent by its own lights, and on a badly torn directory tree its idea of consistency can mean severing or orphaning the very entries a careful reconstruction would have saved, exactly as this archive's FOUND-folder cases document. The write-protection that blocked it — whatever its cause — and the admin rights they couldn't obtain functioned, between them, as an accidental safety catch: the volume reached the bench unrepaired, its damage original and legible, every reconstruction option intact. The honest instruction it converts to: when repair tools are blocked on a damaged drive, don't fight to unblock them — the block is doing the recovery a favour.

On the bench

The drive was imaged write-blocked behind the DeepSpar USB Stabilizer 10Gb — the volume captured exactly as the damage left it, untouched by any repair — and the single authoritative reading was built on the copy: the directory structures analysed and reconstructed until one complete tree stood where two partial views had argued, with OSForensics carving by signature for any entries torn beyond the structures. The training materials, the documents, the "missing" half of her drive — present all along behind the damage — were verified by opening and delivered on media that tells every computer the same story.

The outcome

The full folder tree reconstructed from the image and delivered verified — one truth replacing two partial ones. Free assessment, one fixed written figure including VAT, no recovery, no fee. Her mystery, resolved for every cross-platform drive owner: different systems render damaged structures differently — omission on one, visible-but-unreadable on the other — so contradictory views mean corruption, not migration; a blocked repair tool on a damaged drive is protection, not obstruction; and the cure is a write-blocked image and one careful reconstruction beneath both readers' opinions.

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.