Data Recovery Case File · Formatted & Logical Faults · A Sequence Worth Reading
Files Disappeared and Then the Drive Followed
Her enquiry was written under real pressure and contains two observations that between them are close to a diagnosis. "My drive has just disappeared. It was working absolutely fine, then the files disappeared, then the drive disappeared. It appears to be a software fault as the drive can still be detected on my friend's laptop. I am a teacher and it's decided to do this in the last couple of hours before I go back to school. I'm extremely worried that all my files have disappeared — it's years of work." The pressure is real and the outlook is better than she fears. The order of the two disappearances describes a specific kind of failure, and the fact that another laptop still detects the drive is the single most reassuring detail in the enquiry.
| Media | Portable drive holding several years of teaching material — files became inaccessible, followed by the volume itself; device still detected on a second computer |
| Reported situation | Progressive loss: file access failed first, volume disappeared subsequently · device still enumerated by another machine · years of work held · immediate professional deadline |
| Fault class | Progressive filesystem or partition failure over functioning hardware — contents intact behind structures that are no longer mounting |
| Equipment used | Write-blocked imaging before any repair · partition and filesystem reconstruction on the image · signature carving for anything beyond structural repair · files verified by opening; timescale confirmed in writing given the deadline |
The decode: what the order means, and why detection is the good news
Why the sequence matters: a drive that dies suddenly — hardware failure, a dead controller, a mechanical fault — usually vanishes in one step. Her drive did something different: the files became inaccessible first, and only afterwards did the volume itself stop appearing. That is the signature of a filesystem failing progressively rather than hardware stopping. The structures describing where files live became damaged, so the files could not be found; then the damage reached the point where the volume could no longer be mounted at all, so the drive stopped presenting. Both stages describe bookkeeping deteriorating, not data being destroyed.
Why the friend's laptop is the reassurance: it is the most useful test she ran, and she may not realise how much it settles. For another machine to detect the drive, the device must have received power, spun up or powered its controller, identified itself and completed the introduction. All of that is the hardware working. So the drive has not failed — it is a functioning device carrying a damaged filing structure, which is the most recoverable category in this archive. Her instinct that it "appears to be a software fault" is correct, and she reached it from good evidence.
What must not happen next, especially under deadline pressure: the temptation now is to fix it, and every available fix is harmful. Windows will offer to scan and repair; a Mac will offer First Aid; either may offer to initialise or format. All of those write to precisely the structures a reconstruction rebuilds from — and a repair tool run on a badly damaged volume converts something rebuildable into permanent structural loss, stripping filenames and folders in the process. On years of teaching material organised into folders, that difference is not academic. The pressure of a deadline is exactly what makes people press the button, which is why it is worth saying plainly: do nothing to it.
On the deadline itself: she should ask for a written timescale alongside the figure rather than a verbal estimate, and say plainly that she is working to a date. Structural reconstruction on functioning hardware is measured in days rather than weeks, and where a job is genuinely time-critical it can be sequenced to deliver the most needed material first. It is also worth telling her school now rather than later — institutions handle this kind of thing routinely and respond far better to being told in advance.
On the bench
The drive was imaged write-blocked in one pass before any repair was contemplated, which is the discipline no repair utility can offer — everything afterwards happened against a copy, and the original was never modified. On the image the structures were examined in order, partition records first and then the filesystem, establishing which layer had failed and how far the damage extended. That layer was reconstructed until the volume mounted from the copy with its folder tree, filenames and dates intact, and signature carving swept alongside for anything beyond structural repair. Her material was verified by opening, and a written timescale was confirmed at the outset given the deadline.
The outcome
The volume rebuilt from a write-blocked image with folders and filenames intact, verified and delivered to a written timescale. Free assessment, one fixed written figure including VAT, no recovery, no fee. The decode, for anyone whose drive faded rather than died: the order is diagnostic — files becoming inaccessible before the volume disappears describes a filesystem deteriorating rather than hardware stopping, and neither stage destroys data; a drive still being detected on another computer proves the hardware works, which places the fault in the recoverable category; and under deadline pressure the one thing to resist is fixing it, because every repair, initialise and format offer writes over exactly what a reconstruction rebuilds from.
Files gone, then the drive gone, with a deadline
Do nothing to it — that's the hardest advice to follow under time pressure and the most important. Every offer your computer makes now is destructive: scan and repair, First Aid, initialise, format. Each writes over the structures a proper recovery rebuilds from, and on a badly damaged volume a repair tool turns something rebuildable into permanent loss, stripping your folders and filenames along the way. Take encouragement from what you've already established. If the drive is still detected on another computer, its hardware is working — power, controller and identification all succeeded — so this is a filing problem rather than a failed device. And files disappearing before the drive did describes structures deteriorating rather than hardware stopping. Ask for a written timescale as well as a figure, say you're working to a date, and tell your employer now rather than after the deadline.
Don't let anything repair it — call Glasgow Data Recovery on 0141 404 0294; imaged write-blocked, structures rebuilt on the copy, folders and filenames preserved, timescale in writing.
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.