I have been trying for hours to get the database to rebuild without success.  I had trashed the database after a few crashes throughout the day but now it seems I've created a bigger problem.  I have been able to rebuild the database with 20 out of the 3900+ files I have, but I'm now dead in the water.

The problem began while I was working on Symphony 6.0.0.  I've since upgraded to 6.03 thinking it would fix the problem, based on a few threads in this forum.  Wrong.

This is an external 6TB G-Raid that was supplied by the client.  The drive is connected to the system via eSata.

I've never in two decades of Avid work seen a problem like this.  Any suggestions?

My system:

Mac OS 10.7.3

Processor 2 x 2.93 GHz 6-Core Intel Xeon

Memory 32 GB 1333 MHz DDR3

Running:

Symphony 6.03

with Matrox MXO2 Mini MAX running 3.0.0.0073 software

Just tried copying files to a different drive & rebuild the databases with no luck.

This really is strange, I've never seen this either, but:

Scott Silva:

...I had trashed the database after a few crashes throughout the day...

Please elaborate. What were you doing when it crashed and what error message did you get? Check your "fatal errors" folder for any relevant log files.

Scott Silva:

This is an external 6TB G-Raid that was supplied by the client.  The drive is connected to the system via eSata.

Have you verified how the Raid is formatted? Is your client PC or Mac based?

The G-Raid drive is formatted Mac OS Extended (Journaled)

The initial crash happend while I was in Color Correction mode.  What was happening as I was moving from clip to clip I would get the color beach ball before my system would move the time line.  That sluggisness forced me to save constantly, just to be safe.

The Error I saw most was - 

"segmentation fault" in thread "MainThread", at address 0x0

Right now I am copying files a few at a time and rebuilding the database.  I think I may have identified two files that are hanging the database rebuild process.

What happens is the Symphony hangs on the 2nd database rebuild window.

Also my client is MAC based.  (As am I)

Scott Silva:

Right now I am copying files a few at a time and rebuilding the database.  I think I may have identified two files that are hanging the database rebuild process.

I was starting to suspect corruption and was going to suggest that next. Usually during the scan/index mode if a corrupted file is found the system pauses with a prompt window with options to ignore, continue or quarantine. Did that happen on the 2nd database rebuild when it hung?

Scott Silva:

"segmentation fault" in thread "MainThread", at address 0x0

When that has come up due to Lion X OS presets, the recommendation is to get info on the Macintosh HD and under permissions set "everyone" to "read/write".

Larry Rubin:

Usually during the scan/index mode if a corrupted file is found the system pauses with a prompt window with options to continue or quarantine. Did that happen on the 2nd database rebuild when it hung?

No.  There was no prompt.

Larry Rubin:

When that has come up due to Lion X OS presets, the recommendation is to get info on the Macintosh HD and under permissions set "everyone" to "read/write".

Permissions are set to Read & Write

This issue sounds similar to one another person and I are having. In my case I came across the problem the same way you did. No solution yet, but I've been able to narrow down to a degree what might be causing it on my system. The threads are located here

http://community.avid.com/forums/t/111850.aspx

And here

http://community.avid.com/forums/t/111921.aspx

The current workaround is to use another system not running 6 to rebuild the database, although hopefully we can find something better. If you have any luck let us know. 

Btw, if you're still having the segmentation fault error while color correcting, I was able to fix it by creating a new avid user. 

Thanks Kyle.  I'll check out the threads.

Right now what I've found is that there were 485 audio files that, if included in the MXF "1" folder would hang the database.  Yet they were fine before I started crashing & the client created the files on a Media Composer 5.5.3 running on a Mac. So who knows.

I also suspect that the Matrox MXO 2 Mini is the cause for a lot of headaches, like long delays when switching between clips while color correcting.

My original error messages have subsided without these files included.  Now it's just sluggish color correcting, which seems to be a Matrox problem.  May be switching to a BlackMagic DeckLink Studio this week.

I tried using my laptop to rebuild databases but I still experienced trouble with the same media files.  :(

I'm thinking it has something to do with the audiofiles because they are in grouped clips on the timeline.  Or maybe the files are the incorrect sample rate (44.1 instead of 48)  Will find out Monday when client gets into office.

I'd hate to create a new user but I may break down and do it.

I'll let you know what I find out.

I did the piece by piece method.  Took 7 hours!  Thats how I know it is 485 files that caused the system to hang.

Also the audio files are from sound recorders in the field.  Just do not understand why the MC 5.5.3 can import them originally and the Symphony 6.03 cannot deal with them.

Right now since I am only worried about picture for color correct, I can live without audio.

Scott Silva:

Right now since I am only worried about picture for color correct

I appreciate you need to get on with the Colour corrections but do you have time to try reimporting one of the offending BWF files from the field recorder directly into 6.0.3?  Thanks