File System Errors on CF Card

[Damon Meledones]

I have a RED 8GB CF card that suffered some problems when it was mounted for download. It appears that the FAT of the card downloaded before it was partily written over this cards FAT. Another possibility is that the camera did something strange when formatting or shooting the card. In any event, the first take on the card is not readable. A file system check reports cross-linked and too many clusters allocated for the R3D file, as well as the magazine and log files, and orphaned clusters on the volume. I have taken the card out of circulation and created a disk image of it, running fsck in repair mode on a copy of the image results in the clip being truncated to the first 10 or so seconds. How should I proceed in an attempt to recover this clip?

 

[Damon Meledones]

After digging further into the disk image, it appears that the problem happened while the card was mounting. All of the proxy files the camera created refer to the correct directory structure (e.g. "A032_blabla.RDM/A032_C001_blabla.RDC/A032_C001_blabla_001.R3D"), while the actual filesystem is partially overwritten with the directory structure of the previous card (e.g. "A031_blabla.RDM/A032_C001_blabla.RDC/A032_C001_blabla_001.R3D").

 

[Damon Meledones]

I've tried File Scavenger with no luck, and I'd like to give Foremost a shot next. Does anyone have a configuration file for recovering R3Ds with Foremost? Or some insight as to the best head and tail patterns to use? Failing Foremost, I think my next move is to start extracting raw chunks of varying length from the disk image, starting at the beginning of my clip and hunting for the end of usable data.