-
Plagued by general error
Well this is a sticky wicket.
We are working on a big show in London. We have six G5 units hooked up to gigabit and sharing media through one of them that is fiber channeled to an Xsserve Raid.
One user had run into a problem whenever the shared volume of the Xraid was mounted on her machine, a general error showed up on trying to open any FCP projects. When she ejected the shared RAID volume she could open them.
Today she (for various reasons) had to move to work on the machine connected via fiber to the Xserve RAID. So as not to kill productivity, we moved the RAID to another machine with a Fiber card. Both the machines that have hosted the Fiber Channel are quad G5’s with 8 gigs of memory, latest OS and FCP 5x updates.
Now the new host machine for the Xserve cannot open a particular (and critical) FCP project. General Error on opening. None of the files used by the project are on the RAID volume, nor is the project file itself. All of that is local stored. In this case, even when the RAID is ejected, the project file has the same General Error problem now. Tried trashing prefs, zapping PRAM, restarting, everything short of reinstalling the app.
So now we’re sort of dead in the water… ANY thoughts ? We’re working on tracking back selects, clips, trying to work out if we have some corrupt piece of media somewhere… I checked permissions on the volume, everything seems wide open…
So we’re in deep.
Any help appreciated.
Best,
Bob Bonniol -
5 Replies
-
You’ve tried putting everything back to its previous config?
Have you made a duplicate of the project & tried opening that?
What about trying to open the last good copy in the Autosave vault?
just a few thoughts..
Peter
-
Are all the machines using the same version of OSX and drivers, etc?
Next thing would be to try yet another machine, once you have exhausted the routes that Peter suggested in his post.
Have you tried opening it with no other machines connected to the Xraid?
-
Sorry 2 of those points made no sense, have you tried disconnecting everything on the system, just going back to basics with it, removing cards, maybe transferring the media to a new drive etc.
-
Bob, try this. Put everything back to the way it was. Boot FCP. Change the scratch disk settings to something local on the machine.
I THINK you are hanging because fcp is looking for a scratch disk that has been moved. This happened to me, and doing the above fixed it.
Good luck.
-
Thanks Jim… we’re going to try that out now… We’d moved on to other parts of the show, but the time has come to sort this out.
Reply to this Discussion! Login or Sign Up