On 9/18/20 10:44 PM, David C. Rankin wrote:
All,
I have a trail-cam with a 16G card that I use to monitor the predators coming into the yard so I can keep the cats from getting eaten (long story). This month when I pulled the card, it can't be recognized in any of my readers (Linux or the kids Windows boxes) It is seen and the full 16G is recognized, but blkid reports no filesystem on it. No clue what happened, lightning, low-battery, who knows.
But now that leaves me with the problem of how best to try and recover what I can. Do I just image all 16G with dd_rescue and then use a scanner that will recognize the jpeg headers and try a recovery that way. What tool?
Instead of dd_rescue, can I just open the device as a raw file and read the number of bytes reported? If I'm just going to scan through it, then I don't see why a dd_rescue write to an image would help. (other than it's multiple attempts to read from each memory location) However, I'm not worried if I miss an image or two because one of the header bytes wasn't read or I get a few off colored pixels.
Anybody run into a similar issue and find a decent way to recover what is recoverable?
Update: I have run testdisk and photorec against the card and absolutely nothing is found. I made two-passes with photorec, the first looking for all file types, the second looking only for jpg files. Nothing was found at all. So I guess this card is just toast. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org