Her wedding photos are trapped behind a card that is misreporting itself. Her camera "went off mid taking photos", and since then she cannot access files — the error "Card1 cannot be accessed" shows, and though it is a 32GB card, recovery tools see it "coming up as 2gb with no files accessible." She has been advised to ask about "chip off recovery." A card that reports the wrong capacity has a controller fault, not lost data — the controller is misrepresenting the card, which is exactly the situation where chip-off may be the answer, though it is the last resort after gentler routes are tried.
| Media | 32GB SD card reporting as 2GB with no accessible files after the camera lost power mid-shoot — wedding photos the target; chip-off recovery raised as a possibility. |
| Reported situation | Camera powered off mid-capture · card inaccessible since, showing a "cannot be accessed" error · recovery tools seeing it as 2GB rather than 32GB · no files visible to those tools · wedding photos at stake · chip-off recovery suggested to the owner. |
| Fault class | SD controller fault — the card misreporting its capacity and refusing access, the memory and photos intact behind it; recoverable via controller access or, as a last resort, chip-off reading of the NAND. |
| Equipment used | Card imaged under a hardware write-blocker where it part-responds, before further attempts · the controller addressed on PC-3000 Flash to correct the capacity misreporting and read the true memory behind it · where the controller cannot be revived, chip-off reading of the NAND after removing it from the card, the raw dump reconstructed in specialist flash software · recovered photographs validated by rendering. |
The wrong capacity is the key symptom, and it points at the controller. A 32GB card reporting as 2GB is not a card that has lost most of its data — it is a card whose controller has failed in a way that makes it misrepresent itself. The controller manages how the card presents to devices, and when it faults, it can report a wrong size, refuse access, or show no files, while the memory holding the photos remains intact behind it. The 2GB figure is the controller misbehaving, not a measure of what survives.
The camera cutting out mid-write is a plausible trigger. Losing power while the card was being written can corrupt the controller's state or the structures it relies on, leaving it in the faulty condition she now sees. That the fault began exactly when the camera went off mid-capture fits this — the interrupted operation left the controller unable to present the card correctly. It is a controller fault brought on by the power loss, not damage to the wedding photos themselves.
Her consumer tools failed because they depend on the faulty controller. Disk Drill and PhotoRec talk to the card through its controller — and if the controller is misreporting a 2GB card with no files, that is all those tools can see, because they cannot get past the controller to the real memory. Their failure does not mean the photos are gone; it means the fault is below the level consumer software can reach, which is why laboratory methods are needed.
Chip-off is a real answer here, but it is the last resort, and the order matters. The advice she received is sound in that chip-off suits exactly this kind of controller fault — but it is not the first step. Gentler routes are tried first: addressing the controller directly on professional equipment to correct the misreporting and read the true memory through it, which preserves the card and is less invasive. Only where the controller genuinely cannot be revived does chip-off follow — physically removing the memory chip to read it directly, bypassing the failed controller entirely.
The honest prognosis is good, given the fault. A controller fault with intact memory — which the wrong-capacity symptom strongly indicates — typically returns the photos, whether through controller access or chip-off. The recovered wedding photos are validated by rendering before return, and the recoverable extent is confirmed at assessment before any charge. The one honest caveat is that if the memory itself was damaged by the power event, some images may not survive — established from the read, not assumed.
The card was imaged under a hardware write-blocker where it part-responded, before further attempts. The controller was addressed on PC-3000 Flash to correct the capacity misreporting and read the true memory behind it, and where the controller could not be revived, the NAND was read by chip-off after removal, the raw dump reconstructed in specialist flash software. The recovered photographs were validated by rendering.
Controller fault addressed to correct the misreporting, or the memory read by chip-off where it could not be, and the wedding photos reconstructed and validated. The diagnostic costs nothing and completes within two working days of arrival, and the quote is one fixed written figure with VAT already in it; if the data can't be brought back, no charge is made. The decode: a 32GB card showing as 2GB is a controller misrepresenting the card, not lost photos. Chip-off is the right tool if needed — but gentler controller access comes first, and either way your wedding photos are intact behind the fault.
Stop running consumer recovery tools on it — a card showing the wrong capacity has a controller fault those tools can't see past, and repeated attempts risk the card. Don't format it. The wrong size means the controller is misrepresenting the card, with your photos intact behind it, recoverable by addressing the controller or, as a last resort, chip-off reading of the memory. Chip-off is real but comes after gentler routes, so have the card assessed rather than reaching for it first.
Our case files are written up from genuine enquiries our lab has handled for customers across Swansea and South Wales, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery approach our engineers apply to that fault, using the equipment listed.
Free diagnostic, fixed quote, no fix no fee — start now or call the freephone.