Data Recovery Case File · Portable Drives · Two Copies, Neither Independent Enough
Partial Visibility Is a Window, and a Synced Copy Was Never a Second One
His enquiry describes two losses that arrived together. A portable drive dropped some months ago where "initially nothing showed up, now a few files appear" — and, in the same period, the same material disappeared from a cloud account with no explanation given. Both halves matter: a few files appearing means the drive is partially readable right now, and a synced account was never the independent copy it felt like.
| Media | 250GB portable hard drive following an impact some months previously — initially not presenting, currently listing a small proportion of content; corresponding cloud copy also unavailable |
| Reported situation | Portable drive dropped several months previously · initially nothing appearing when connected · a small number of files now appearing · substantial data and images sought · the same material also lost from a cloud account in the same period · no explanation obtained for the cloud loss |
| Fault class | Impact damage with partial readability — a proportion of regions currently returning data; readable window finite and reducing with use |
| Equipment used | Partial file visibility interpreted as partial readability rather than partial content · drive removed from use before capture · imaged write-blocked under strict per-sector timeouts with readable regions taken first · marginal regions revisited across later passes · files validated by opening |
The decode: what partial visibility means, and why the second copy failed
What a few files appearing actually indicates: some of the drive can be read and some cannot. Listing a folder requires reading the structures that describe it, so files appearing means those particular structures are in regions currently returning data — the rest are in regions that are not.
Why that is more hopeful than nothing appearing: it establishes that the drive powers, spins, identifies itself and returns data. Almost the entire chain is working, and the fault is localised read failure rather than a device that cannot be reached at all.
Why the change from nothing to something is worth noting: behaviour that varies between attempts is characteristic of a drive whose readability shifts — heads that position correctly on some attempts and not others. It is not improving; it is varying, and the direction over time on a damaged drive is downward.
Why that makes this urgent rather than encouraging: the readable proportion is what a capture can take today. Every connection spent browsing to see what appears is a connection not spent copying, and each one is another set of positioning attempts by damaged heads.
What the impact did: if the drive was running when dropped, heads flying above the platters were driven into contact. Damaged heads read some regions and not others, which is exactly the pattern he describes — and it explains why the picture changes between attempts.
What is done differently from browsing: the drive is imaged with strict per-sector timeouts so no single difficult region absorbs the remaining time. Readable areas are taken first at full speed while the drive is at its best, and marginal regions revisited across later passes.
Why the cloud loss deserves separate attention: it is a genuinely different failure and it should be pursued with the provider directly. Account histories, deletion logs and version retention are things they hold and can look up, and the material may still exist there in a form that is recoverable by them rather than by anyone else.
Why a synced copy is not a second copy in the sense people intend: synchronisation propagates changes. Deletion on one side is applied to the other by design — so a sync protects against a device failing and not against material being removed, which is why the two losses can coincide without being connected.
What that suggests for afterwards: the copy worth having is one that does not receive changes automatically. An offline drive, or a service that retains versions and deleted items for a defined period, is what covers the case a sync does not.
What must not happen now: no further connection to check what appears today. The drive should come out of use until it can be captured.
On the bench
Partial file visibility was interpreted as partial readability rather than partial content — folder listing requiring the structures describing it to be read, so files appearing indicates those structures occupy regions currently returning data while the remainder do not, which establishes power, rotation, identification and data return as functional and localises the fault to read failure. Variation between attempts is characteristic of damaged heads positioning inconsistently. Imaging ran write-blocked under strict per-sector timeouts with readable regions taken first.
The outcome
Partial visibility read as partial readability, the drive taken out of use, and readable regions captured first under capped timeouts. Free assessment, one fixed written figure including VAT; where a drive has to be opened, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode: a few files appearing means part of the drive reads today, which is a window rather than an improvement. And a synced cloud copy propagates deletions by design — it covers a device failing, not material being removed.
A drive showing some files but not others
Stop connecting it to see what appears — the readable proportion is what a capture can take today, and every browsing attempt is another set of positioning attempts on damaged heads. Files appearing at all is genuinely informative: it means the drive powers, spins, identifies itself and returns data, so the fault is localised read failure rather than an unreachable device. Behaviour that changes between attempts isn't improvement, it's variation, and on a damaged drive the direction over time is downward. Separately, pursue any cloud loss with the provider directly — deletion logs and version retention are theirs to check.
Take it out of use — call Easy Data Recovery on 028 9002 0144; partial visibility read as partial readability, imaged under capped timeouts with readable regions taken first, marginal areas revisited across passes.
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.