Currently Being ModeratedNov 30, 2012 3:09 AM (in response to somanna)
Hello to all,
I wish I could get guidance in this matter!
The above post, I have observed now, does not show up the screenshot which I had added and I wonder why!
I have in the meanwhile done this, and I am purposed to post the screenshots of every stage of my attempts to set things right:
This has been the first pop up which stared at me when I tried to open FCPX.
I then tried to open FCPX in an indirect manner, selecting a project on my Seagate-1 ext HD [which I had earlier duplicated from the original timeline which was on the SCRATCH DISK partition of my 3-partitioned Seagate 2TB ext HD] and asking for it to be opened by FCPX. Upon doing this, FCPX answered:
Since this event was not an important one for me, I wanted to delete it and thereby hope for FCPX to purr smoothly. I went to the event which was offensive to FCPX, an event which was located on the SCRATCH DISK:
and tried to send it to trash:
When I tried to trash it, this cautionary pop up turned up:
I clicked upon the delete button and then was faced with this sickening information:
Having experienced this situation before, I did this first: I ejected the the drive upon which the 'rogue event' was located by resorting to force quitting [ earlier, when the error-50 was active, this SCRATCH DISK would not eject and I had to force quit]. Upon remounting the SCRATCH DISK, I was able to go to the offending file, select and subsequently even successfully trash it:
Feeling that I had removed the offending event whose database was corrupted in the eyes of FCPX, I restarted FCPX hoping that it would now behave properly, but this is what it threw at me when I now tried to open it:
back to square 1!
PLEASE, PLEASE, PLEASE! Can anyone help me to successfully climb up and reach the 'HOME' of this 'snake and ladders' type of 'game'? What are the ladders which I need to climb and where are the snakes of whom I should be wary?
Any guidance, any help, anything positive, will be 'really' appreciated.
FWIW, these are the important posts which I had started/participated when I last encountered this problem:
This error code-50 is to me an 'old enemy'. I had encountered it about 3 weeks back and seems to stem from different issues. [ Re: error code -50 ,
Message was edited by: somanna
Message was edited by: somanna
Currently Being ModeratedNov 30, 2012 3:36 AM (in response to somanna)
I had kept away from opening FCPX for a little while and later, when I reopened it, this pop up turned up:
Now, FCPX is finding fault with, I counted, nearly 30 files/events! Since these 'rogue files/events were backed up, I clicked continue hoping that FCPX would restore them and become friendly with them as before. But when I clicked upon 'continue' FCPX's misbehavior remained unchanged:
Now, what should I do? In the first screenshot above, FCPX has stated that I could quit and manually locate and restore or remove the 'corrupted' databases. Can anyone let me know how to proceed ahead in this matter of restoring the affected files/events in the Finder?
Message was edited by: somanna
Currently Being ModeratedNov 30, 2012 10:11 AM (in response to somanna)
You may be having disk corruption issues. Try running Disk Utility to Verify Disk and possibly repair it - but I don't know if you'll be able to recover those files unless they are backed up somewhere else.
Currently Being ModeratedNov 30, 2012 10:02 PM (in response to Luis Sequeira1)
Thanks Luis for chipping in. I guess you may be right on this issue...but, in this moment where my head is spinning and reeling, I feel, FWIW, FCPX's sixth version seems to be having some stability issues.
I have tried to use disk utilities services for repair but found that this particular disk could not be mounted. In a similar situation 3 weeks ago, I had downloaded a free download [trial] of PFman and somehow managed to come out of that mess. Unfortunately the free trial period has lapsed and I am unable to recruit its services this time .
I do not feel I should buy this application right now and there is no assurance that this problem will go away. Luckily, when I faced this problem last time, I was able to transfer all of the contents of this scratch disk to two other drives [i.e. I have 2 copies of all of my finished projects and unfinished projects]. However, I had done this: I duplicated projects along with 'used clips only' for my finished projects, and for unfinished projects, I duplicated the projects along with all the associated event clips.
Now, as I shall try to 'repair' the Seagate [which comprises 3 partitions] I will also post the screenshots associated in case it helps:
The first partition I have named as camera archives where I have stored as disk images all of my camera footage.
FYI, I have made two copies of these archives and placed them on 2 other drives.
The above 2 screenshots show that DU has found no fault in this partition.
The screenshot above shows that the second partition named 'MOVIES' needed a repair. I have exported QT movies from my timeline to this partition. Luckily, I have now made 2 copies of this partition and placed them on 2 different ext HD. This part of my work is safe. Upon clicking repair, this turned up:
From the above information, I gather that DU had stopped repairing this partition for this error: could not unmount.
When I next turned my attention to the partition named 'SCRATCH DISK' DU responded in a similar manner and stated that the partition needed repair but stopped the repair process because of its inability to unmount.
Luis, I am totally at sea with all these processes and do not know what these statements imply. If you look at the screenshot above, you can read the pop up at the top which states that DU stopped repairing Seagate Movies/ could'nt unmount the disk. A little below, under Verify and Repair volume "SEAGATE MOVIES" this is mentioned:
'VOLUME REPAIR COMPLETE'!
Updating boot support partitions for the volume as required.
ERROR: Could'nt unmount disk.
Can you or anyone let me know the 'gross' implications of these pop up notifications in a plain to understand manner by which a layman as me can understand? What is the next step I should take in this matter?
My ultimate plan for this troublesome ext HD is this: to erase it completely and have it only as a single [unpartitioned] volume and use it for TM backup to my Mac's internal HD.
Waiting eagerly and hopefully for someone to throw some light as how I should proceed ahead in this matter.