Data Recovery Case File · Trust, Practice & Honest Limits · The Useful Sentence
Naming Your Fallback Before the Work Starts
His enquiry described the fault clearly and then did something better. A 240GB solid-state drive that "is no longer booting in its original machine. It won't initialise in Windows Disk Management when plugged into another machine in a drive caddy. I need to ideally recover the entire drive, but if all else fails then recovering a folder or two from within the desktop" would do. That second clause is worth more than the rest of the message. Most people state a requirement; he has stated a requirement and a floor — and having both, before any work begins, changes how the job is planned and how its result is judged.
| Media | 240GB solid-state drive — not booting in its original machine; failing to initialise when connected externally via a caddy; complete recovery preferred with a defined minimum acceptable outcome |
| Reported situation | Drive no longer booting · not initialising when connected externally · complete recovery sought · specific folders identified as an acceptable fallback |
| Fault class | Controller-level failure with no usable enumeration — vendor-mode access the realistic route; outcome not determinable in advance |
| Equipment used | Vendor technological and safe-mode access (PC-3000 portfolio, SSD support) · firmware area and translation-layer assessment · imaging sequenced against the stated fallback · losses reported per file |
The decode: why the fallback sentence matters so much
What it does to the plan: a recovery on a drive that may or may not stay accessible is a race against an unknown clock, and the sequence of the sweep decides the outcome. Knowing the floor means the identified folders can be located and captured first, before the bulk of the volume, so that the minimum acceptable result is banked while access is at its most reliable. Everything after that is upside. Without that sentence, the sensible default is a full sequential image — which is correct in general and can mean reaching the one folder that mattered at the very end.
What it does to the conversation afterwards: arguably more important. A recovery that returns eighty per cent of a drive is either a success or a failure depending entirely on what was in the missing twenty. Where a floor was agreed in advance, the result is measurable against something both parties accepted; where it was not, the same outcome becomes a disagreement about whether the job was done. That protects the customer as much as the firm, and it is the reason this archive asks for priorities as a matter of course.
What it does not do: it does not lower the ambition. The instruction remains to recover everything possible; the floor simply orders the work and defines the minimum success. Nobody stops at the fallback if more is available.
The technical position on his drive: not booting and not initialising externally is a complete elimination — the operating system, drivers, the caddy and the host machine are all ruled out. That places the fault at the drive's own controller, which on solid-state storage is the characteristic failure: the controller holds the address mapping and often the encryption, so when it fails the drive presents nothing usable. The route is vendor technological and safe modes, addressing the drive where normal start-up fails, assessing and repairing the firmware area, and imaging on restored access.
The honest limit that goes with it: where the failure lies in the memory rather than the controller's firmware state, reading the packages directly is not the dependable fallback it is on cards and sticks, because the mapping and keys live in the controller. So this is worth attempting and not guaranteed — which is precisely the situation in which a stated floor earns its value.
One thing to stop: repeated attempts to initialise it. Windows offering to initialise a drive is offering to write a fresh structure, and on a drive whose controller is struggling that is both futile and risky.
On the bench
Access was attempted through the PC-3000 portfolio's SSD support in the drive's vendor technological modes, with the firmware area and translation layer assessed for the corruption that typically prevents a drive completing start-up. Once addressing was restored, imaging was sequenced against his stated fallback — the named desktop folders located and captured first so that the minimum acceptable outcome was secured while access was most reliable, with the full volume taken afterwards. Losses were resolved to the individual files they affected and reported against the agreed floor rather than as a percentage.
The outcome
The controller addressed in vendor modes, the stated fallback secured first and the full volume imaged afterwards. Free assessment, one fixed written figure including VAT; where a chip has to be removed, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode, for anyone commissioning a recovery: state your floor as well as your goal, because a drive that may not stay accessible is a race and the order of the sweep decides the outcome — naming the folders you cannot do without lets those be captured first, with everything else as upside; and it makes the result measurable against something agreed rather than a matter of opinion afterwards. It does not lower the ambition; nobody stops at the fallback if more is available.
Commissioning a recovery when the outcome is uncertain
Tell them your minimum as well as your ideal. Say "I want everything, but if it comes to it, these two folders are what I actually can't lose" — and name them. That single sentence changes the work: on a drive whose access may not last, those folders can be located and captured first, while everything is at its most cooperative, with the rest of the volume taken afterwards as upside. Without it, the sensible default is to image the whole drive in order, which can mean reaching the one thing that mattered at the very end. It also protects you afterwards, because a partial result is either a success or a failure depending entirely on what's missing, and a floor agreed in advance makes that measurable rather than a matter of opinion. And stop letting Windows offer to initialise the drive.
Name your floor as well as your goal — call Glasgow Data Recovery on 0141 404 0294; controller addressed in vendor modes, your stated minimum captured first, losses reported per file.
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.