It crashed on Tuesday with the UMP i used. It wrecked three SSDs worth of footage during the shooting.
I found a solution to rescuing the files (kinda), but i haven't found a solution to it not happening anymore, but i'm on it.
How I rescued the files (using Windows):I started off doing a 1:1/bit-by-bit/dd/whatever you may call it backup using HDD Raw Copy. This is optional, but it creates a "raw" .img-Image on a separate drive which you can use in the next step. This just ensures no further damage is done to the SSDs or the footage.
I opened testdisk, a fabulous free piece of software which allows you to open up the damaged .img or SSD and interpret it using predefined filesystems. Even though it automatically interprets both .img and SSD as "HPFS - NTFS" instead of exFAT (and i found no exFAT in the available systems), it found
MOST of my footage. The program is able to copy these files back to another drive, and in my case none was corupt.
My observations:- The rescued files don't seem damaged, only the broken file system makes it unreadable.
- Even though the problem occured on the UMP with firmware version 6.0 and our replacement UMP had the same setup but the newer 6.2 firmware and no problems whatsoever, it seems like the data loss never occurred on the 6.0-UMP on the projects before. The question is if the newer firmware eliminates this issue, we had no time to test this yet.
- Interestingly, on both rescued SSDs C001-C003 got lost, i could only save C004 and the ones following.
- It seems like the camera started writing the new file and failed, because the latest clip on both SSDs got created, but contains no information but the correct file name. Thus I doubt a hardware issue like dust is the problem.
- We somehow fixed the third SSD by pressing on playback directly after the problem occured, before we turned the camera off and back on and other stuff. So maybe restarting is more or less "saving" the damage and going in the playback menu is somehow repairing the damaged file system?
I will try to take some time to inspect the issue more clearly, but i hope the problem is solved in the newer firmware.
Someone experiencing the same problems still? Would be interested to hear more details about your situation and if my solution to rescuing data helped.
Greets
Georg