schepers wrote:Andrew Kolakowski wrote:Problem is that if this is your drive failing then you may think it's Resolve corrupting it (and if you work on file in Resolve which forces drive to do activity then it will happen ), not drive
Solution (and proof) is crazy simple-
use different drive and finish project this way!And as pointed - checksums is good "measure" of corruption. Corruption can happen at any point, although today even internet is quite reliable. If you use good tools and hosts then it's about as reliable as local disks these days.
Besides- author of the post is not writing anymore, so case closed.
Why you say that I don't writing anymore and case closed? Please take those words back. I constantly communicate trough the forum and have direct contact with Blackmagic over e-mail.
I also send opened a support ticket at the disk factory. I hope to hear back from them soon.
It could be the disk, but I don't have any other problems with the disk. No crashes at all. The disk is a professional grade G-Raid Thunderbolt 3 20 TB and is about two years old now. Also not heavy used.
Please be nice and don't judge people.
BR, Robert
You didn't for long time so I assumed case closed.
Class of the drive is irrelevant here. Any drive can fail at ANY moment, so fact it's new, not used much etc. is about meaningless when it comes to those failures (failures in first few months of usage are probably more often than later unless drive is very old). I'm looking after storage around 500TB. Had few drives dead over last few years, but in some boxes none. It's a total lottery.
Have you tried copying original source to new drive and exporting project from there?
Have you tried copying new file to your maybe faulty drive, then keep playing this file many times in eg. BRAW Player (so disk has activity) and then checking if corruption is there (so not touching Resolve)?
Have you tried simply locking file for write and then working in Resolve with it (if Resolve has no write access to the file it can't corrupt it)?
Your first file clearly had corruptions, actually more than your reported. You have to be methodological in this case.
Take source file, make 100% sure that it has no problems. Generate checksum for it. Any further copy etc needs that checksum to be verified straight after copy. Then play with file (so there is a lot disk activity) and verify checksum again. Do the same with Resolve. Verify. If problem is there after Resolve step then do the same with new drive. If Resolve causes corruption then it should happen again.
You have many points of failure -drive, TB3 connection, cable, etc.(or even OSX issue with particular TB3 device).
Without proper approach you will be just wasting your time. It's your choice
People keep pointing you to recording issues, without reading your description of the problem. According to you
your main source is fine, so no idea why everyone suggest recording issue, causing unnecessary confusion ?