Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Help, R3D Data manager Checksum Error

Jesse Lyon

Member
Joined
Apr 15, 2009
Messages
11
Reaction score
0
Points
0
Shooting 4k on 16g Cards Ran through R3D Data manager, "error" on 2 cards, I checked the log found 1 clip on each card says "failed to match md5 checksums"

I open the md5 log on teh card and on teh Back up HD both have 5 lines

_p
_m
_h
_f
.r3d

But the .R3D's first 3 digits in the long number in front of it are different on the card as it is on the Drive.

what does this mean?


Thanks all.

Jesse
 
What does the log in the program say? If you click on view results it will tell you specificially which files are corrupt. Did you try to "remove files with errors and try again"?

In addition, it may be that you were looking or changed some settings in a RSX file or MOV file. Errors on those files are not as important as errors in R3D files. You can set the option to "report only errors on R3D files" to ignore errors on other files.
 
What does the log in the program say? If you click on view results it will tell you specificially which files are corrupt. Did you try to "remove files with errors and try again"?

In addition, it may be that you were looking or changed some settings in a RSX file or MOV file. Errors on those files are not as important as errors in R3D files. You can set the option to "report only errors on R3D files" to ignore errors on other files.

I found the clip that has the issue in the log, "failed to match md5 checksums"

"report only errors on R3D files" is on

File size on the card matches the exact file size on the Back up drive. same number of files, proxies all play fine. the only differnece is teh name in the md5 file.
 
Does it fail on the same clips? Are the checksums the same in the 3 copies, but different in the source? If so, then there was a read error during the generation of the checksums. I would place your hardware in suspect and say the copies are fine.

If the checksums are different on all 3 copies, then your destination is having issues, and none of the copies are safe.

I would suspect the former case.
 
Back
Top