Can't copy .r3d files

[markparry]

I have a set of dailies from a single RED Drive that was made into a disk image in the Finder. Now when I mount the image, I am able to open or copy some of the .r3d files, but not others. If I try to open the QT proxies it says an I/O error occurred. If I try to copy I get error -36. The files on the mounted image appear to have data within and list the size when I look at Get Info.

Any ideas?

Thanks!

 

[Jeff Kilgroe]

Seems like the image file might be corrupt. Any access to the original media elsewhere? You could always mount the image and try running REDundead on it -- assuming you're on a Mac, but I'm making that assumption since you say you also tried the proxies.

See if you can run some repair or recovery tools on the image. Make a backup of the disk image first.

 

[markparry]

Unfortunately, I don't have the original media. I've tried REDundead, but no luck there. Ran disk utility and the image checked out, so I'm stumped. Probably half of the disk image works fine, the other half, nothing.

 

[markparry]

Though the files that won't read seem to have data, or at least take up disk space.

 

[Deanan]

Though the files that won't read seem to have data, or at least take up disk space.

Do they open in RA?

What sort of disk image was it? compressed or regular?

 

[markparry]

The ones that won't copy don't open in RA. It was a regular disk image. Funny thing is I made a disk image so that the data would be safe. Oh the irony.

 

[Deanan]

The ones that won't copy don't open in RA. It was a regular disk image. Funny thing is I made a disk image so that the data would be safe. Oh the irony.

I don't know if it'll work but you might want to try running redundead on the disk image.

 

[Von Thomas]

What was your workflow for transferring the original fils, and how many backups were involved at that point?

 

[Ranniel Araw]

Funny thing is I made a disk image so that the data would be safe. Oh the irony.

i was thinking of implementing this on our workflow, prior to disk image it should have prompted an error if there's a corrupt files on the original disk. If the mounted image has problem on it's contents, what could have possibly go wrong? I hope you have a 2nd copy of the original disk.

 

[markparry]

This was early on in our use of the camera and we were still getting used to the workflow. I thought that by copying to a disk image that I was protecting the data. Because of the time involved, I don't make disk images any more. I'm going to try REDundead on the the image and see what comes out. I have also looked at R3D Data Manager and will probably go that route.