Data Recovery Case File · Solid State & Flash · A Move Deletes as It Goes
USB Not Readable After a Crash During Import
Her enquiry gave the sequence precisely, which makes the diagnosis straightforward and produces one immediate free win. About 800 photographs and videos plus documents on a USB drive: "this happened shortly after I was attempting to move my photos on the Mac. I managed to import around 130 pictures before the system crashed, and then I was unable to open the USB on the Mac or any other device including Windows afterwards." She has tried two consumer recovery programs and "nothing was there". She asked about cost and timescale, by email, which was honoured. Two things before anything technical. Those 130 imported pictures are on the Mac and should be checked and secured today — that is 130 fewer to recover. And the word move matters enormously, because if the import was moving rather than copying, the crash caught it partway through deleting as it went.
| Media | USB flash drive holding approximately 800 photographs and videos plus document files — unreadable on Mac and Windows following a system crash during a photo import |
| Reported situation | Import in progress; about 130 images transferred before the machine crashed · drive inaccessible on all devices since · two consumer recovery tools returned nothing · cost and timescale sought by email |
| Fault class | Filesystem structure damage from an interrupted write — contents intact behind unreadable structures; partial source deletion possible if the transfer was a move |
| Equipment used | Write-blocked imaging (DeepSpar USB Stabilizer 10Gb) · partition and filesystem reconstruction on the image · deleted-entry recovery for anything removed by an interrupted move · signature carving with per-file validation · timescale confirmed in writing |
The decode: the crash, the move, and why the software found nothing
Why the crash broke the stick: an import is a sustained read from the drive, and — depending on the application's settings — often a write to it as well, because moving files means deleting each one from the source after it has transferred. Either way, a crash during that operation interrupts the filesystem mid-update: entries partly modified, allocation records disagreeing with one another, and a journal recording changes that never completed. The result is a volume that no computer will mount, on a stick whose contents are otherwise entirely intact. Her stick did not fail; it was interrupted.
Why "move" versus "copy" matters here: if the transfer was copying, every original remains on the stick and nothing has been deleted. If it was moving — which several photo applications do by default, and which the word import often conceals — then roughly 130 files were deleted from the stick as they transferred, one of them was possibly in flight when the crash happened, and the rest are untouched. That does not make the recovery harder; deleted entries are recovered routinely. But it does mean the 130 on the Mac and the deleted originals are the same pictures, so the priority is to confirm the Mac's copies open properly before anything else.
Why the consumer tools found nothing: this is the part that most needs reframing, because "nothing was there" sounds like a verdict and is not one. Both programs work through the operating system's normal view of a device. When the partition and filesystem structures are damaged, the operating system presents no readable volume — so the tools have nothing to scan and report emptiness. That is a statement about the structures, not about the contents. Her photographs are still physically written on the stick, and reconstruction works below the level those programs operate at, on an image where the damaged structures can be rebuilt rather than read around.
Cost and timescale, answered: her two practical questions deserve direct answers. The assessment is free and establishes what the stick will need; one fixed figure follows in writing, including VAT, before any work begins; and on a case like this, where nothing needs opening, nothing is payable unless the data comes back. A timescale is put in writing alongside the figure rather than estimated verbally — and for a stick with intact contents behind damaged structures, it is measured in days rather than weeks.
On the bench
The Mac was checked first, because 130 recovered photographs that cost nothing are worth more than any bench procedure — the imported set located, opened and confirmed complete. The stick was then imaged write-blocked behind the DeepSpar USB Stabilizer 10Gb, and the reconstruction ran on the copy: the partition records and filesystem structures rebuilt until the volume mounted with its folder tree, and deleted-entry recovery run alongside to retrieve the originals that the interrupted move had removed. Signature carving swept for anything beyond structural repair. Every photograph and video was validated by rendering or playback, reconciled against the Mac's imported set to remove duplicates, and delivered on fresh media.
The outcome
The stick's structures rebuilt from a write-blocked image, the interrupted move's deletions recovered, and the whole set reconciled, validated and delivered. Free assessment, one fixed written figure including VAT; on cards and sticks where content has been deleted or overwritten, the figure is payable upfront. The decode, for anyone whose drive died during a transfer: a crash mid-import interrupts the filesystem while it is being updated, which leaves a volume no computer will mount over contents that are perfectly intact; check the destination first, because whatever transferred before the crash is already safe and costs nothing to confirm; understand whether your import was moving or copying, since moving deletes each file from the source as it goes; and treat "the recovery software found nothing" as a description of unreadable structures rather than of missing data, because those tools read through the operating system and reconstruction works below it.
Drive unreadable after a transfer crashed partway
Check the destination first — whatever transferred before the crash is already safe, and confirming it costs nothing. Then find out whether your software was moving or copying, because photo import tools often move by default: if it was moving, those files were deleted from the stick as they went, which is recoverable but worth knowing. Don't reformat the stick, don't accept any offer to repair it, and stop running recovery programs at it. If consumer tools reported nothing, that isn't a verdict — they read through the operating system's view of the device, and when the partition and filesystem structures are damaged there is no volume for them to scan, so they report emptiness while your files sit intact underneath. Reconstruction works below that level, on an image. Ask for a written timescale as well as a figure if you're working to any kind of deadline.
Check what already arrived, then call Leeds Data Recovery on 0113 322 3083; imaged write-blocked, structures rebuilt on the copy, deletions recovered and every file validated.
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.