Data Recovery Case File · Formatted & Logical Faults · Correct About the Drive
The Manufacturer's Diagnosis: Right, and Incomplete
Her enquiry came with a diagnosis already attached, and an unusually good one. Having contacted the manufacturer about a portable backup drive, she was told that "the file system on the drive has been corrupted. File system corruption generally does not indicate a problem with the drive itself, only that the data was not written correctly. It most often occurs when an unscheduled communication break has taken place between the drive and the host — unsafe removal of the drive by not using the safe removal icon" and similar causes. That explanation is accurate, well expressed and genuinely helpful, and this page says so. But it answers a question about the drive, and she has a question about her data — and the advice that follows from the first is the opposite of what serves the second.
| Media | Portable external backup drive — filesystem corruption diagnosed by the manufacturer's support team; hardware not implicated; contents required |
| Reported situation | Drive malfunctioning · manufacturer consulted and diagnosis provided · corruption attributed to interrupted communication with the host · data recovery not addressed by that advice |
| Fault class | Filesystem structure damage over working hardware — contents intact behind unreadable records; manufacturer remedy would resolve the device at the cost of the data |
| Equipment used | Write-blocked imaging before any repair · partition and filesystem reconstruction on the image · signature carving for anything beyond structural repair · contents verified by opening and delivered |
The decode: what they got right, and the gap in the advice
What their explanation gets right: nearly everything, and it is worth reinforcing because it is the most useful thing anyone has told her. Filesystem corruption really does not indicate a failing drive — the hardware can be in perfect health while the records describing where files live have become inconsistent. And the cause they identify is the correct one: an interrupted conversation between the drive and the computer. Operating systems hold recent changes in memory and commit them in batches, so pulling a drive out, losing power, or a cable disconnecting mid-write leaves the filing structure part-updated. Do that once and nothing happens; do it repeatedly and the inconsistencies accumulate until the volume will no longer mount.
Why that is genuinely good news: it places her firmly in the most recoverable category in this archive. Working hardware, intact data, damaged bookkeeping. The files are physically present exactly where they were written.
The gap in the advice: and it is not a criticism of the manufacturer, whose responsibility is the product. Support teams answer the question "is my drive faulty?" — and having correctly concluded that it is not, the natural next step they will offer is to reformat it, which restores the device to full working order. That advice is entirely correct for the drive and catastrophic for the data, because formatting writes fresh empty structures over exactly the damaged ones a reconstruction rebuilds from. So the sequence to be careful of is: an accurate diagnosis, a reasonable-sounding remedy, and a customer who follows it because everything they have been told so far was true.
What to do instead: the recovery and the repair are two different jobs and the order is fixed. Get the data off first, from an image rather than the original, with the filesystem rebuilt on the copy so the folders, filenames and dates come back intact. Then reformat the drive, if she wants to keep using it — at which point the manufacturer's advice becomes exactly right.
One practical note on the cause: their diagnosis also tells her how to avoid a repeat. Ejecting is not a formality — it flushes writes still held in memory and closes the filesystem cleanly — and on a drive holding backups it is worth the two seconds every time.
On the bench
The drive was imaged write-blocked in one pass before anything was contemplated, which is the discipline that separates recovering data from restoring a device. On the image the structures were examined in order, partition records first and then the filesystem, to establish which layer the accumulated interruptions had damaged — and that layer was reconstructed until the volume mounted from the copy with its folder tree, filenames and dates intact. Signature carving swept alongside for anything beyond structural repair. Her files were verified by opening rather than counted, and the drive was returned for reformatting afterwards.
The outcome
The volume rebuilt from a write-blocked image with structure intact, verified and delivered, and the drive returned for reformatting afterwards. Free assessment, one fixed written figure including VAT, no recovery, no fee. The decode, for anyone given a manufacturer's diagnosis: on filesystem corruption they are usually right, and the news is good — the hardware is healthy and your files are physically present behind damaged records, which is the most recoverable situation there is; but their remit is the product, so the remedy they offer next is to reformat, and that is correct for the drive and fatal for the data; recovery and repair are two jobs in a fixed order, so get the data off an image first and reformat afterwards. And take their advice about ejecting seriously.
Told your drive has filesystem corruption
Take the diagnosis as encouraging and be careful with the remedy. Filesystem corruption genuinely doesn't mean a failing drive — your hardware is fine and your files are physically present behind records that have become inconsistent, usually because the conversation between drive and computer was interrupted mid-write. That's the most recoverable position there is. But whoever diagnosed it was answering "is the drive faulty?", and the natural next step they'll suggest is to reformat, which restores the device perfectly and writes empty structures over exactly what a recovery rebuilds from. Don't do it in that order. Get the data off first, from an image rather than the original, and ask specifically for the filesystem to be rebuilt so your folders, filenames and dates come back. Reformat afterwards if you want to keep using the drive — and eject it properly from now on.
Recover first, reformat second — call Glasgow Data Recovery on 0141 404 0294; imaged write-blocked, structures rebuilt on the copy, folders and dates returned intact.
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.