Corrupt file?

Hey!

I have a weird issue that I have never encountered before.

I was filming a show, and had to transfer the footage (AVCHD from Sony FS700) to FCPX so I could format the card for next days shoot. When it was time to hand over the footage, the file just wouldn't work. It stops copying at around 80% in the Finder. Also cannot move it via FCPX.

I've managed to export the entire footage by exporting it a piece at the time. If I try to export/render the entire clip it fails. But byt exporting in 3-4 bits, I got everything. I can also view it, skim etc with no issues.

So now I am stuck with that footage on a hard drive I don't want it on. It's a fairly substantial file, around 1 hour and just under 15gb. In Finder I get this message: "The Finder can’t complete the operation because some data in “Clip #5.mov” can’t be read or written. (Error code -36)"

Anyone have any idea if there's anything you can do?

Hi Dimitri,

How is that drive formatted?

- Ronny

I've tried to copy to the internal SSD, two different USB3 drives and a USB3 stick.

What is the format of the drive where the problematic file is stored?

- Ronny

Mac OS Extended (Journaled)

It's imported using FCPX so it's in a FCPX library. All other files from same night work just fine. Just this one that something funky happened to.

You can bypass Finder errors by executing the copy process in Terminal. Are you familiar with Terminal?

If so: create a new folder on the destination drive (this drive must be MacOS Extended as well).
Then launch Terminal. In the terminal window, type this exact line including the spaces:

sudo cp /

To be clear, that is: sudo (space) cp (space) forward slash

Now drag the problematic file into the Terminal window, right after the forward slash
The path to the file will automatically be entered in the window

Type a new forward slash

Then drag the folder you have created on the destination drive into the Terminal window
The path to the folder will automatically be entered in the window

Press Return

