Data Recovery Case File · Cameras, Drones & Cards · Stopping Was the Skill
A Device That Degrades With Each Attempt Is Spending Something It Cannot Replace
This enquiry describes exactly the right sequence of decisions. A 64GB card in an adapter showing as an unformatted volume, where retrieved data was unreadable and "the card seems to be further malfunctioning when plugged in, so this has been removed and kept in an anti-static bag until able to find a suitable specialist." Recognising deterioration and stopping is rarer than any technical knowledge, and it is why this case has a good prospect rather than a poor one.
| Media | 64GB memory card in an adapter — presenting as an unformatted volume; retrieved content unreadable; behaviour deteriorating across successive connections; approximately 50GB occupied |
| Reported situation | Memory card presenting as an unformatted volume · content retrieved by the owner proving unreadable · behaviour observed to deteriorate on successive connections · card removed from use on that basis · card stored in antistatic packaging pending specialist assessment · alternative adapters tried without success · mixed photographic and video content held |
| Fault class | Progressive controller or translation-table degradation — volume descriptor unreadable while content regions substantially retained; deterioration proportional to powered attempts |
| Equipment used | Owner-observed deterioration accepted as a limit on powered attempts · card read on fixed contact equipment under a single controlled session · memory read past the controller where the card did not present reliably · translation layer reconstructed in software from the raw arrangement · content carved by signature and validated by opening |
The decode: what raw means, and why each attempt cost something
What an unformatted reading actually reports: a descriptor that could not be interpreted. The host looks for a structure identifying the filesystem, does not find one it recognises, and reports the volume as raw.
Why that says nothing about the content: the descriptor is tiny. A few hundred bytes at a known position determine whether a volume is recognised, and the files are elsewhere entirely.
Why the occupied figure supports that: something reported it. A capacity figure consistent with what he expects means the card is still describing itself.
Why data retrieved by consumer software was unreadable: it was read through a failing translation. The controller maps logical positions to physical memory, and a degraded mapping returns the wrong regions — producing files of the right size containing the wrong content.
Now the deterioration he observed, which is the important part: it is real. A controller struggling to maintain its mapping can corrupt it further on each power-up as it attempts maintenance.
Why that makes attempts genuinely costly: the mapping is not stored anywhere else. Each degradation of it makes reconstruction harder, and enough of them make it impossible.
Why stopping when he did is worth more than any tool: he preserved the remaining mapping. Most cards in this state arrive after dozens of attempts and are correspondingly worse.
Why antistatic storage is a sensible precaution and a minor one: it protects against a real but unlikely risk. The important thing he did was not connecting it.
How it is approached now: once, and deliberately. The card is read in a single controlled session on fixed contact equipment rather than in repeated attempts.
Why the memory is addressed past the controller where needed: it removes the failing element. Reading the packages directly and reconstructing the arrangement in software bypasses the mapping that is degrading.
On the bench
Owner-observed deterioration was accepted as a limit on powered attempts — a raw reading reporting only that a small descriptor could not be interpreted, with content held elsewhere, while a controller struggling to maintain its logical-to-physical mapping can corrupt that mapping further on each power-up as it attempts maintenance. The mapping exists nowhere else, so each degradation makes reconstruction harder. The card was read in a single controlled session and memory addressed past the controller.
The outcome
Observed deterioration accepted as a limit on attempts, the card read in one controlled session, and memory addressed past the controller. Free assessment, one fixed written figure including VAT; on cards where content has been deleted or overwritten, the figure is payable upfront. The decode: noticing it was getting worse and stopping is worth more than any tool. Most cards in this state arrive after dozens of attempts — and every one of those costs mapping that exists nowhere else.
A device that gets worse each time you try it
Do what you did — stop. That observation is real rather than an impression: a controller struggling to maintain its mapping of logical positions to physical memory can corrupt it further on each power-up while attempting maintenance, and that mapping exists nowhere else, so every attempt makes reconstruction harder. Read a raw volume as encouraging, too: it reports only that a small descriptor couldn't be interpreted, and your files sit well away from it.
Stopping was right — call Cambridge Data Recovery on 01223 655015; deterioration accepted as a limit on attempts, read in one controlled session, memory addressed past the failing 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.