Data Recovery Case File · Portable Drives · Collateral From Another Problem
The Drive Was Not the Thing That Was Wrong
Her enquiry describes a failure caused by an action taken about something else entirely. Installing software on a laptop that "started going very slowly, so I decided to restart the laptop — with the external hard drive connected. When I turned it back on, the laptop d"id not see it. The slow machine was the problem she was solving. The drive was simply attached at the moment she solved it, and a restart performed while a system is struggling does not put connected volumes away cleanly.
| Media | External hard drive mounted during a host restart performed while the system was unresponsive — not presented by the host afterwards |
| Reported situation | Software installation in progress on a laptop · system becoming very slow · machine restarted by the owner with the external drive connected and mounted · drive not appearing after restart · contents required |
| Fault class | Filesystem left inconsistent by an unclean dismount during a forced restart — content unaffected |
| Equipment used | No repair utility permitted on either platform · imaged write-blocked before any reconstruction · structures rebuilt on the image from surviving backup copies · signature carving alongside · files validated by opening |
The decode: what a restart does to a mounted volume, and why the slowness matters
What a clean shutdown does for external drives: the system flushes outstanding writes to each mounted volume, updates the structures describing them, and marks each one cleanly unmounted before power is removed. That last step is a flag recording that the volume was put away properly, and it is what lets a host trust the filing structures next time.
What a restart during a struggling system does instead: often none of that. A machine that is slow or unresponsive may not complete its shutdown sequence — and where a restart is forced, it certainly does not. So outstanding writes are lost, structures mid-update are left half-written, and the volume is never marked as cleanly closed. The next host reads structures it cannot reconcile and declines to mount.
Why the software installation is relevant: installations write heavily and can touch connected volumes — caching, temporary files, or simply keeping the system busy enough that the external drive's writes were still queued. A slow machine is a machine with work outstanding, and outstanding work is exactly what a restart discards.
Why none of this touched her files: the damage is to the small structures describing the volume, not the data area. Photographs, documents and everything else sit where they were written. An unclean dismount damages the catalogue, not the contents, and it is among the more routinely recoverable conditions in this archive.
Why filesystems usually survive this and hers did not: most modern filesystems keep a journal — a record of intended changes written before they are made, so an interruption can be reconciled on the next mount. Not all volumes have one, and where the interruption catches structures outside the journal's protection, the automatic reconciliation cannot resolve it.
What must not be run: the repair utility. Both platforms will offer one for a volume that will not mount, and both write their conclusions over the structures a rebuild would use — where those conclusions are drawn from half-written information, the result frequently mounts with much of the content missing.
The habit worth keeping: eject external drives before restarting, and especially before forcing a restart. It takes seconds, and a machine that is too slow to shut down is precisely the machine where it matters most.
On the bench
No repair utility was permitted on either platform, both offering one for a volume that will not mount and both writing conclusions drawn from half-written information over the structures a rebuild depends on. The drive was imaged write-blocked before any reconstruction, and structures rebuilt on the image from their surviving backup copies — an unclean dismount damaging the catalogue rather than the data area, so files return with folders and original names. Signature carving ran alongside and files were validated by opening.
The outcome
The drive imaged before any reconstruction and the structures rebuilt from their surviving copies. 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: a clean shutdown flushes outstanding writes to each mounted volume and marks it properly closed, and a restart forced on a struggling machine does neither. So structures were left half-written and no host will trust them — while your files sit untouched in the data area. Refuse any offer to repair it.
External drive lost after restarting a slow computer
Don't let either machine repair it — both will offer, and both write conclusions drawn from half-written information over exactly what a rebuild needs. Your files are fine. A clean shutdown flushes outstanding writes to every mounted volume, updates its structures and marks it properly closed, which is what lets a computer trust those structures next time. A restart forced while the system is slow or unresponsive does none of that, so writes are lost, structures caught mid-update are left half-written, and the volume is never flagged as cleanly closed — which is why nothing will mount it now. The damage is to the catalogue rather than the contents. In future, eject external drives before restarting, particularly when the machine is struggling.
Don't repair it — call Guildford Data Recovery on 01483 901310; imaged write-blocked before any reconstruction, structures rebuilt from their surviving copies, files checked by opening.
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.