Data Recovery Case File · Solid State & Flash · Unknown Contents
An Intermittent Connection Makes the Question What Is on the Device, Not Just How to Read It
His enquiry contains an uncertainty most people do not admit to. A portable solid-state drive of several years that is "randomly dropping its connection, though sometimes it stays connected" — and he believes there may be photographs on it, though "with the drive randomly dropping I'm not 100% sure they copied over." That doubt is the substance of the case: a device that disconnects during transfers may hold complete files, partial ones, or neither.
| Media | Portable solid-state drive of several years' service with a modern interface — connection dropping intermittently; content presence not confirmed by the owner |
| Reported situation | Portable solid-state drive in use over several years · connection dropping at random intervals · connection sometimes sustained · photographs believed to have been transferred to the device · completion of that transfer not confirmed · content dating from a known period · discussion requested |
| Fault class | Intermittent enumeration with content presence unestablished — transfers possibly interrupted leaving partial or absent files; controller, connector and thermal causes all open |
| Equipment used | Content presence treated as a question to answer rather than an assumption · device addressed through hardware with imposed timeouts rather than the host stack · imaged write-blocked in a single pass with the connection held stable · file completeness verified by opening rather than by directory listing · findings reported before any recovery scope was agreed |
The decode: three faults that produce dropping, and one question that comes first
What an interrupted transfer leaves behind: less than it appears to. A copy that stops partway generally leaves a file entry with the full name and only part of the content, and a directory listing shows it as present.
Why that makes his doubt the important part: a listing would reassure him falsely. Files can be named, sized and dated correctly while holding nothing usable, and only opening them establishes otherwise.
Why that is the first thing done here: verification precedes recovery. Establishing what is actually present, and whether it opens, determines whether there is a case at all.
The first cause of dropping — the connector. Joints fatigue with use and a partially fractured one conducts intermittently. This is the commonest cause and the most repairable.
The second — thermal behaviour. Compact solid-state drives run warm and throttle or disconnect when they exceed their limit. Dropping after a period of activity rather than at random points this way, and it is worth asking whether the timing correlates with use.
The third — the controller. A controller struggling with its management structures can reset, which appears to the host as a disconnection. This is the least repairable and the most likely to worsen.
Why the age matters: all three accumulate. Several years of insertions, heat cycles and rewrites make each more likely, and they are not mutually exclusive.
Why the device should come out of use now regardless: a controller resetting mid-write is how structures become inconsistent. Continued use risks converting an intermittent fault into a structural one.
What should be checked before anything technical: where else the photographs might be. Content from a known period is frequently still on the source device, or on a phone, or shared elsewhere — and a transfer he cannot confirm may simply not have been needed.
Why saying that first is the right order: if the originals exist, this stops being urgent. Establishing that costs nothing and may end the case favourably.
On the bench
Content presence was treated as a question to answer rather than an assumption — an interrupted copy leaving a file entry with correct name, size and date while holding only part of the content, so a directory listing reassures falsely and only opening establishes completeness. Dropping arises from connector joint fatigue, thermal limits reached during sustained activity, or controller resets appearing to the host as disconnection. Findings were reported before any recovery scope was agreed.
The outcome
Content presence treated as the first question, the device addressed through hardware, and completeness verified by opening rather than by listing. 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 doubt is the case. A transfer interrupted partway leaves a file with the right name and only part of its content — so a listing would tell you they are there, and opening them is what settles it.
A drive that disconnects at random and may not hold what you think
Check the original source first — the phone, camera or machine the photographs came from, or anywhere they were shared — because a transfer you can't confirm may simply not have been needed, and establishing that costs nothing. Then stop using the drive: a controller resetting mid-write is how structures become inconsistent, so continued use can turn an intermittent fault into a structural one. And don't trust a file listing, since an interrupted copy leaves the right name, size and date with only part of the content behind it.
Check the originals first — call Cambridge Data Recovery on 01223 655015; content presence treated as the first question, addressed through hardware, completeness verified by opening rather than by listing.
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.