Data Recovery Case File · Cameras, Drones & Cards · Nothing Was Done to It
Card That Failed While Nobody Touched It
Her enquiry ruled out the usual suspects before it began. A microSD card that "suddenly became invisible to all my devices despite me not removing it from my phone — the phone was just lying on my desk after an update when a message appeared that the card was removed. I have tried restarting the phone, removing the card and putting it in again, and putting it into a card reader to see if my PC will recognise it, but no luck. Under Disk Management it appears only as unallocated RAW data." No unsafe removal, no drop, no water — the phone was on a desk. Two details do the work here: the failure followed an update, and the card now presents as unallocated rather than not at all.
| Media | microSD card in a mobile handset — reported as removed while the device sat idle following a system update; now presenting to a computer as unallocated with no readable filesystem |
| Reported situation | No physical handling at the time of failure · card-removed notification appearing after a system update · handset restart, reseating and card-reader testing all attempted · card enumerating on a computer but showing no partition |
| Fault class | Partition or filesystem structures lost over functioning media — card enumerating and reporting capacity; contents intact behind missing structures |
| Equipment used | Write-blocked imaging (DeepSpar USB Stabilizer 10Gb) · partition and filesystem structures located and reconstructed on the image · format-aware carving for anything beyond structural repair · contents verified and delivered |
The decode: what unallocated means, and why an update is a suspect
Why "unallocated" is the good news: the most important thing in her message. For a computer to describe a card as unallocated, the card must have received power, its controller must have responded, it must have identified itself and reported its capacity. All of that succeeding eliminates the serious hardware faults in one observation — a dead controller, a failed connection, physical damage. What "unallocated" then means is narrow and specific: the computer looked for the structures describing how the space is divided and used, and found none it could read. So the card is healthy and its bookkeeping is missing. Her photographs are physically present in space the computer currently believes is empty.
Why the update is a reasonable suspect: a system update is one of the busiest things a phone ever does — it writes extensively, remounts storage, and often reorganises where things live. If the card was mounted and being written to when something went wrong during that process, the structures describing it can be left inconsistent or truncated, and the phone's response is to report the card as removed because it can no longer make sense of it. That is consistent with everything she describes, and it means the loss was caused by an interrupted write rather than by anything she did.
Why her testing was correct and has finished: she restarted the phone, reseated the card and tried a separate reader on a computer. That is a complete and sensible elimination — it rules out the phone, the slot, the contacts and the operating system, and it produced the useful finding that a computer sees the card and reports its size. There is nothing further to test, and each additional insertion achieves nothing.
The button that would end it: a card showing as unallocated in Disk Management sits one right-click away from New Simple Volume, and Windows may separately offer to format it. Either writes a fresh, empty structure over exactly the region a reconstruction rebuilds from. The photographs would usually still be physically present afterwards, but they would come back stripped of folders, filenames and dates. Nothing should be created, initialised, formatted or repaired on that card.
Why the outlook is good: structures lost over healthy media is the most recoverable category in this archive. Filesystems keep backup copies of their key structures in known locations, so the originals can frequently be located on an image and rebuilt — returning the folder tree and filenames rather than an unnamed carve.
On the bench
The card was imaged write-blocked behind the DeepSpar USB Stabilizer 10Gb, so that everything afterwards happened against a copy and no prompt from any host could reach the original. On the image the partition and filesystem structures were located — including the backup copies filesystems maintain for exactly this event — and reconstructed until the volume mounted from the copy with its folder tree, filenames and dates intact. Format-aware carving swept alongside for anything beyond structural repair. Her photographs and video were validated by rendering and playback rather than counted, and delivered on fresh media with the original card returned untouched.
The outcome
The lost structures rebuilt from a write-blocked image and the contents verified and delivered. Free assessment, one fixed written figure including VAT, no recovery, no fee. The decode, for anyone whose card shows as unallocated: that description is good news, because reporting a capacity means the card powered, responded and identified itself — the hardware is fine and only the structures describing the space are missing, with your files physically present behind them; a failure during or after a system update points at an interrupted write rather than anything you did; testing on a separate reader is a complete elimination and there is nothing more to try; and the offer to create a new volume or format it is the one thing on your screen that turns a full recovery into a carve.
Card showing as unallocated or RAW
Don't right-click it. A card described as unallocated has powered up, responded and reported its capacity, so the hardware is working — what's missing is only the structures describing how the space is used, with your files sitting physically intact behind them. That's the most recoverable situation there is. But the fix your computer offers is the thing that costs you: creating a new volume, initialising, or formatting all write a fresh empty structure over exactly what a reconstruction rebuilds from, and while the photographs would usually survive, they'd come back with no folders, no filenames and no dates. If the failure happened around a system update, that's a likely cause rather than anything you did — updates write heavily and remount storage. Stop reseating the card, don't run recovery software, and don't let anything repair it.
Don't create a new volume — call Glasgow Data Recovery on 0141 404 0294; imaged write-blocked, structures located from their backup copies and rebuilt, folders and dates returned intact.
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.