![]() It was great to see Matt’s suggestion confirmed in this instance by Marc. ![]() In my researching the problem I read a great post by Matt Hovey about deleting this file. Once Marc had connected to my Mac he deleted the fsck_hfs file from the Activity Monitor window and the Stardom drive popped back onto my desktop. They offered me technical support via instant messenger and a shared desktop screen. In the meantime, Marc from Alsoft got back to me to confirm that the version of OSX would not be the problem. My friendly local Lambeth based IT support company Trams kindly ran DiskWarrior on my Stardom RAID from their Mountain Lion Macs and reported the same error messages as me. ![]() Alsoft helpful technical supportĭay three: I woke up thinking I should check the OSX Mavericks compatibility with DiskWarrior. Or I can start transcoding the original camera files from fresh. In the meantime, I’ve decided to order another external drive so that I can start moving any media I can recover if need be. I hope to hear back from Alsoft tomorrow and will then know how to progress. It’s a safe work-flow but I don’t have a back up of all the transcoded files. I have two separate copies of the camera files on separate hard drives. So night two and it’s looking like it could be a busy few weeks ahead transcoding all the original camera files. After requesting some technical support from the Houston based Alsoft team they responded quickly and asked me to run DiskWarrior again and then send them my nMP console information. ![]() I am running the latest OSX software so I wondered if there could be some compatibility issues there. There does seem to be some comments around which suggest that it might not work so well with a Time Machine external drive. I’ve had a good look at the web and really it looks like DiskWarrior is the main solution. I tried TechTool Pro 7 to see if that could help but it just stopped progressing without any kind of notification. For the first time since I’ve used it, DiskWarrior could not repair the drive directory. Problem-solving with Disk Warriorĭay two: In the morning I updated my Disc Warrior to the latest version 4.4 via the Alsoft website and tried to fix the Stardom drive directory with that great piece of software. As an experienced Avid Editor, I still get the occasional surprise affecting my workflow but wasn’t expecting on fixing a RAID 5 drive array. Disk utility suggested I back up the files and re-format – great when you have 7TB of transcoded video media that you are editing with and no current spare hard drive large enough. It ended up being a long night as Disk Utility was unable to repair the disk and was flagging in red – Invalid index key and Invalid key length. I tried it again a few times and then quickly copied my Avid projects onto a separate G-Raid drive to protect my Avid editing timeline and project. This was the first time I had seen that TM backup failure message. The time machine back up could not complete. A small error warning popped up on my second monitor. I finished the day with my usual time machine back up onto my Stardom 12TB four slot Raid 5 external drive. Disc Utility showing invalid index key and invalid key length warnings How editing workflows can get interruptedĪ normal editing day: I was using my MacPro (nMP) (OSX 10.9.4) and Avid Media Composer to edit down a series of interviews for a short film I am making. I post this account of how the problem was resolved in case it might help anyone resolve their similar issue. I would not normally expect to be fixing a RAID 5 drive array but when my workflow got suddenly got interrupted I needed to resolve the problem.
0 Comments
Leave a Reply. |