-
Persistent Catalog B-Tree Errors
So here is the saga of my new FCP system. This is my first FCP setup. I’ve been in post production for over 10 years, Avid for 5 years, Media 100 prior. I decided to get an FCP system for HD work. Anyway, here is the configuration:
Quad G5, 4.5 gb Ram
Kona 3
Atto UL5D
Dell 2405
Huge Systems Media Vault U320-RX 1.6TBAnyway, when I first received the system, I got some errors the first day trying to digitize some HDCAM footage. After upgrading the AJA drivers, I called AJA and they suggested re-striping the drives. I did that and was able to digitize no problem. A few days later I had some issues one morning with the Huge system drive after booting up. Some of my files and folders were missing. I ran the disk utility and it said “Keys out of sequence, Catalog B-Tree needs to be repaired”. The disc utility was not able to repair this problem. I did not have a copy of Disk Warrior or some other disk repair utility at the time. Since the media was just test data, I went ahead and restriped the drive.
I went ahead over the next few days and digitized a lot of footage for my first project. About 3 days into it, I booted up the system one morning and had the same “Keys out of sequence, Catalog B-Tree needs to be repaired” error. I purchased Disk Warrior and it repaired the directory. I lost about 1/3 of the footage. I spent the next few days redigitizng the lost footage and the day after I finally got all of the footage redigitized, I booted up the system and got the “Keys out of sequence, Catalog B-Tree needs to be repaired” error again! This time Disk Warrior could barely repair it and I lost a lot of the media.
I was planning to go away for a long needed vacation for a week so I shipped the drive back to Huge Systems while I was gone. They performed diagnostics on all of the drives and they said that everything was in good working order. They upgraded the firmware and returned the drive to me. I hooked up the drive a few days after I got back. I digitized about 6-10 clips and everything seem to be working fine for the first 3-4 days, then yesterday I booted up the system and got the same damn error again. My entire capture scratch folder had just vanished. Disk Warrior can fix it but I and everyone else I asked, have no clue why this is happening over and over again. I called Huge Systems again and they are going to replace the controller board and power supplys. This is their only suggestion and hope to fixing this ongoing problem.
I have upgraded eveything I can think of; the latest OSX, FCP HD upgrade, AJA & Atto drivers. I boot up and shut down the system in proper order. I bought a FW800 drive for SD footage and have had no problems with it. Prior to the last time I got the Catalog B-Tree error, I added a SCSI raid from an older Avid system to the FCP system. The morning I got the last Catalog B-Tree error, the older Avid raid was fine. The Huge system drive was the only drive that got the error.
I don’t know if anyone else has ever experienced this problem as many times as I have. I obviously need to fix this before I can take on any project with a time sensitive deadline. Any advice or suggestions would be greatly appreciated. I am shipping the drive back to Huge on Monday morning and was told I should get it back on Wednesday with the new controller board and power supplys. I’ll keep you posted.
BTW, other than the hard drive issue, I really like the FCP system.
Sorry for this long and drawn out post.
George Bellias
Jade Productions -
5 Replies
-
Did you call Huge Systems?
Something wrong with the raid controller? -
I did call Huge Systems. The first time I sent it back to them to check it out, I sent it with my Atto UL5D card and cables. I am sending it back to them again this morning and they are going to replace the internal controller board and power supplys.
George Bellias
-
I ASSUME that you downloaded the latest driver from ATTO for your UL5D when you installed it. HUGE is a great company, and they will take care of you.
bob Zelin
-
Bob,
Yes I did. I actually called Atto tech support and they were very helpful. Still, no one has a clue why this is happening so much.
George
-
I had a power outage and [gulp] no UPS device protecting my XServe RAID [connected via copper fiber to FCP G5 2Ghx DP]. I have had power outages before and, thankfully, I have had no problems when restarting the RAID up until recently. I guess I was lucky before, and I have since learned my lesson.
After the recent outage, the RAID started up again OK, but after a short while, it unmounted and would not mount. Disk Utility gave me the same error you reported. I searched around and it seems that I was pretty much screwed, so I thought.
I called in a specialist who ran Disk Warrior [like I couldn’t have done that myself, except I would rather not compromise anything on the RAID by doing something irretrievably bad if it was the wrong thing to do], and it fixed the problem nearly instantly.
I ignorantly thought that the battery supplies in the RAID were for power outage protection, but it was actually only to protect the cache read/write. I was surprised that my VAR did not recommend an UPS when we bought the system, but that is water under the bridge.
I have since rebuilt both arrays and restriped the RAID with the correct options selected for having an UPS device, and no major issues.
I don’t know if this helps, but at least this episode is somewhat similar.
steve covello
double wide post
Reply to this Discussion! Login or Sign Up