Data Recovery Case File · Cameras, Drones & Cards · Working Off the Card
SD Card Failed While Editing a Video
His enquiry pinned the failure to a specific activity, and the activity is the story. Running social media for a gym: "I have an SD card that has just stopped working whilst editing a video. Every time I now plug it in to either the Mac or my camera it says it's not readable by this computer, and says error on the camera. The videos on there are important." Two hosts refusing it settles that the fault is in the card rather than in either machine. But the detail worth extracting is whilst editing — because editing directly from a card is a far more demanding thing to ask of it than anyone realises, and it is the single most common way that working cards become failed ones. This page covers what the two error messages mean, and the working practice that would have prevented it.
| Media | SD card holding video content — failed during an editing session; reported as unreadable by a Mac and as an error by the camera; footage required |
| Reported situation | Card in active use for video editing when it stopped · unreadable on the computer · error reported by the camera · both hosts refusing consistently |
| Fault class | Filesystem or structure damage arising under sustained access — footage intact behind unreadable structures; card-side fault confirmed by two independent hosts |
| Equipment used | Card imaged write-blocked with per-sector timeouts (DeepSpar USB Stabilizer 10Gb) · partition and filesystem reconstruction on the image · format-aware video carving where structures were beyond repair · every clip validated by playback |
The decode: why editing is demanding, and what the two messages mean
Why editing from a card is hard on it: most card use is undemanding — a camera writes a clip and stops, or a computer copies files off in one pass. Editing is neither. Editing software reads continuously and unpredictably: scrubbing a timeline jumps back and forth across a large file, previews are generated, and the card is kept powered and working for the length of a session rather than for the length of a copy. Some software also writes to the card — preview caches, project files, autosaves — which means a card being edited from is often being written to as well. A card with a marginal region or a tiring controller will cope perfectly with everyday use and fail under exactly that sustained load. So the edit did not break a healthy card; it asked more of the card than anything previously had.
What the two messages mean together: both hosts are reporting the same thing in their own dialect. The Mac's not readable by this computer means the card was detected and no volume could be mounted from it — the device is alive and its filing structure will not parse. The camera's error is the same finding from a device with a much simpler vocabulary. Two independent hosts refusing it eliminates cables, readers, drivers and machines in one step. And crucially, both messages describe a structure problem rather than an absence: the footage is still physically on the card.
The danger on each device: different but equally serious. The Mac's message arrives with an Initialise button that opens the erase tool. The camera's response to a card it cannot read is to offer to format it, sometimes as part of preparing the card for use. Either would write fresh empty structures over exactly the ones a reconstruction rebuilds from. The card comes out of both and stays out.
The practice that prevents it: worth saying because he will shoot again next week. Copy footage off the card before editing, and edit from the copy. The card should be a transport medium that gets emptied and verified after every shoot, not a working drive that software runs against for hours. That habit costs a few minutes per job and removes this entire failure mode — and it means a card failing later is an inconvenience rather than a crisis.
On the bench
The card was imaged write-blocked behind the DeepSpar USB Stabilizer 10Gb with per-sector timeouts enforced, so that any region which had begun struggling under the editing load could be worked patiently rather than stalling the pass. On the completed image the partition and filesystem structures were reconstructed until the volume stood up with its folders and filenames; where damage went beyond repair, format-aware carving recovered the clips directly from the card's contents by their internal structure. Every video was validated by playing it end to end rather than by checking its size, ordered by embedded capture time, and delivered on fresh media.
The outcome
The footage recovered by structure reconstruction and validated carving, delivered on fresh media. 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, for anyone whose card failed mid-edit: editing from a card is far more demanding than copying from it — continuous unpredictable reads, sustained power, and often writes as well — so a card that coped with everyday use fails under exactly that load; two hosts refusing it eliminates readers, cables and machines and confirms a card-side fault; both messages describe unreadable structures rather than missing footage; and the habit that removes this failure mode entirely is to copy the card off and edit from the copy.
Card that failed while you were working from it
Take it out of both the computer and the camera and leave it out. Your Mac's unreadable message comes with an Initialise button, and your camera's answer to a card it can't read is to offer a format — either would write empty structures over exactly what a recovery rebuilds from. Neither message means your footage is gone; both mean the filing structure won't parse while the video sits behind it. Understand what happened, because it will happen again otherwise: editing from a card asks far more of it than copying does, with continuous unpredictable reads across large files, sustained power, and often preview caches and project files being written back. A card that handled everyday use for years can fail under one editing session. From now on, copy every shoot off the card first, verify it opens, and edit from the copy — the card is transport, not a working drive.
Don't let either device format it — call Leeds Data Recovery on 0113 322 3083; imaged write-blocked under timeout control, structures rebuilt on the copy, every clip validated by playback.
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.