Data Recovery Case File · Mac & Apple Systems · Files or the Thing That Held Them
A Photo Library Is a Database and Its Pictures, and They Come Back Differently
His enquiry asks the question that decides what a successful outcome looks like. A drive visible in the system's disk utility but refusing to mount, holding a photo application's library, and he wants to know whether he would get "the exact intact photo app reinstated as was, or does the data extraction only mean the retrieval of individual images?" Those are two different deliverables, and asking before committing is exactly the right sequence.
| Media | Externally connected hard drive in Apple format — present in the system disk utility, not mounting; holding a photo application library comprising originals and its own catalogue |
| Reported situation | External drive formatted for the platform · visible in the system disk utility · not mounting · holding a photo application library · images organised within albums and lists maintained by the application · owner seeking clarity on whether the library returns intact or as loose images |
| Fault class | Volume not mounting with device present — structures unreadable rather than device failed; library integrity dependent on catalogue as well as originals |
| Equipment used | Deliverable clarified as library structure or extracted originals before work began · imaged write-blocked at the block level before any interpretation · filesystem structures interpreted with their duplicate copies · library package recovered as a whole where its internal catalogue survived · originals carved separately where it did not |
The decode: what a library actually is, and which outcome is achievable
What the application stores: two things that depend on each other. The original image files, and a catalogue recording albums, dates, edits, faces and the order of everything — the pictures are the content and the catalogue is the arrangement.
Why that matters for his question: extracting images returns the content without the arrangement. He would have every photograph and no albums, no edit history and no organisation — which is a real loss for a library built over years, and it is what he is trying to avoid.
What determines whether the library comes back whole: whether the catalogue is recovered intact alongside the originals. It is a set of files within the library package like any other, and it recovers or fails to recover on the same terms as the images.
Why the odds are reasonable here: the drive is visible in the disk utility. That means the device is present, powered and enumerating — it is the volume structures that cannot be read, not the drive that has failed, which is among the more recoverable positions.
Why a volume-level recovery favours the library specifically: where the filesystem can be reconstructed, the library package is recovered as a directory tree with its internal arrangement preserved. Copied to a new drive, it opens as it did before — which is precisely the outcome he described wanting.
What the fallback produces if the structures cannot be rebuilt: carving finds images by their own signatures, without reference to any folder. That returns pictures with generic names and no arrangement — the outcome he is hoping to avoid, and worth being clear is possible.
Why the two are not alternatives to choose between: the volume reconstruction is attempted first because it yields more. Carving is what happens where that fails, so the answer to his question is decided by the drive rather than by a decision he has to make.
What is worth knowing about the catalogue's fragility: it is a database, and a database damaged in the middle is less forgiving than an image with a damaged region. A partly-recovered catalogue may not open at all, whereas a partly-recovered photograph is still a photograph.
Why the honest position is therefore a ranked one: best case the library opens as before; middle case the originals return organised by folder but the catalogue does not open; worst case loose images. All three are useful outcomes and they are not equally good.
What must not happen meanwhile: no repair utility run against the volume, and no accepting an offer to fix or reformat it. The structures that would restore the library whole are the ones a repair rewrites.
On the bench
The deliverable was clarified as library structure or extracted originals before work began — a photo library comprising original image files together with a catalogue recording albums, dates, edits and ordering, so extraction of images returns content without arrangement, whereas volume-level reconstruction recovers the library package as a directory tree with its internal arrangement intact. Filesystem structures were interpreted with their duplicate copies, and originals carved separately where reconstruction was not achievable.
The outcome
The deliverable clarified before work began, the drive imaged at the block level, and the library recovered as a package where its catalogue survived. 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: your library is a catalogue plus its pictures. Reconstructing the volume returns both together and the library opens as before; carving returns the images alone, with no albums or edit history.
Asking what form your data will come back in
Ask before committing, because for a photo library the two possible answers differ a great deal. A library is original images plus a catalogue recording albums, dates, edits and ordering — so extraction returns the pictures with none of the arrangement, while reconstructing the volume returns the whole package, which opens as it did before. Which you get is decided by the drive rather than by a choice you make, since volume reconstruction is attempted first because it yields more. Note that the catalogue is a database: partly recovered, it may not open at all, whereas a partly recovered photograph is still a photograph.
Ask before committing — call Easy Data Recovery on 028 9002 0144; deliverable clarified before work begins, imaged at the block level, library recovered as a package where its catalogue survives.
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.