Data Recovery Case File · Cameras, Drones & Cards · The Error Names the Fault
Truncated Means the File Is Shorter Than It Claims
Her enquiry quotes an error precisely, and the word in it is a real diagnosis. Photographs taken on a camera "were fine and viewable at first, then they started appearing as 'cannot view this file' on camera. Then when put into laptop it says something like 'damaged or truncated file'." She has tried two platforms and recovery software. Truncated is not a generic word for broken — it means the file's recorded size and its available content no longer agree, and that tells you something specific about the card.
| Media | microSD card used in a digital camera — images initially viewable and subsequently not; host reporting files as damaged or truncated |
| Reported situation | Photographs taken and confirmed viewable on the camera · images subsequently failing to display on the camera · host reporting files as damaged or truncated · behaviour reproduced across two platforms · recovery software attempted · card used with an adapter |
| Fault class | Progressive block-level read failure — file content becoming unreadable after successful writing; directory entries intact |
| Equipment used | Card removed from use and adapter eliminated as a variable · imaged write-blocked under per-block timeouts with marginal blocks re-read across passes · partial-file integrity assessed per image · media validated by rendering |
The decode: what truncation actually reports
What a directory entry holds: among other things, a file's size. When something opens that file, it reads the recorded size, then reads that many bytes of content. If it runs out of readable content before reaching the stated length, the file is truncated — the description and the substance no longer match.
Why that is more informative than "damaged": it locates the problem. The directory entry is intact — the system knows the file exists, what it is called, and how big it should be. What it cannot do is retrieve all of the content that entry describes. So the structures are fine and the data area is not, which is the reverse of most cases in this archive.
Why the progression matters most: the images were viewable and then were not. Nothing wrote to them in between. A file that could be read on Monday and cannot be read on Wednesday, with no intervening activity, means the medium's ability to return that content has degraded — which is a card losing data rather than a card that recorded it badly.
What causes it on flash media: stored charge drifting until the controller's error correction can no longer reconstruct the original values. The correction absorbs a great deal silently, and when it cannot, the block returns nothing usable. That is progressive, and it is continuing.
Why that makes this urgent rather than merely annoying: images that render partly today may not render at all next week, and images currently fine may join them. The card should come out of use now and be captured, with marginal blocks read repeatedly across multiple passes — a block sitting near the correction threshold frequently succeeds on a later attempt.
What the adapter contributes, since she mentioned it: a small card in an adapter adds a set of mechanical contacts to the path, and cheap adapters are a genuine source of intermittent reads. It is worth eliminating as a variable rather than assumed innocent — though it would not explain files degrading over time.
Why her software found the same thing: consumer tools read through the same path and meet the same unreadable blocks. Their agreement confirms the finding rather than indicating a poor choice of tool.
On the bench
The card was removed from use and the adapter eliminated as a variable, additional mechanical contacts being a genuine source of intermittent reads. It was imaged write-blocked under per-block timeouts with marginal blocks re-read across passes — truncation indicating intact directory entries with content unavailable, caused by stored charge drifting beyond what error correction can reconstruct, and blocks near that threshold frequently yielding on a later attempt. Partial-file integrity was assessed per image and media validated by rendering.
The outcome
The adapter eliminated, the card imaged with marginal blocks re-read across passes and integrity assessed per image. Free assessment, one fixed written figure including VAT; where a chip has to be removed, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode: truncated means the file's recorded size and its readable content no longer agree — so the directory entry is intact and the content is not, which is the reverse of most faults here. And images viewable one week and not the next, with nothing written in between, means the card is losing data now.
Files reported as damaged or truncated
Take that word literally and act quickly. A directory entry records a file's size, and anything opening it reads that size and then reads that much content — so truncated means it ran out of readable content before reaching the stated length. The entry is intact; the content is not. What makes it urgent is the progression you describe: images viewable at first and not later, with nothing written in between, means the card's ability to return that content is degrading now rather than having recorded them badly. That continues, so pictures that render partly today may not next week. Get it captured. Worth eliminating any adapter too, since extra contacts cause intermittent reads.
Stop using the card — call Guildford Data Recovery on 01483 901310; adapter eliminated as a variable, imaged under per-block timeouts with marginal blocks re-read across passes, integrity assessed per image.
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.