Data Recovery Case File · Cameras, Drones & Cards · A Single Large Target
Recovering One Large File Is Not the Same Problem as Recovering Many Small Ones
His enquiry is unusually specific about what he needs. A card that "won't let me access it without formatting it, but there is a file on there that I need, so I can't format" — a single file of more than twenty gigabytes. Refusing the format is the right instinct, and the size of what he wants changes the technical problem in a way that is worth understanding.
| Media | Memory card presenting an unformatted prompt on access — holding a single required file exceeding 20GB alongside other content |
| Reported situation | Card not permitting access without formatting · format declined by the owner · a single file exceeding 20GB required · consumer tools considered but limited by file size or licensing · recovery sought |
| Fault class | Filesystem structures unreadable with content retained — single large file requiring contiguous reassembly across a substantial span rather than signature location alone |
| Equipment used | Declined format credited as preservation of the recoverable structures · single-large-file target assessed as a contiguity problem rather than a location problem · card imaged write-blocked before any scanning · allocation records examined to establish the file's extent · content reassembled by continuity and validated by opening in full |
The decode: why refusing helped, and why one big file is harder than many small ones
What the prompt means: the system read the beginning of the card and could not identify a filesystem. Finding nothing it recognises, it offers to create one — which describes a failure to interpret rather than a card that is blank.
Why declining was the whole of the decision available to him: accepting would write a fresh empty structure over exactly the region a reconstruction reads. The content would remain briefly and the map to it would be gone, which converts a recoverable position into a considerably worse one.
Why a single large file is a distinct technical problem: recovering small files works by finding their recognisable openings. A photograph or document is located by its signature and read forward a short distance, and success does not depend on knowing where anything else sits.
Why that approach struggles with something very large: twenty gigabytes spans an enormous portion of the card. Finding the opening establishes where it starts and nothing about where it continues, and a file that size is unlikely to occupy one unbroken run.
What fragmentation does to it: a file written into a card with existing content is placed in whatever gaps are available. Its pieces sit in several separate regions, in an order recorded only by the filesystem — which is the thing that cannot currently be read.
Why that makes the allocation records the priority: the filesystem records which regions belong to which file. Recovering those records recovers the order, and reassembling from them produces a complete file where signature searching alone would produce the first fragment and stop.
Why the prospects are nevertheless decent: allocation records are duplicated in most filesystems. Where the primary set is unreadable, a secondary set frequently survives — and it describes the same arrangement.
Why this explains the limits he encountered: tools that cap file size or restrict output are working on the signature-searching model. Their limits are commercial, and their approach is also the one least suited to a single very large target.
What verification means here specifically: a large file must be opened in full rather than merely recovered. A file of the right size that fails partway is a reassembly that went wrong, and that is only established by playing or opening it through to the end.
What must not happen: nothing further written to the card, and no accepting the format prompt on any device. The prompt will reappear on every machine, and it will look like the way forward each time.
On the bench
The declined format was credited as preservation of the recoverable structures — an unformatted prompt indicating failure to identify a filesystem rather than an empty card, with acceptance writing a fresh structure over the region reconstruction reads. The single-large-file target was assessed as a contiguity problem rather than a location problem: signature searching establishes where a file begins and not where it continues, and a file of that size is unlikely to occupy an unbroken run. Allocation records were examined to establish the file's extent.
The outcome
The declined format credited as preservation, the target assessed as a contiguity problem, and the file reassembled by continuity and validated by opening in full. Free assessment, one fixed written figure including VAT; on cards where content has been deleted or overwritten, the figure is payable upfront. The decode: declining was the right call and it preserved the position. One very large file is a different problem from many small ones — finding its opening says where it starts, not where it continues, so the records describing its extent are what matter.
Needing one large file off a card demanding to be formatted
Keep declining the prompt on every device — it will reappear each time and look like the way forward, and accepting writes a fresh structure over exactly the region a reconstruction reads. Understand why your case is harder than it looks: recovering small files works by finding their recognisable openings and reading forward, but something over twenty gigabytes spans a huge portion of the card and is unlikely to sit in one unbroken run. Finding its start tells you nothing about where it continues, so the filesystem's records of which regions belong to it are what matter. Verify by opening it through to the end.
Keep declining it — call Easy Data Recovery on 028 9002 0144; declined format credited as preservation, allocation records examined to establish the file's extent, reassembled by continuity and validated in full.
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.