SD cards and SSDs have one major thing in common: both run on NAND flash memory. Despite that, they’re still drastically different in many ways, and that includes failures.
When there’s an issue with an SD card, the warning signs may differ from those of an SSD or an HDD. Here’s what you need to look out for, and why recovering an SD card is so weird when compared to an SSD.
SD cards aren’t tiny SSDs
And the controller is a whole other story.
Because they both use NAND flash memory, it’s easy to assume that SD cards are just some kind of tiny-form-factor amalgamation of an SSD. But no—they’re an entirely different product, for better or worse.
The controller makes all the difference. NAND is just the storage; the controller is the part that decides how data gets written, where it really lives, and what happens when things go south.
An SSD controller is pretty robust, especially when you compare it to an SD card. It’s meant to be both consistent and fast, and this is true for both the fastest SSDs and older PCIe Gen 3 models. It has way more room for error correction, improved wear management, and some extra features that help your SSD hang in there during power cuts and other such events. This doesn’t exactly mean that the SSD is super easy to recover lost data from, but it does mean it tends to be more predictable.
SD cards, on the other hand, have different priorities (or, well, their manufacturers do). They’re tiny and thus prioritize maintaining that small form factor, and they need to be fairly affordable. Although, in this RAM-pocalypse era we’re all living in right now, no storage solutions are truly cheap anymore, but I digress.
Since SD cards have to focus on the form factor, the controller can behave differently, and two cards that look similar on the outside can behave completely differently once they start failing.
This is also why SD cards tend to feel more fragile—because they are. They’re constantly being yanked from one device to the next, so their environment is far from similar to the stable life of an internal SSD.
How SD cards usually fail
They aren’t considered the best available option for backups.
Most SD card failures aren’t obvious at a glance, but since a lot of SD cards aren’t used frequently, you may miss the first signs and only figure out that the card is dead when it actually happens.
The most common failure mode is logical corruption. When this happens, the card still shows up, but the filesystem is damaged. You might get errors from your PC or another device, saying that the card needs to be formatted. You might also find missing folders or weirdly named files.
The second common mode is unstable reads, where the card works just long enough to give you hope. Transfers crawl, files fail mid-copy, the card disconnects and reconnects, or you get repeating I/O errors across different devices.
Lastly, your SD card might become read-only, often as a result of the controller detecting too many errors. This might be your final alarm bell to get your files off the drive as soon as possible before the SD kicks the bucket.
Now, for the point of no return: The SD card may not show up anywhere, or it may show up as 0 bytes, or it may disappear when you try to interact with it in your OS.
Why SD recovery is such a weird process
It’s still data recovery, but it’s nothing like what you do with an SSD.
Let’s say your SD card is having a bad time, some files seem to be missing, and you want to try to recover them. Most people approach the process the same way they would with an SSD or any other drive: Run a repair tool, try an “undelete” tool, and hope for the best.
The problem is that SD failures often start as filesystem damage, so the data may still be there, but the map that points to it does not. They’re essentially lost in a (tiny) void.
That’s why SD recovery differs from what you’d do with an SSD, and it’s essentially split into two paths: You either rebuild enough of the filesystem to recover files with their names and folders intact, or you carve files out of raw data. Carving can save your photos, but it often dumps them into a giant pile with generic filenames and no folder structure.
SSDs are weird in their own way. Recovering deleted files can get tricky because modern SSDs are so efficient at cleaning up freed blocks in the background, so the data you might want could be gone even if the drive is at 100% health (at least in theory). With SD cards, the data can stick around longer, but corruption and unstable reads can make the whole recovery process feel unstable and unpredictable from one attempt to the next.
If your SD card is encrypted, the whole thing can potentially get even worse; the same is true if the controller stops presenting a usable device. At that point, it’s important to act fast.
Clone first, then triage
Worry about your data first, everything else second.
Once you start noticing problems with the SD card, it’s better to act fast. Fixing the card should be the least of all problems. Focus on getting whatever readable data can still be recovered from the device. Repair attempts are wasting precious time and resources when, unfortunately, recovering your data should be the top priority.
Don’t try to repair or format the card, and don’t necessarily try to interact with the files once you spot the first signs of trouble. Instead, make a full image of the drive first. That image is basically just a byte-for-byte copy of the entire card saved as a single file on another drive, and it gives you something you can safely experiment on without hammering the SD card itself.
On Windows, the easiest way is to use an imaging tool that can read removable media into an image file. You pick the SD card as the source, choose where to save the image, and hit Read. The big gotcha is space. If you’re imaging a 128GB card, you need about 128GB of free space even if it only holds a few photos, because the image captures the whole device, not just the visible files.
If the card is unstable, don’t keep on trying and trying file copies. The whole point of imaging is to get as much as possible in one controlled pass, then try to recover whatever you can on the image, which lives on a stable drive now. And if your card keeps disconnecting and you can’t copy the files over, it’s time to consider professional recovery services.
Stephan is the sports journalist for the Maple Grove Report.
