Data Recovery Case File · Second Fixes & Trade Handoffs · Establish What Was Already Done
Someone Has Already Worked on This, and the History Shapes the Job
His enquiry describes a drive that has already passed through capable hands. His original laptop drive, unrecognised after a system crash, where "my local trusted computer specialist swapped the drive and made initial attempts to recover the data" before the matter came further. A drive that has been worked on is not a fresh case — what was tried, and what state it was left in, shapes everything that follows and should be established before anything new begins.
| Media | Laptop hard drive unrecognised following a system crash — subject to a drive swap and initial recovery attempts by a prior technician |
| Reported situation | Original laptop drive not recognised after a system crash · drive swapped by a local technician · initial recovery attempts made by that technician · matter brought for further assessment · contents required |
| Fault class | Undetermined with prior intervention — nature and extent of earlier attempts determining the current state and the safe next step |
| Equipment used | Prior actions and their outcomes established before any new attempt · whether earlier attempts wrote to the drive determined · current state assessed against the reported history · imaged write-blocked before any further work · approach adjusted for interventions already made |
The decode: why the history is part of the diagnosis
Why a worked-on drive differs from a fresh one: its current state is the product of both the original fault and everything done since. Assessing it without knowing what was tried means mistaking the consequences of an attempt for the fault itself — and possibly repeating something that has already failed.
What "swapped the drive" needs to be clarified into: almost certainly replacing the laptop's drive so the machine could be returned to use, with the original set aside for recovery. That is a sensible separation — but it is worth confirming, because the word could mean other things, and the original drive's handling since matters.
What "initial attempts to recover" must be resolved into: the single most important question. Were those attempts read-only, or did they write to the drive? Running recovery software that only reads is harmless; running a repair, a consistency check, or anything that attempts to fix the drive alters it.
Why that distinction governs the next step: if the earlier work was read-only, the drive is in its original state and can be approached fresh. If it involved writing, the current state reflects those changes, and the reconstruction has to account for what was altered — a repair that discarded structures, a partition operation, a partial clone.
Why the technician being trusted and capable is relevant but not sufficient: competence at general computer work is real and valuable, and it is different from recovery. A good technician may run the standard tools — some of which write — because those are the tools the trade uses, and the outcome needs to be known regardless of skill.
What is worth asking him to obtain: from the technician, what specifically was run and what it reported. That conversation costs nothing and prevents both repetition and false assumptions, and a technician acting in good faith will answer readily.
Why the crash that started it matters too: a drive unrecognised after a system crash could be logical — a filesystem left inconsistent — or physical, with the crash a symptom of a failing drive rather than its cause. The earlier attempts may already have indicated which, which is more information worth having.
What must not happen until the history is clear: no new attempts layered on unknown ones. The drive is imaged first, so that whatever state it is in is preserved before anything further is tried.
On the bench
Prior actions and their outcomes were established before any new attempt — a worked-on drive's current state reflecting both the original fault and every subsequent intervention, so assessment without that history risks mistaking an attempt's consequences for the fault or repeating what has failed. Whether earlier attempts wrote to the drive was determined, read-only work leaving the original state intact while repair or checking alters it, and the drive imaged write-blocked before any further work.
The outcome
The prior actions established before any new attempt, write activity determined, and the drive imaged before further work. 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: someone has already worked on this. What was tried, and whether it wrote to the drive, shapes the whole job — so the history is established first, and the drive is imaged before anything new is layered on.
A drive someone has already attempted
Find out what was already done before anything new is tried — a worked-on drive's current state reflects both the original fault and every attempt since, so assessing it blind risks mistaking the consequences of an attempt for the fault. The key question is whether earlier attempts only read the drive or wrote to it: read-only recovery is harmless, while a repair or consistency check alters things and the reconstruction has to account for that. Ask the previous technician exactly what was run and what it reported — that costs nothing and a good-faith technician will tell you. Competence at general repair is real, and different from recovery.
Establish what was done first — call Easy Data Recovery on 028 9002 0144; prior actions established before any new attempt, write activity determined, drive imaged before further work.
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.