• Apple Final Cut Pro

  Error Code -36 while attempting to Duplicate my FCPX Multicam Project

  Posted by Robert Esmonde on February 17, 2012 at 9:03 pm

  While attempting to back up (Duplicate) my FCPX 10.0.3 Multicam project I’ve repeatedly run into a hard disk error (Error Code -36) on external eSata disks attached to my Mac Pro (2008). After a few minutes of copying files I get an error message. The amount of data copied varies a little each time. The target disks pass Disk Utility diagnostic tests with flying colours.

  I’ve tried it on two separate 3.5″ Seagate Barracuda 1TB drives, in an eSata/USB combo enclosure, and in a USB/eSata Dock. I’ve chosen to ‘Duplicate the Project and Referenced Events’ so that I’ll have a copy of all of my original media, at least until the edit is complete. The eSata devices are connected to a backplate on my Mac Pro and the plate is connected to my spare motherboard Sata connectors. I’m only connecting one eSata device at a time. I’ve had no problems with this setup before now.

  fcpxesatabackuperror.png

  See above image for details of the error messages. I always get the ‘The Finder can’t complete … (Error Code -36)’ message shortly after FCPX begins duplicating the project, and I sometimes get the ‘The disk was not ejected properly’ message. When I tried to move the files, including the original media (approx 466 GB) using the Finder I run into the same problem. Some of the files are large – about 1 hr. of ProRes HD material.

  One of the drives I’ve been trying to back up to is a brand new replacement Seagate Barracuda 7200.12 1TB drive from Seagate. I used that bare drive in the dock. I’ve re-partitioned and formatted the drive a few times (one single 1TB partition) but I always end up with the Error Code -36 message.

  One quirky thing is that I tried using a newly formatted 40GB 2.5″ Samsung drive in the dock and selected a few of my project .mov files to copy across and it worked fine without any error messages. Obviously, with such a small drive, I couldn’t attempt a full backup.

  Anyone come across this before, or able to offer any suggestions?

  Thanks.

  Robert Esmonde replied 14 years, 2 months ago 1 Member · 0 Replies
• 0 Replies

Reply to this Discussion! Login or Sign Up