Data Recovery Case File · Solid State & Flash · Borrowed Vocabulary
There Are No Sectors, and the Finding May Still Be Right
His enquiry quotes a written assessment from a previous provider. A 1TB solid-state drive that failed while transferring a large file, where "the forensic and research teams have both finished their attempts in trying to get through the bad sectors in order to access the data, but unfortunately we have not been successful." Solid-state drives do not have sectors in the sense that phrase implies — the vocabulary is inherited from mechanical drives, and understanding what it stands in for changes how the finding should be read.
| Media | 1TB SATA solid-state drive — failing during a sustained large-file write; assessed by a previous provider reporting unreadable regions and no recovery achieved |
| Reported situation | Drive failing during transfer of a large file · assessed by a previous data recovery provider · provider reporting inability to read through affected regions · no recovery achieved · written finding supplied to the owner · contents required |
| Fault class | Uncorrectable read failure at block level with the controller partly functional — prior methods and translation layer handling to be established |
| Equipment used | Previous provider's methods and translation layer handling established before assessment · read distribution mapped at block level rather than by logical address · vendor technological modes attempted with the drive's own mapping preserved · position stated honestly before any charge |
The decode: what the borrowed words stand for
Where the vocabulary comes from: a mechanical drive stores data in physical sectors on a platter, at fixed locations, and a bad sector is a specific patch of surface that can no longer be read. The word describes a place. Every tool, every error message and every technician's habit of speech was formed around that model, and it carried over to devices built entirely differently.
What a solid-state drive has instead: memory arranged in pages and blocks, with a controller deciding where each piece of data physically lives and maintaining a map from the addresses a computer asks for to the locations it used. The same logical address can sit in a different physical place tomorrow, because the controller moves data around to spread wear evenly.
So what "bad sectors" actually means here: logical addresses the drive will not return data for. That could be memory whose stored charge has drifted beyond what error correction can reconstruct. It could be a mapping the controller can no longer resolve, in which case the memory is intact and the record of where it went is not. Those are very different situations behind identical language.
Why the distinction matters for a second opinion: if the memory itself has degraded, a further attempt will find the same thing and there is no honest reason to charge for confirming it. If the controller's mapping is damaged, the data may be intact behind a resolvable fault — and whether the previous provider addressed that is the question worth asking.
So the question to put to them: were the affected regions read through the controller, at logical addresses, or was the memory examined at block level with the mapping reconstructed. Those are different depths of work, and a finding of unreadable regions means something quite different depending on which was done.
Why the timing is consistent either way: the drive failed during a large file transfer, which is sustained heavy writing — the operation that most thoroughly exercises a device. That is when marginal media reveals itself, and when a controller under load is most likely to encounter something it cannot resolve.
Being honest about the outlook: a provider describing forensic and research effort has generally done real work, and their failure is meaningful. A second attempt is worth making when the first left a question open and not worth buying when it did not — and the answers above decide which applies.
On the bench
The previous provider's methods and translation layer handling were established before assessment — unreadable regions meaning something materially different depending on whether they were read through the controller at logical addresses or examined at block level with mapping reconstructed. Read distribution was mapped at block level rather than by logical address, a controller relocating data so that logical and physical positions do not correspond. Vendor technological modes were attempted with the drive's own mapping preserved, and the position stated honestly before any charge.
The outcome
The previous methods established, read distribution mapped at block level and the position stated before any charge. Free assessment, and no charge where nothing further is possible. The decode: the words are borrowed from mechanical drives, where a bad sector is a patch of surface. A solid-state drive has a controller deciding where data physically lives, so "unreadable regions" can mean degraded memory or a mapping the controller cannot resolve — and only one of those is a dead end.
Told your solid-state drive has bad sectors
Ask whether the affected regions were read through the controller or examined at block level with the mapping reconstructed — those are different depths of work and the same phrase covers both. The vocabulary is borrowed from mechanical drives, where a bad sector is a specific patch of platter that can no longer be read. Solid-state drives have no such thing: a controller decides where each piece of data physically lives and maintains a map, so the same address can sit somewhere different tomorrow. That means "unreadable regions" might be memory whose charge has degraded, which is final, or a mapping the controller can't resolve, where the data is intact behind a fault. Worth knowing which was found.
Ask what depth was attempted — then call Guildford Data Recovery on 01483 901310; previous methods established first, read distribution mapped at block level, position stated honestly before any charge.
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.