Data Recovery Case File · Trust, Practice & Honest Limits · A Backup You Never Restored

Disk Image That Will Not Mount: An Untested Backup

Her enquiry described a precaution that turned out not to be one. After a previous crash had been repaired, she took care to protect herself: "I managed to make a disk image on my external hard drive the second time and thought I saved my data. I haven't managed to use this disk image since, and I always have this message when I try to mount it: 'No mountable file systems'." She did the right thing in principle and the outcome exposes the flaw in how most people back up. A backup that has never been restored from is not a backup — it is a hypothesis. The good news is that the message she is seeing is far less final than it sounds, and an image that will not mount is frequently still readable.

The decode: what the message means, and why it is not fatal

What a disk image actually is: a single file containing an entire filesystem — every folder, file and structure of the original volume, wrapped in a container. When she double-clicks it, the operating system reads the container, finds the filesystem inside, and presents it as though it were a disk. Two separate things therefore have to be intact: the container and the filesystem within it.

What "no mountable file systems" is reporting: that the file was found and opened, and that nothing inside it could be interpreted as a mountable volume. It is a precise statement rather than a general failure, and it has three usual causes. The image may be incomplete — creation was interrupted, or ran out of space on the destination, leaving a file that exists at a plausible size with a truncated filesystem inside. The container may be damaged, so the header describing what is inside cannot be read. Or the image may have been written to a drive that was itself developing problems, in which case parts of the file are unreadable. In her case the first is the most likely: an image made once, under pressure, and never verified.

Why it is usually recoverable: the reassuring part. Mounting is the operating system's convenience, and it is all or nothing — it either presents a clean volume or refuses. A recovery bench does not need to mount anything. The image is a file containing a filesystem, so that filesystem can be examined directly, its structures reconstructed, and its contents extracted, even when the container will not open normally and even when the image is truncated. A partial image usually yields the substantial majority of what it contains. So the message she has been staring at for months is an obstacle rather than a verdict.

The lesson, said plainly: because it is the reason this case is in the archive. She did more than most people do — she recognised a risk and made a copy. What she did not do, and almost nobody does, is open it afterwards. A backup is not verified by existing; it is verified by being restored from. Once, at least partially, at the time it is made. Ten minutes of opening a few files out of an image is the difference between a safety net and a comforting file that turns out to be empty at the worst possible moment.

One thing worth checking alongside: the external drive the image lives on. If that drive was itself struggling when the image was written, both the image and anything else on it deserve attention — and it should be treated as suspect rather than trusted with the recovered copy afterwards.

On the bench

The external drive holding the image was imaged write-blocked before the image file itself was touched — because a container that will not mount deserves to be examined on a copy, and because the host drive's own condition was unknown. The image container was then examined directly rather than mounted: its header inspected, its true extent established against its declared size, and the filesystem inside located and reconstructed regardless of whether the operating system would present it. Contents were extracted from that reconstruction, verified by opening, and delivered on fresh media rather than back onto the drive they came from.

The outcome

The image examined directly, its contained filesystem reconstructed and the contents verified and delivered. 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, for anyone with a backup image that will not open: the message means the file was read and nothing inside it could be interpreted as a volume — usually because creation was interrupted or ran short of space, leaving a plausible-looking file with a truncated filesystem inside; that is an obstacle rather than a verdict, because a bench does not need to mount anything and can reconstruct the contained filesystem directly, even from a partial image. And the lesson worth taking: open your backups when you make them, because a backup you have never restored from is only a hypothesis.

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.