Data Recovery Case File · Solid State & Flash · They Were Reading Nothing
Software Scanning a Drive That Returns Nothing Will Scan for Hours and Find Nothing
His enquiry documents a thorough and futile campaign. A solid-state drive that showed as fully unallocated after a critical failure, against which he ran four separate recovery programs — one scanning overnight for a projected forty-four hours, another finding three files. His conclusion, that the problem is at chip level, is very likely right — and the reason is that all four tools were asking a controller that cannot reach the memory, so they were scanning emptiness.
| Media | 500GB solid-state drive — reported as entirely unallocated and uninitialised following a critical system failure; four consumer recovery tools returning effectively nothing |
| Reported situation | Machine experiencing a critical failure and not restarting · drive reinstalled as a secondary device · volume management reporting the drive fully unallocated and uninitialised · four recovery tools run against it · one scan left running overnight without result · another returning three files in trial · under a gigabyte of work documents required |
| Fault class | Controller unable to present the memory — software scans reading an empty address space rather than stored content; access below controller level indicated |
| Equipment used | Consumer scan results interpreted as absent access rather than absent data · device addressed through hardware with imposed timeouts rather than the host stack · controller state assessed in vendor technological modes · chip-level read past the controller with translation layer reconstructed in software · document structures carved and validated by opening |
The decode: why all four found nothing, and why that is not a verdict
What every one of those tools does: asks the operating system to read the drive, sector by sector, and examines what comes back for recognisable file structures. Every one of them depends entirely on the drive returning content when asked.
Why they all returned nothing: the drive is reporting itself as unallocated, which means the controller is presenting an address space it cannot fill. When software reads that space, it receives zeroes — so the scan proceeds normally, finds no file signatures anywhere, and reports nothing found.
Why the forty-four hour scan is the clearest evidence: a scan estimating that long is working through the full capacity at a reasonable rate. The tool was reading successfully and getting empty data, which is a very different situation from a tool that stalls or errors.
What that distinguishes: a drive that returns nothing from a drive that has nothing. The scans establish that no content is being presented; they say nothing about whether content exists in the memory — and those are separate questions the software cannot tell apart.
Why running four made no difference: they share one dependency. All of them read through the operating system, which reads through the controller — so a controller that cannot reach the memory produces the same emptiness for every tool, however capable.
Why the three files found in trial are worth explaining: small finds like that typically come from residual structures or a fragment the tool assembled. They do not indicate that the drive is mostly empty — they indicate that almost nothing is being returned.
Why his conclusion is sound: he reasoned that if nothing readable is being presented, the answer must lie below the level everything he tried operates at. That is exactly right, and it is the reason chip-level work exists.
What that involves: the drive addressed through hardware that does not rely on the controller presenting a usable address space, the controller assessed and where necessary bypassed, and the memory read directly with the pattern by which content was distributed rebuilt in software.
Why under a gigabyte of documents is a favourable target: a small quantity of text-based work reduces what must be reconstructed. Documents carry recognisable structures and are carved reliably once the raw memory content is available.
What must not happen: no further scans, no initialising, and no accepting any offer to prepare the drive. Further scanning costs time and finds the same nothing, while initialising writes to a device whose contents have not yet been reached.
On the bench
Consumer scan results were interpreted as absent access rather than absent data — recovery tools reading through the operating system and therefore through the controller, so a controller presenting an address space it cannot fill returns zeroes to every scan, which proceeds normally and reports nothing found, with a lengthy completed scan confirming successful reading of empty data rather than stalling. Four tools sharing that dependency produce identical results. Chip-level reading was performed past the controller.
The outcome
The scan results read as absent access, the device addressed through hardware, and the memory read past the controller. 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: your conclusion was right. All four tools read through the same controller, and a controller that cannot reach the memory returns emptiness to every one of them — so they scanned successfully and found nothing, which is not the same as nothing being there.
When several recovery programs all find nothing
Stop running more of them — they share one dependency, so the result won't change. Every consumer recovery tool reads through the operating system, which reads through the drive's controller, and a controller that can't reach the memory presents an address space full of zeroes. The scan then runs perfectly normally and finds no file signatures anywhere. A long scan completing is actually the clearest sign of this: the tool was reading successfully and getting empty data, rather than stalling or erroring. That distinguishes a drive returning nothing from a drive containing nothing, and only the first is what your scans measured. Don't initialise it.
Stop scanning — call Easy Data Recovery on 028 9002 0144; scan results read as absent access rather than absent data, addressed through hardware with imposed timeouts, memory read past the controller.
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.