Data Recovery Case File · Solid State & Flash · RAW, When It Finally Connects

"Finally" is the headline: why intermittent connection outranks the RAW verdict — an SSD imaged inside its shrinking windows, the filesystem question answered on the copy, and the cost question answered with a figure instead of a range

His report was the restrained, careful kind, and its most important word was hiding mid-sentence. The drive: a 240GB SSD, used for data storage only. The state: "inaccessible… Disk Management, when it finally connects, shows it as RAW. Other than removing it from my laptop to put it in a caddy, I've not done anything else." The ask: "what might the range of costs look like?" Two decodes, in the order of what matters. First: on this drive, "finally" outranks "RAW." RAW is Windows saying "a volume is here but I can't identify its filesystem" — ordinarily a corruption verdict — but on an SSD that takes its time even to connect, the garbled structures are more likely a symptom than the disease: a controller in decline, serving unstable reads, so that whatever Windows samples where the filesystem should be arrives as noise. Intermittent connection on solid state is this archive's closing-window signature in its SSD form — a countdown, not a quirk — and it reorders the whole plan: image first, inside the windows that remain, and argue about the filesystem afterwards, on the copy. Second: his cost question, answered honestly — there is no range, and this page explains why a range is exactly what a careful buyer shouldn't accept.

The decode: why "finally" wins, and why ranges lose

RAW, re-read in context: on a healthy drive, RAW is a bookkeeping verdict — structures torn, territory intact, the rebuild-on-image case this archive documents at length. But the verdict assumes the witness is reliable: Windows read where the filesystem lives and found nonsense. On a drive that only sometimes deigns to connect, that assumption collapses — a declining SSD controller serves marginal, inconsistent reads, and "nonsense where the structures should be" is exactly what unstable reads look like whether or not the structures are damaged at all. So RAW here is unproven either way, and — the practical point — unimportant to prove right now: whichever it is, the answer lives on a complete image, and the intermittency says the chance to take one is being rationed. The plan writes itself: characterise the windows, capture everything inside them, single session, priorities first — and let the RAW question be settled at leisure on a copy that never flickers.

His restraint, banked: "other than the caddy, I've not done anything else" is the sentence every bench hopes to read. No repair utilities aimed at structures that may be phantoms of bad reads; no format accepted; no scan tools grinding a declining controller through hours of sustained work. A drive in countdown arrived with its countdown unspent — which is, more than any tool, why this case ends well.

The range question, answered without one: "what might the range of costs look like?" is a sensible buyer's question shaped by trades where ranges are honest. In recovery, a range is usually the opposite: it's an estimate wearing a safety margin, and estimates are how figures grow — the low end quoted, the high end invoiced, the middle a negotiation. The honest structure replaces the range with a sequence: the assessment (free) establishes the fault; the fault sets one fixed figure, in writing, VAT included, before any work; and no-recovery-no-fee caps the downside at zero. The truthful answer to "what's the range?" is therefore: from nothing (if we fail, or you decline the written figure) to exactly one number you'll see before committing — which is narrower than any range and firmer than any estimate. Careful buyers shouldn't want the bracket. They should want the sequence.

On the bench

The drive went straight onto the Atola TaskForce 2's native connection and its windows were characterised rather than wished away: enumeration behaviour mapped, and the image captured inside the availability the controller still offered — complete, single-session, priorities first, the countdown spent on the one act that mattered. The PC-3000 platform road stood ready for a controller that stopped answering; it wasn't needed. On the finished image, the RAW question finally got its fair trial: the structures assessed on stable ground, reconstructed where genuinely torn, and the volume stood up. His files were verified by opening and delivered — under the one written figure that had replaced the range, fixed at assessment and never revisited.

The outcome

The SSD imaged completely inside its remaining windows, the RAW verdict retried and resolved on the copy, and the data delivered verified — for a fixed written figure, not a range. Free assessment, one fixed written figure including VAT, no recovery, no fee. The two answers, posted for every careful owner in his position: on an intermittently-connecting SSD, "finally" outranks "RAW" — the corruption verdict is unreliable testimony from unstable reads, and the only urgent act is a complete image inside the windows that remain; and on costs, decline the range and demand the sequence — free assessment, one fixed figure in writing, nothing owed on failure. A bracket is an estimate's disguise. A figure is a commitment.

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.