Terminal will ask for your admin password. Enter the password (you won't see anything while you type, just enter the password correctly)

Press Return

The file will be copied into the folder you have created on the destination drive. Any errors should be bypassed.

If this does not work, or if you are uncomfortable with using Terminal commands, post back and I will post a step-by-step including screenshots.

- Ronny

Ronnie
He will also most likely need to 'rm' in Terminal to remove the files if I am reading his post issue right.
I hesitate to instruct anyone in using rm in Terminal if they don't know what they are doing.
I'll let you have the honor.

Great advice by the way. I think drag and drop to Terminal is a great way to go and not screw up.

I also wonder if Dmitri made a camera archive off the card when it came in. Sounds like some form of corrupt file/clip. If you have an camera archive, it might correct the file/clip.

Hope this helps, Greg

No camera archive...

I want to move the entire FCPX library that the file is part of, but not sure how to achieve that when it stops while trying to move this particular file...

Is there no applications for fixing broken files or anything?

I think this is the first time I've encountered a file not being possible to move. Files getting corrupted and rendered useless while moving them or not being able to move due to a hard drive error has happened, but not being able to move a file at all because the file is a first for me as far as I can remember!

Hi Dmitri
Have you tried Ronnie's suggestion? Are you not comfortable with Terminal?
Ronnie is using the cp command which means "copy".
His step by step is good. Your old files should still be in place. I don't mean to scare you about using Terminal.
Using "sudo" (SuperUser 'do') allows Terminal to manage files without having the MacOS safety net in place, in this case it will just copy the files even if it encounters an error.
These are UNIX commands.
mv is used to "Move" files and rm ="Remove". Using "rm" while as sudo can cause serious problems if you remove the wrong file, you can even remove necessary system files, and this is why I hesitate. Got in trouble with someone once when they didn't follow my instruction to the "T" not "t". Yeh even capitalization matters in Terminal.
That is why the drag and drop method for file location is so wonderful. As long as you grab the right file in the finder, you will not accidentally act on the wrong file.
This is a good first lesson in command line/Terminal.
I think once the file is "Removed" you will not have any problem moving the library from inside FCPX. Looks like corrupted clip.
You do have to be an administrator on the computer and anytime you invoke sudo you need to type in your password.
Finally, you can read through everything prior to pressing the "Return(enter)" key. When you drag and drop, you will see location paths in place of the icon for your folder.

Hope this helps, Greg
p.s. I never told you about "rm"
This message will self destruct in 5 seconds Mr Phelps

Great points, Greg.

Dmitri,

There is no magical trick for fixing corrupt files. Of course you could buy specialized software that can fix certain corruptions. An example of such software is Remo: www.remosoftware.com/remo-repair-mov

But there is no guarantee wether this will really solve your specific issue or not. Furthermore, many of these applications require you to save the fixed file as a new one. This would make your file offline, and possibly un-relinkable, in FCP X.

If you want to copy the entire Library including the corrupt file to a new drive, there is one thing you can try: ZIP the entire Library and try copying the ZIP file over to the new drive.

If you can create the ZIP file but you still cannot copy this file over to the new drive, you will need to use the sudo cp command in Terminal to copy the ZIP file over. Libraries cannot be copied over using this command, because Libraries are seen as directories and not as files.

- Ronny

Well Ronnie I just learned a couple of things.
The zip idea might just work, never thought of that.
I also hadn't thought about Libraries being directories.
Great day to learn some new ideas.
Your instructions were for the file, not the library so if he can move that then he should be good to go.
Targeting the offending file I think is the way to resolve it, so it just occurred to me that Dmitri might be able to just delete the clip and footage inside FCPX and get it to export. Worth a try if he can identify the actual clip in question.
Also Dmitri, have you applied any 3rd party effects? That could be an issue, especially if the clip plays in the library browser. If so, you could also try to disable/remove the effect prior to export.
All said and done, Terminal may be the easiest way.

Hope this helps, Greg

Dmitri
I tried to see if the error code (-36) would give me any hints, but this one is pretty generic; I/O error.

Here is a link to a lot of error codes for anyone interested.
krypted.com/commands/comprehensive-list-...ac-os-x-error-codes/

Also didn't I read on another post you are now on El Cap? Did you install using MA or clean install?
I finally left Mavericks and clean installed EC. Wish me luck

Best of luck, let us know if and how you resolve it.
Greg

Great advice, Greg.

And regarding the rm command: I use a little trick when I need someone to force-delete a corrupt file using rm, and I feel this person does not have any experience with Terminal.

First I tell the person to empty his trash and then to put the corrupt file in the Trash. Corruption or permission issues usually don't prevent files from being put in the Trash.

Then I tell him to enter rm -R / (or sudo rm -R /) in Terminal, to open the Trash in Finder and to drag the file that's in the Trash window onto the Terminal window. Pressing Return will then permanently remove the corrupt file.

This method is relatively easy and it absolutely prevents accidental removal from any other files than the one you need to force-delete. I have seen too many desperate posts from people who have permanently lost critical files because they messed around with rm in Terminal without really knowing what they were doing.

Best of luck with El Capitan! Still not for me yet, but the new beta does look promising

- Ronny

Another great idea about using Trash.
I just added it to my Evernote files so I can find it again.
Would have saved some grief in the past.
Funny when trying to help, if something goes wrong guess who gets the blame no matter what.

Between projects, was having some issues with Mavericks, not using any no go apps/plug-ins so cloned old, in with the new. Updated iPhone 5s to 9. In for a pound forget the penny. How's the new iMac?

Thanks Ronny

I am thoroughly enjoying myself with this new machine. And you were absolutely right, you cannot downgrade the new 5K iMac to Yosemite. That's because this machine uses completely new and faster RAM that can only be addressed within El Capitan. As I use it as my test system, this does not matter. But until EC is completely cleared I would not use any new 5K iMacs for production.

Today I got some reports from my friends at Metronome, saying that their new 5K iMacs constantly lost the network connections to their servers. Fortunately they seem to have resolved the issue by installing the OSX 10.11.2 beta, so I have good hopes for the near future. Once the sky has cleared, I think EC will be a huge improvement. Certainly when FCP X will receive its next major update, which I don't expect to happen very soon. I do think it will be worth the wait

- Ronny

Ronny didn't want to argue about downgrading, but good to know.
Generally when new Model numbers come out and new features in OS, older OSs don't have the kext for the new machine. Like you say, new hardware needs software/firmware support.
I have installers back to Jaguar either on disc or thumb drives. Used to have System Software back to 2.5 on 3.5" disks.
I really expect some new features in FCPX10.3. Hope your are wrong on timing, but who knows. Announce no later than Jan, launch Feb
Lots of new frameworks & expansion of AV components/library structure, etc… in EC. True editing sharing maybe?
Sure to be lots of growing pains/bugs.
Wasn't discovery-D fun? I actually missed it by staying on Mavericks.
Surprised no USB-C on your iMac.

OK enough hijacking thread.

Be Well, Happy Editing
Greg

I think you must have a crystal ball

Happy editing!

- Ronny

Thanks Ronny & Greg!

I tried to zip the file but that also stops at about the same place.

Guess I at one point have to use the Terminal trick.

Thing is, how can I get it back into the FCPX library if the file can't be moved by FCPX? (I still want to be able to use the file in FCPX!)
I guess I could export/render it as ProRes and then delete the file and re-import the ProRes but I don't really have the hard drive space for that...

Hey Dmitri,

If you still need the file inside the Library, just use Terminal and copy the entire zipped Library onto the destination drive. The ZIP is considered as a regular file, so this should work.

Once you have copied the zipped Library over, we can show you how to delete the corrupt Library from the original drive.

- Ronny