Data Recovery Case File · Portable Drives · The Catalogue Needs Its Paths
Photo Catalogue and Images on a Knocked Drive
Her enquiry named both halves of what she needs, which is rarer than it should be and changes how the job is delivered. A WD 4TB portable drive that "took a slight knock when I was travelling. There are many thousands of photos on it and I'm now unable to access them. When the drive is connected to my laptop, my cataloguing software will not even open and causes my laptop to crash. I'm desperate to retrieve the images and the catalogue saved there." Most people ask for their photographs. She has asked for the photographs and the catalogue — and that second request has a technical consequence most recoveries get wrong: a catalogue is only useful if the images are still where it expects them to be. Recovering both and returning them in the wrong shape produces a database pointing at nothing.
| Media | WD 4TB portable hard drive — impact sustained in transit; several thousand photographs and an editing catalogue held; host crashes when the cataloguing software accesses the drive |
| Reported situation | Knock sustained while travelling · drive inaccessible · editing software fails to open and crashes the laptop on connection · both images and catalogue required |
| Fault class | Post-impact damage with reads stalling long enough to hang the host — mechanical assessment required; delivery must preserve folder paths for catalogue integrity |
| Equipment used | No further host connection · laminar flow bench inspection before power · matched donor head service as indicated · PC-3000 Express with Data Extractor prioritised imaging · original folder structure preserved in delivery; catalogue recovered and relinked |
The decode: why it crashes the laptop, and why the paths matter
Why the software crashes the machine: not a software fault. A cataloguing application opening a library immediately reads a great many files — the catalogue database, then previews and originals across the drive. If the drive stalls on reads, the storage driver waits inside the operating system's core and eventually the system halts rather than continuing in an unknown state. So the crash is the drive failing to answer, and the editing software is simply the thing that asks it the most questions fastest. It also means every launch is a sustained, uncontrolled hammering of a drive that has taken an impact — which is the strongest reason to stop connecting it.
What "a slight knock" can do: more than the phrase suggests, and whether the drive was powered at the time is the fact that matters. Travelling with a drive usually means it was switched off and its heads parked clear of the surfaces, which is the survivable case. A knock while running can drive flying heads into the platters. Either way, stalling reads point at the mechanism or the media rather than at the filesystem, and the drive should be assessed before power rather than tested again.
Why the catalogue needs its paths: the part that determines the deliverable. A photo catalogue does not contain the images. It contains references to them — file paths — plus the edits, ratings, keywords and collections she has built up. If the photographs come back in a flat folder, or renamed, or reorganised by file type, the catalogue opens and reports every image as missing, and years of editing work becomes a database pointing into empty space. Relinking thousands of images by hand is possible and miserable. So on a job like this, preserving the original folder structure is not a nicety — it is the difference between recovering her work and recovering her files.
What that means practically: filesystem reconstruction is attempted before content carving, because reconstruction returns the tree with its real names and paths while carving returns images stripped of both. The catalogue file itself is recovered alongside, and delivered with the folder hierarchy identical to the original — so that when she attaches the new drive and opens the catalogue, it finds what it is looking for. Where paths must change, the relink is done deliberately rather than left to her.
On the bench
The drive was not connected to a computer again. It was assessed on instruments where a stalled read hangs nothing, and — given the impact history — inspected under the laminar flow bench before power where the findings indicated mechanical damage, with matched donor parts fitted as required. Imaging ran on the PC-3000 Express under Data Extractor, head-mapped and prioritised. Reconstruction then took the filesystem route deliberately rather than carving, so that the original folder hierarchy, filenames and paths were preserved exactly; the catalogue database was recovered alongside the images, and the delivered set was arranged so that it opens and finds its references intact.
The outcome
The drive assessed and imaged after an impact, with the images and catalogue recovered into their original structure and verified. Free assessment, one fixed written figure including VAT, 50% of parts and labour upfront with the balance only on successful recovery. The decode, for any photographer in this position: editing software crashing your machine is the drive stalling rather than a software fault, and each launch hammers a drive that has already taken a knock — so stop connecting it; and if you want your catalogue as well as your images, say so explicitly, because a catalogue holds references rather than photographs and only works if the folder paths survive. Ask for filesystem reconstruction ahead of carving and for the original hierarchy to be preserved, or you will receive your pictures and lose your editing work.
Editing drive that crashes your computer
Stop connecting it and stop launching the software. A cataloguing application reads hundreds of files the moment it opens, so it finds a stalling drive faster than anything else you own — and the crash is your computer's storage driver giving up on a drive that never answered, not a software problem. Every launch is sustained load on a drive that has taken a knock. Then be specific about the deliverable, because this is where photographers lose work rather than files: your catalogue contains references to image paths plus all your edits, ratings and collections, so if the photographs come back flat, renamed or reorganised, the catalogue opens with everything reported missing. Ask explicitly for filesystem reconstruction rather than carving, for the original folder structure to be preserved exactly, and for the catalogue file itself to be recovered alongside the images.
Ask for the paths to be preserved — call Glasgow Data Recovery on 0141 404 0294; assessed before power, imaged prioritised, folder structure kept intact so your catalogue still finds its references.
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.