Data Recovery Case File · Mac & Apple Systems · A Clear Scope Helps
An Operating System and a Home Folder Occupy Different Parts of the Same Drive
His enquiry states its objective more precisely than most, and the precision is useful. A drive removed from a machine whose operating system failed, physically intact, where "files appear to be working but the operating system partition seems to be corrupt" — and he wants documents and photographs, explicitly not system files or applications. That scope makes this a smaller job than it sounds.
| Media | Hard drive removed from a laptop following operating system failure — drive physically intact; system region reported corrupt with user content apparently readable |
| Reported situation | Laptop operating system failing · drive removed from the machine · drive physically intact and in good condition · files appearing readable on inspection · operating system region reported as corrupt · personal documents and photographs required · system files and applications not required |
| Fault class | System region damage with user data intact — content unaffected by operating system corruption; declared scope limiting extraction to the user hierarchy |
| Equipment used | Declared scope used to limit extraction to the user hierarchy · drive imaged write-blocked at the block level before any interpretation · native volume format interpreted from the image · user home hierarchy extracted with structure and permissions normalised · application-managed libraries identified and delivered whole |
The decode: why the two are separable, and what still needs care
How a system drive is arranged: the operating system, applications and user content all live on it, in distinct areas of the directory. System files sit in their own hierarchy and personal content sits in a user folder, and the two rarely interfere.
Why an operating system can fail without touching personal files: the damage is usually to system components, caches or the records the system needs to start. A machine that will not boot is frequently one whose start-up chain is broken while everything else is intact.
Why his observation supports that: files appear readable on inspection. That is direct evidence rather than an assumption, and it fits a fault confined to the system region.
Why the drive being physically intact matters: this is a logical job rather than a mechanical one. No opening, no donor parts, no filtered air — which places it at the straightforward end of the range.
Why the declared scope genuinely reduces the work: excluding system files and applications removes the overwhelming majority of the file count. A system installation is hundreds of thousands of small files, and none of them is wanted.
What still needs care despite the simple scope: content held inside application-managed libraries. Photographs, mail and messages frequently live in container files within the user folder rather than as loose documents, and those must come across whole.
Why that is worth specifying rather than assuming: a naive extraction of documents and pictures can miss a photo library entirely, because it does not look like a folder of photographs. Asking for application libraries to be delivered intact avoids exactly that.
What else should be preserved: the folder structure and the timestamps. A user folder is organised by its arrangement, and content delivered flat is complete and unusable.
Why permissions deserve a mention: files from one machine's user account can arrive on another machine unreadable without adjustment. Normalising ownership at delivery avoids a frustration that looks like a failed recovery.
Why the drive should still be imaged rather than copied from directly: a drive that hosted a failing system may have unreadable regions that caused the failure. An image secures whatever reads before anything is selected, and the scope is applied to the copy.
On the bench
The declared scope was used to limit extraction to the user hierarchy — operating system, applications and personal content occupying distinct areas of the same directory, so system-region damage frequently leaves user content intact, which the owner's observation of readable files supports. Application-managed libraries hold photographs, mail and messages in container files within the user folder rather than as loose documents, and were identified and delivered whole, with structure, timestamps and permissions normalised.
The outcome
The declared scope applied to a block-level image, the native volume format interpreted from it, and application libraries delivered whole. 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: an operating system and your home folder sit in different parts of the same drive. Excluding system files removes most of the file count — but ask for application libraries to be delivered whole, since a photo library does not look like a folder of photographs.
Asking for personal files only
Say so up front — it removes the overwhelming majority of the file count, since a system installation is hundreds of thousands of small files nobody wants. But add three specifics. Ask for application-managed libraries to be delivered whole, because photographs, mail and messages often live in container files that don't look like folders of documents and a naive extraction misses them. Ask for the folder structure and timestamps to be preserved. And ask for permissions to be normalised, since files from one machine's account can arrive unreadable on another.
Say so before the work — call Manchester Data Recovery on 0161 871 0788; scope applied to a block-level image, user hierarchy extracted with structure preserved, application libraries delivered whole.
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.