Data Recovery Case File · Portable Drives · Shared, and Therefore Unwitnessed
Several People Used It and Nobody Was Watching It
His enquiry describes an arrangement most households have. An external drive "that we use for our home laptops, that contains mainly photos of our family over the years plus a few basic files. Last night it just stopped work"ing. A drive shared between several machines and several people has a history nobody holds in full — which matters, because the most useful information about a failure is usually what happened immediately before it, and in a household nobody is quite sure.
| Media | 1TB external hard drive in shared household use across multiple machines — ceasing to function without warning; accumulated family photographic content held |
| Reported situation | Drive in routine shared use across household laptops · years of family photographs held · additional documents held · drive ceasing to function overnight · no symptom detail established · no prior warning reported |
| Fault class | Undetermined pending observation and use history — multiple users and hosts complicating establishment of preceding events |
| Equipment used | Household use history established across all users before assessment · observable symptoms recorded before power was applied · drive assessed on a native connection with the enclosure eliminated · imaged write-blocked · single-copy exposure addressed on delivery |
The decode: what a shared drive hides, and what to ask at home
Why the use history matters more here than usual: the single most informative thing about a failure is what was happening just before it. Was it being written to? Was it knocked? Did a machine crash while it was connected? Was it unplugged without ejecting? In a household, the person reporting the fault is frequently not the person who was last using it — so the answer exists and nobody has been asked for it.
The questions worth putting to everyone, without any suggestion of blame: who used it last, on which machine, what were they doing, and did anything happen — a knock, a crash, an unplug, a warning message ignored. People do not volunteer these things, partly because they do not know they matter and partly because nobody enjoys being the last person to touch something that broke.
Why the answers change the approach: a drive that was knocked is assessed for impact damage before power is applied. A drive that was connected to a machine that crashed is very likely a filesystem case with intact hardware. A drive unplugged mid-write is the same. Those are three different jobs and the difference between them is one conversation over breakfast.
What to establish about the drive itself, since the enquiry does not say: whether it spins, whether it makes any sound and of what character, whether a light comes on, and whether any of the household machines register it at all. Four answers that cost nothing and separate most fault families from each other.
Why multiple machines is genuinely useful information: a household drive has already been tested on several computers in the ordinary course of things. If none of them see it now, the hosts are eliminated more thoroughly than most people manage deliberately.
The structural point, and it is the one worth acting on afterwards: a shared drive accumulating years of family photographs is the household's single point of failure, and shared ownership makes it worse — because a resource everybody uses is a resource nobody is responsible for backing up. Nobody checks it, because everybody assumes somebody does.
What must not happen meanwhile: not everybody trying it on their own laptop in turn. That is the natural household response and it means the drive is powered five times in an evening.
On the bench
Household use history was established across all users before assessment — the most informative fact about a failure being what preceded it, and in shared use the person reporting the fault frequently not being the person who last used the drive. Observable symptoms were recorded before power was applied. The drive was assessed on a native connection with the enclosure eliminated, imaged write-blocked, and the single-copy exposure addressed on delivery.
The outcome
The use history established across the household, symptoms recorded before power and the drive imaged with the enclosure eliminated. 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: ask everyone in the house who used it last and what happened — a knock, a crash, an unplug. That one conversation distinguishes three quite different jobs, and the person reporting a fault is rarely the person who was there.
Shared family drive that has stopped working
Ask everyone in the house who used it last and what they were doing — without any suggestion of blame, because people don't volunteer these things. Was it knocked? Did a machine crash or freeze while it was connected? Was it unplugged without ejecting? Was there a warning message somebody dismissed? Those answers point at three quite different jobs: impact damage is assessed before power is applied, while a crash or an unclean unplug usually means intact hardware and a filesystem problem. In shared use the person reporting the fault is rarely the person who was there. Meanwhile, don't let everybody try it on their own laptop in turn — that's five power-ups in an evening.
Ask the household first — then call Guildford Data Recovery on 01483 901310; use history established across all users, symptoms recorded before power, enclosure eliminated on a native connection.
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.