Data Recovery Case File · Desktop Externals & Aging Drives · The Compromise Format
A Filesystem Chosen for Compatibility Trades Away Its Own Resilience
Her enquiry describes a sensible setup that failed in a characteristic way. A drive "previously formatted to read on both platforms, but somewhere along the line the data became inaccessible or unreadable on both." Choosing a shared format is the obvious solution to using one drive with two systems — and the formats that both understand are generally the ones with the least protection against exactly this.
| Media | 1TB external hard drive formatted for cross-platform compatibility — volume no longer readable by either operating system |
| Reported situation | Drive formatted to be readable by two operating systems · used across both · content becoming inaccessible · volume unreadable on both platforms · owner seeking indication of cost and timescale before committing |
| Fault class | Cross-platform filesystem structure damage — format lacking journalling and redundancy present in native filesystems; content retained and reconstructible |
| Equipment used | Filesystem type identified as determinative of both cause and approach · imaged write-blocked before any interpretation · allocation and directory structures examined against their limited duplicates · content reconstructed from structures where present and by signature where not · files validated by opening |
The decode: why the shared format is the fragile one
Why a shared format was needed at all: each operating system has its own native filesystem, and support for the other's is partial or absent. A drive used by both has to be in something they both understand, which narrows the choice considerably.
What those formats give up: the protections the native ones added. Modern native filesystems keep a running record of intended changes, so an interruption can be resolved by consulting it — the cross-platform options generally do not.
Why that matters most at exactly the wrong moment: without such a record, a write interrupted partway leaves the structures inconsistent with no way to determine what was intended. The filesystem cannot repair itself, and the volume becomes unreadable rather than briefly inconsistent.
Why moving between two systems increases the exposure: a drive disconnected from one machine and attached to another is disconnected more often. Every removal is an opportunity for a write to be interrupted, and cross-platform use multiplies them.
Why one platform's handling of the other's removals compounds it: systems differ in how aggressively they cache writes and how they respond to a device disappearing. A drive removed safely on one may not have been fully settled by the other's standards.
Why becoming unreadable on both is expected rather than surprising: the damage is in the volume, not in either system. Both machines are reading the same broken structures and reaching the same conclusion, which confirms the fault belongs to the drive.
Why the outlook is nevertheless good: the simplicity that makes these formats fragile also makes them straightforward to reconstruct. Their structures are well documented and their layout is predictable, and content is generally stored contiguously.
What limited redundancy they do have: most keep a second copy of their principal allocation table. Where the primary is damaged the backup frequently survives, and it describes the same arrangement.
What is worth knowing for afterwards: the practical alternative is not a better shared format. It is using a native format on each side with copies passed between them, so a single volume is never the thing both machines are writing to.
What must not happen meanwhile: no repair utility on either platform. Two systems each offering to fix the same volume is two chances to have entries discarded.
On the bench
The filesystem type was identified as determinative of both cause and approach — cross-platform formats being those both systems understand and generally lacking the running record of intended changes that native filesystems use to resolve interrupted writes, so an interruption leaves structures inconsistent with no means of self-repair. Use across two systems multiplies disconnections and therefore exposure. Allocation and directory structures were examined against their limited duplicates, most such formats retaining a second allocation table.
The outcome
The filesystem type identified as determinative, the drive imaged before interpretation, and structures examined against their duplicates. 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: the format that both systems read is the one with least protection. Native filesystems keep a record letting them resolve an interrupted write; the shared ones generally do not — so an interruption becomes unreadable rather than briefly inconsistent.
A drive shared between two operating systems
Don't run a repair utility on either platform, since two systems each offering to fix the same volume is two chances to have entries discarded. Understand the trade you made: formats both systems understand generally lack the running record of intended changes that native filesystems use to resolve an interrupted write, so an interruption leaves structures inconsistent with no way to self-repair. Moving a drive between machines also multiplies disconnections. For afterwards, the better arrangement isn't a different shared format — it's a native format on each side with copies passed between them.
Don't repair it on either — call Manchester Data Recovery on 0161 871 0788; filesystem type identified as determinative, imaged before interpretation, structures examined against their duplicates.
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.