Data Recovery Case File · Portable Drives · The Common Factor Is Not a Drive
Two Devices Failing the Same Way Are Reporting About Something They Share
His enquiry contains a diagnosis he has almost written himself. A new 4TB drive onto which he has been collating "literally all the data and files I own, which has suddenly had a corrupted filesystem. It was often not mounting, and I have the same issue with a 500GB drive" using the same format. Two different drives, of different makes and ages, with the same symptom and the same filesystem — which points at the filesystem and the way both were used rather than at either device.
| Media | Two external hard drives of differing make, age and capacity — both using a cross-platform filesystem without journaling; both exhibiting mount failures and structural corruption |
| Reported situation | Recently purchased 4TB drive used to consolidate the owner's complete file collection · filesystem corruption occurring · drive frequently failing to mount beforehand · second older drive of a different make exhibiting the same behaviour · both formatted with the same cross-platform filesystem · contents required |
| Fault class | Filesystem-level corruption from unclean dismounts on a non-journaling format — common across devices; hardware not implicated by the pattern |
| Equipment used | Common factor identified across both devices before any hardware assumption · drive health confirmed independently on each by self-reported attributes · both imaged write-blocked before any reconstruction · structures rebuilt from surviving copies · dismount practice addressed on delivery |
The decode: what the two drives have in common
Why two failures with a shared characteristic is a finding: the drives differ in make, age and capacity, so a hardware explanation would require two unrelated devices to fail identically at the same time. What they share is the filesystem and the person using them, and those are the candidates.
What that filesystem is for: being readable and writable by every platform. That is genuinely useful and it is why people choose it — a drive that works everywhere solves a real problem.
What it lacks, and this is the weakness: journaling. A journaling filesystem records what it is about to do before doing it, so an interruption partway leaves a record that allows the incomplete operation to be finished or undone on the next mount. This format has no such record.
So what an interruption does to it: leaves the structures partly updated with no way to reconcile them. Unplugging without ejecting, a machine sleeping with the drive attached, a cable knocked, or power lost mid-write all produce inconsistency that the filesystem cannot repair itself out of.
Why his precursor observation is the confirmation: the drive was often not mounting before it failed properly. That is accumulated inconsistency — each unclean dismount leaving a little more damage, until the volume could no longer be interpreted at all. He noticed the pattern and did not know it was one.
Why the second drive doing the same thing settles it: two devices, one format, one workflow. The hardware is not the variable.
What to change, and it is practice rather than equipment: eject before disconnecting, every time. Prevent the machine sleeping while a drive is attached. And where a drive lives with one platform, use that platform's own journaling filesystem instead, accepting the loss of cross-platform writing.
The other thing worth saying: consolidating everything he owns onto one drive means that drive holds his only copy. The filesystem choice made it fragile and the consolidation made it critical, which is an uncomfortable combination.
On the bench
The common factor was identified across both devices before any hardware assumption — two drives differing in make, age and capacity sharing a filesystem and a usage pattern, which are the variables a hardware explanation cannot account for. Drive health was confirmed independently on each by self-reported attributes. Both were imaged write-blocked before any reconstruction, the filesystem in question lacking a journal and therefore retaining no record from which an interrupted operation can be reconciled.
The outcome
The common factor identified before any hardware assumption, each drive's health confirmed independently, and structures rebuilt from surviving copies on both. Free assessment, one fixed written figure including VAT per drive; 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: two drives of different makes and ages failing identically are reporting about what they share. That filesystem has no journal, so an interrupted write leaves inconsistency it cannot repair — and your drive often failing to mount beforehand was that accumulating.
More than one drive with the same fault
Look at what they have in common rather than at either device — two drives of different makes and ages failing identically is not a hardware coincidence. If they share a cross-platform filesystem, that's very likely the answer: those formats are chosen because every platform reads and writes them, and the trade-off is that they keep no journal. A journaling filesystem records what it's about to do before doing it, so an interruption can be reconciled on the next mount; without one, an unclean dismount leaves damage that accumulates. Eject every time, stop the machine sleeping with drives attached, and use a journaling format where a drive lives with one platform.
The common factor is the clue — call Oxford Data Recovery on 01865 593000; shared variable identified before any hardware assumption, each drive's health confirmed independently, structures rebuilt from surviving 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.