Data Recovery Case File · Portable Drives · Check the Account First
Downloading Is Usually Copying, So They May Still Be There
His enquiry describes a deliberate migration with an unfortunate result. A recently bought 4TB drive onto which he "moved all of my cloud photos. I have no backup sadly, and this drive is no longer working properly. It flashes a white light when connected, shows up briefly on the computer but is inaccessible, and then disappears." Before anything technical, one question is worth asking — because what he calls moving is very often copying, and the originals may not have gone anywhere.
| Media | 4TB external hard drive of recent purchase — enumerating briefly and disconnecting; photographic library transferred from a cloud service and held as sole copy |
| Reported situation | Drive purchased recently · complete photographic library downloaded from a cloud service onto the drive · no second copy retained · drive indicator flashing on connection · drive appearing briefly and becoming inaccessible · drive then disconnecting · multiple cables and ports tried |
| Fault class | Intermittent enumeration with early-life failure indicated — cloud-side originals to be established before any recovery is commissioned |
| Equipment used | Cloud account contents and deletion state established before any work · enumeration windows characterised under strict timeouts · Atola Insight Forensic error-rate assessment · imaged write-blocked with retries capped · delivery to two destinations |
The decode: the free check, then the fault
What "moved" usually means in practice: a download. Most services export a copy and leave the originals in place, because deleting a library requires a separate, deliberate action that people rarely take immediately after downloading it. So the first question is not about the drive at all — it is whether the photographs are still in the account.
Why that is worth checking before anything else: it costs nothing and it may end the case entirely. Somebody who downloaded and then deleted has a genuine problem; somebody who downloaded and forgot has a full library sitting online, and the difference is one login.
And if they were deleted, check again: most services hold deleted items in a recoverable area for a period — commonly a month or more — before removing them permanently. A deletion made recently is frequently reversible from within the account, which is a far better outcome than any recovery.
Why this pattern is worth naming: bringing a cloud library down onto a local drive is a reasonable thing to do — for cost, for control, or to stop paying for storage. But it converts a copy that somebody else was maintaining into a single copy that nobody is, and the arithmetic changes at the moment the originals are removed rather than at the moment they are downloaded.
Now the fault itself: appearing briefly and disconnecting means the drive enumerates and cannot sustain the connection. The controller is working sometimes — which is not a device that has failed completely, but one that succeeds occasionally, and each appearance is an opportunity of which an unknown number remain.
Why the drive being new matters: early-life failure is disproportionately common, which is why warranties exist. Nothing he did caused it, and a large transfer onto a new drive is simply the first thing to ask it for sustained work.
What must stop: repeated connection. Those brief windows are the resource, and spending them on checking whether today is different is spending them on nothing.
What to do afterwards: if the library comes back, put it in two places. A single drive is not a home for a life's photographs, whatever it cost.
On the bench
Cloud account contents and deletion state were established before any work — a download typically copying rather than moving, leaving originals in place unless separately deleted, and most services retaining deleted items in a recoverable area for a period afterwards. Enumeration windows were characterised under strict timeouts, intermittent appearance indicating a controller succeeding occasionally with a finite number of opportunities remaining. Imaging ran write-blocked with retries capped and delivery to two destinations.
The outcome
The cloud account checked before any technical work, enumeration windows characterised, and the drive imaged with delivery to two destinations. 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: check the account first. Downloading is almost always copying, so unless you deliberately deleted the originals afterwards they are still there — and if you did delete them recently, most services keep deleted items recoverable for a period.
Bringing a cloud library down onto a local drive
Log into the account before commissioning anything — downloading is almost always copying, and unless you separately and deliberately deleted the originals, they haven't gone anywhere. If you did delete them, check again anyway: most services hold deleted items in a recoverable area for a month or more, so a recent deletion is frequently reversible from inside the account. That single login may end the whole problem. Worth understanding the arithmetic too: bringing a library down is reasonable, but it converts a copy somebody else was maintaining into a single copy nobody is — and that happens when you delete the originals, not when you download.
Check the account first — then call Oxford Data Recovery on 01865 593000; enumeration windows characterised under strict timeouts, imaged with retries capped, delivered to two destinations.
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.