Data Recovery Case File · Cameras, Drones & Cards · What It Did, and What Now
Having Already Run the Repair Tool
Her enquiry reported an action this archive routinely warns against, taken before she had read any of it. A SanDisk microSD card: "we are unable to access it — we have tried mounting it on several machines and have tried First Aid via Disk Utility. However, the card continues to show as 'initializing'. Is this something you might be able to help with?" Email contact requested and honoured. The honest answer has two halves and the first is reassuring: on a device stuck at initialising, First Aid almost certainly did nothing at all — because it cannot operate on a volume it cannot reach. The warning is real, but it applies to a different situation from hers, and she has probably not lost anything by trying.
| Media | SanDisk microSD card — not accessible on multiple machines; presenting as perpetually initialising; disk repair utility already attempted |
| Reported situation | Card inaccessible across several computers · presenting as initialising without completing · First Aid run through Disk Utility · no result obtained · email contact preferred |
| Fault class | Controller responding partially without completing identification — no mountable volume presented; repair utilities unable to act; memory typically intact |
| Equipment used | No further mounting attempts · enumeration attempted write-blocked under strict timeouts (DeepSpar USB Stabilizer 10Gb) · chip-level read past the failed controller (PC-3000 Flash, Rusolut VNR) · contents reconstructed and validated |
The decode: what she has, and what the tool could and could not do
What "stuck at initialising" describes: a device that is responding enough to be noticed and never finishing. The system sees something at the port, begins the process of bringing it into service — reading its identification, asking for its capacity, looking for a volume — and the card stops answering partway. The status never advances because the next step never completes. That is the signature of a partially functional controller rather than a dead card or a damaged filesystem.
Why First Aid could not have done damage here: the reassuring part. Disk repair utilities work on volumes. They read a filesystem's structures, find inconsistencies, and write corrections. All of that requires a volume the system can address — and hers never presented one. Faced with a device stuck at initialising, the utility has nothing to read and nothing to write to, so it fails at the outset. It is very unlikely to have written a single byte to the card.
Where the warning genuinely applies: worth stating so the distinction is clear rather than sounding like a reprieve for everything. When a volume does mount but is damaged, First Aid is a real risk: it repairs by writing decisions — choosing between records that disagree, discarding entries it cannot reconcile, and moving orphaned data into recovery folders with generic names. On a badly damaged volume that converts something reconstructable into permanent structural loss and strips filenames along the way. So the rule stands; her card simply never got far enough for it to bite.
What the fault actually means for her data: good things. A controller that cannot complete its introduction has failed as a doorway, not as a store. The memory die holding her files sits behind it, normally entirely unaffected, and is read directly through the card's internal pads — bypassing the controller rather than trying to revive it.
What to stop now: mounting attempts. Several machines have already established the position, each attempt powers a failing controller, and the one remaining risk is that some machine eventually offers to erase or initialise the card and somebody accepts it out of frustration. That is the offer to refuse.
On the bench
No further mounting was attempted, since several machines had already exhausted what that establishes. Enumeration was attempted write-blocked behind the DeepSpar USB Stabilizer 10Gb under strict timeouts, which gathers information from a device that stops answering without hanging a host or offering to repair anything. With the controller confirmed unable to complete identification, the memory was read at chip level on the PC-3000 Flash with the pinout confirmed against the Rusolut VNR database, then descrambled, error-corrected and rebuilt through its translation layer until the filesystem stood up. The contents were validated before delivery.
The outcome
The controller confirmed as partially responsive, the memory read at chip level past it, and the contents reconstructed and validated. Free assessment, one fixed written figure including VAT, 50% of parts and labour upfront with the balance only on successful recovery. The decode, for anyone who has already run a repair tool: on a device stuck at initialising it almost certainly did nothing, because repair utilities operate on volumes and yours never presented one — so there was nothing for it to read or write; the warning applies to a mounted but damaged volume, where repairing means writing decisions and discarding records, which is where real damage happens; a card that never completes identification has a controller fault rather than a filesystem one; and the memory behind it is normally intact. Stop mounting it, and refuse any offer to erase.
Already ran a disk repair tool on a failing device
Don't panic — and check which situation you were in. Repair utilities work on volumes: they read a filesystem, find inconsistencies and write corrections. If your device never mounted a volume at all — if it sat at "initialising", or nothing ever appeared — the tool had nothing to read and nothing to write to, and almost certainly did no damage. Where the warning genuinely matters is when a damaged volume does mount, because then the repair proceeds: it chooses between records that disagree, discards what it can't reconcile, and dumps orphaned files into folders with generic names, which can turn a rebuildable volume into permanent loss. Either way, stop now. Don't keep trying more machines, and refuse any offer to erase or initialise — that's the one remaining action that would genuinely cost you.
It probably did nothing — call Glasgow Data Recovery on 0141 404 0294; enumeration attempted under strict timeouts, memory read at chip level past the controller, contents validated.
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.