Hi, I have a LaCie Hard drive and it got disconnected and I wasn't aware and then I subsequently shut down FCPX.
This often happens and I never have a problem, however, when I went to reopen Final Cut everything is ok, it opens my local library automatically so i selected external and the window pops up saying it's loading my events and just when you think it's going to show up FCP quits unexpectedly.
I have important projects that I've worked hard on in there and can't access them and I don't know what the problem is,
It's really frustrating and I have deleted FCP and reinstalled but this did not work.
I'd appreciate any help. I'm running FCPX 10.4 on OS HIgh SIerra version 10.13.12
Are your backups located on that same drive or on your computer's hard drive? This is when I would start trying to open older versions. Also, I know you've reinstalled FCPX but certainly try to open the project while holding down command & option keys to delete preferences as well. I know this is frustrating. Good luck.
thanks for the reply Jarrod, the backups are located on my computer and I forgot to mention I have already tried to open previous backups which all failed as well as deleting render files and the flexolibrary.
Are you suggesting holding down the command and option keys when opening the library? I don't have access to the projects because i can't access the library!
Yes. Sorry for the old school nomenclature. Hold down command & option keys when opening the library. It should ask if you want to delete preferences and hit yes. Sorry the backups didn't work. That suggests it may be something more insidious at play here. I've never experienced this exact issue. Maybe someone else can chime in with some other options?
I'm guessing that trashing preferences did not work because once you did and FCPX launched, you attempted to open the same culprit project. You likely would have been able to open your other projects after having done that if you tried those first. Secondly, consider Digital Rebellions Pro Maintenance tools. There is a project repair utility that works very well for fixing corrupt projects. This probably would have allowed you to open and continue work on the project you ended up deleting. I believe they still offer a 10 day fully functional trial, but the whole package is a good investment for those situations. This doesn't help now because you already solved your issue, but something to think about for future problems.
While this was a single external drive, this situation also illustrates why a RAID drive is not adequate backup. It can get suddenly disconnected, or an app crash or hang or OS crash or hang can cause an uncontrolled shutdown. The HFS filesystem layer is fully transactional but to my knowledge the SQLite database used by FCPX is not. SQLite has some transactional features but is not fully "atomic" in all cases like Oracle or SQL Server are. Therefore an uncontrolled shutdown in the midst of a transaction might cause logical corruption.
The SQLite database itself (like Oracle, SQL Server or even the HFS filesytem) has two conceptual layers: the application data and the system structures which manage this. With HFS+ you can run a check via First Aid or Disk Warrior but this only checks the system data structures, not the user data. Likewise you can open an FCPX library using SQLite and run PRAGMA integrity_check but it doesn't check for referential integrity or any other logical anomaly with the user data contained therein. Only the app itself (FCPX in this case) understands the meaning of the data stored by the database layer.
E.g, you can open an FCPX library using SQLite and randomly delete rows, change values, etc. which could cause FCPX to crash, yet PRAGMA integrity_check will still return OK. That's because it's checking the b-trees, linked lists -- IOW the scaffolding supporting the data -- not the data itself.
FCPX is no different from any other database -- there is no good solution unless the app layer itself does additional checks. I suspect this is what the Lightroom integrity check does.
The best solution is have multiple versions of backups in case an error creeps in, you later commit a bunch of work and only later become aware of the error.
Another useful step is using only Thunderbolt storage since it is less likely to spontaneously disconnect than USB, also run all computers and drives off a UPS.
As dgwvideo said you could try Digital Rebellion's project repair tool. Several of their other media repair tools are specific to Quicktime files, so they won't repair, for example, an XAVC-S file. But maybe the project repair would work.