External HD failure: now FCPX 10.3 crashes

Hello all,

Having a huge problem with on of my libraries. Yesterday I was working on a project, when suddenly FCPX told me the files it was refering to were missing. Turned out that my HD had ejected (no idea why though). I closed FCPX and reinjected my HD to get started again. But now, FCPX keeps crashing at the startup.

Some observations:
1. Loading the library from a backup doesn't work, still crashes
2. I don't have a time machine backup
3. FCPX was doing some analysis when it ejected my HD

I've tried the following, of which none work:
1. Deleting render / optimized files manually
2. Deleting the flexolibrary file (and those steps)
3. Deleting the preference files
4. Rebooting
5. Trying to have one of these 'crash insight' software apps find the cause.

None of it helps. I'm really desperate: I have hours, weeks of work in this project and can't go back, there's just no time!

I really don't care about rebuilding the library, as long as I can keep the project file.

Is there anything I can do??? Your help is soooo much appreciated

I'd try working from your backup drive. If that works, wipe the working drive clean, restore. If it's still acting up, it could be a drive going bad.

But I see you said you don't have a TimeMachine backup. I assume that means you have no backup at all. Man, that's super dangerous, especially for work you get paid for.

FIRST! Get a copy of the free app "FCS Remover" (Digital Rebellion dot com) to totally remove FCPX. Reinstall it. Then...

Run Disk Utility to repair the drive.
If you have Disk Warrior, use it to repair the drive's directory (number one cause of drives appearing to die).

You could export your Projects as XMLs, create a new Library and import the XMLs into that new Library/Event.

See if it runs any better after that.

If it is a drive going bad, if you have another drive you can use, I'd export the work as XML. Use something like Carbon Copy Cloner to duplicate everything to the new (known good) drive (because it does a check sum), import those XML projects and start from there.

FCPX.guru wrote: I'd try working from your backup drive. If that works, wipe the working drive clean, restore. If it's still acting up, it could be a drive going bad.

But I see you said you don't have a TimeMachine backup. I assume that means you have no backup at all. Man, that's super dangerous, especially for work you get paid for.

FIRST! Get a copy of the free app "FCS Remover" (Digital Rebellion dot com) to totally remove FCPX. Reinstall it. Then...

Run Disk Utility to repair the drive.
If you have Disk Warrior, use it to repair the drive's directory (number one cause of drives appearing to die).

You could export your Projects as XMLs, create a new Library and import the XMLs into that new Library/Event.

See if it runs any better after that.

If it is a drive going bad, if you have another drive you can use, I'd export the work as XML. Use something like Carbon Copy Cloner to duplicate everything to the new (known good) drive (because it does a check sum), import those XML projects and start from there.

Thank you for your reply. How do export the XML without being able to open the library? I have no idea whether the drive is going bad. So far, there hasn't been an indication of such, but you could be right theoretically.

Are there other Libraries on that drive that work? Are there other libraries you can open directly (double-click them) that work? Or is FCPX crashing for everything?

FCPX.guru wrote: Are there other Libraries on that drive that work? Are there other libraries you can open directly (double-click them) that work? Or is FCPX crashing for everything?

Yes, 'new' libraries just work fine. It's definitely a library problem.

I have a library that crashes on launch, and when I try again it crashes, and then it just opens, my advice is try and launch FCPX close all open libraries and try to open it, if it crashes try a few more time to launch it, if it will work just once you're golden.

Also if that doesn't work try opening from backup, perhaps one of a day or two before the problem started