TheMayneEvent

Q: Error code 36 Please Help!

I am using an iMac with OS X Yosemite.

 

I am experiencing the error code 36 when trying to copy files from my external USB hard drive to any other drive... it could be my internal system drive, another external hard drive, or a USB thumb drive.

 

The hard drive I'm experiencing the problems on was originally an NTFS formatted drive on my old windows computer and it started experiencing a similar issue on that PC.

I then decided to format the drive to be mac journaled and keep it plugged into my iMac. Now even after the formatting it and copying all my files onto the drive I am getting the error code 36 when trying to copy files or folders to any other drive...

 

I've tried the dot_clean "fix" and it did nothing.

 

Any help would be EXTREMELY appreciated!

 

Thanks in advance!

iMac (21.5-inch Mid 2011), OS X Yosemite (10.10)

Posted on Nov 18, 2014 6:20 PM

Close

Q: Error code 36 Please Help!

  • All replies
  • Helpful answers

Page 1 Next
  • by Linc Davis,

    Linc Davis Linc Davis Nov 18, 2014 7:20 PM in response to TheMayneEvent
    Level 10 (207,926 points)
    Applications
    Nov 18, 2014 7:20 PM in response to TheMayneEvent

    The drive is failing and should be replaced.

  • by TheMayneEvent,

    TheMayneEvent TheMayneEvent Nov 19, 2014 5:27 PM in response to Linc Davis
    Level 1 (0 points)
    Nov 19, 2014 5:27 PM in response to Linc Davis

    Ok, thanks so much for the confirmation.

  • by FJ9999,

    FJ9999 FJ9999 Nov 20, 2014 1:59 PM in response to Linc Davis
    Level 1 (0 points)
    Nov 20, 2014 1:59 PM in response to Linc Davis

    I thought my drive was failing, but not sure that's the case.

     

    Shortly after installing Yosemite, Time Machine started failing with errors when trying to backup to my Seagate 4TB external USB drive (formatted one partition, Journaled/Encrypted).  Further testing showed that copying files to this drive sometimes yielded an error -36, and Disk Utility had trouble with certain erasing attempts.  Since the drive is under warranty, I had Seagate send me a new one.

     

    The new one arrived today.  Same problem.  I formatted as Journaled (not encrypted), then tried copying a large file to it.  Many such copy attempts failed with error -36 ("The Finder can't completed the operation because some data in "Filename" can't be read or written").  I've tried changing USB cables, changing the USB port on my Mac Pro, downloading Seagate NTFS drive (which shouldn't matter, but I did it anyway, based on another thread), and Kext Repair Utility.

     

    I do see there is another thread where a lot of people are having trouble getting USB external drives to mount under Yosemite, but that doesn't seem to be the problem here.

     

    It's certainly possible I got a bad replacement disk, but the similarity of errors is striking.  I'm wondering if something got hosed with Yosemite's ability to interact with external USB drives.

     

    Any other thoughts/input would be much appreciated.

  • by FJ9999,

    FJ9999 FJ9999 Nov 20, 2014 2:40 PM in response to FJ9999
    Level 1 (0 points)
    Nov 20, 2014 2:40 PM in response to FJ9999

    Addendum to previous post:  As described in Apple's USB and Firewire Quick Assist guide, I unplugged all other USB devices.  And, the external drive started working again -- no more error -36's.

     

    I plugged all the devices back in, one by one, and it still works OK, even after a restart.

     

    And, I remembered that I also purchased a new Canon USB printer just a week or so ago, around the time this problem started.  So, sounds like a conflict between USB devices.  Not sure why it's working after unplugging and re-plugging everything in, though.

  • by Diego arg,

    Diego arg Diego arg Dec 2, 2014 7:33 AM in response to TheMayneEvent
    Level 1 (0 points)
    Dec 2, 2014 7:33 AM in response to TheMayneEvent

    Same problem here... I send to yosemite feedback this problem.. I have 10 disks 2tb and 4tb and 3 of then income to have problems error code -36 randomly. I don't see problems before yosemite in any disk. The thing is or yosemite burn you disk or its a bugs on copy or communication thru disks. Its extremely rare that 3 of 10 disk have problems just after yosemite install. Obviously its not easy to change or format 3 2tb disks with the tons of data its contain...

  • by ajaszek,

    ajaszek ajaszek Jan 14, 2015 8:23 AM in response to TheMayneEvent
    Level 1 (0 points)
    Jan 14, 2015 8:23 AM in response to TheMayneEvent

    I contacted Lacie technical support with the same issue (2TB LaCie Rugged v2 USB3.0 & Thunderbolt) and they referred me here.  My issue was logged as -

     

    When copying data off the drive to my local hard disk with finder I get the following error message -

    The Finder can’t complete the operation because some data in “random.filename” can’t be read or written. (Error code -36)

    The specific file named changes on some attempts to copy. Finder then dismounts the drive. I have to unplug and replug the drive to see it again in finder.

    I have tried reformatting the drive but the error remains. Currently I have it formatted as 'Mac OS Extended (Journaled)' a single 2TB partition. I am using a 'MacBook Pro (Retina, Mid 2012)' and the drive is connected by the Thunderbolt cable

     

    I use thunderbolt and the drive dismounts.  I am using OS X Yosemite 10.10.1.

     

    Is this an Apple bug - an operating system that can't reliably copy files, or a failing drive? 

  • by scott252,

    scott252 scott252 Feb 5, 2015 2:04 PM in response to ajaszek
    Level 1 (0 points)
    Feb 5, 2015 2:04 PM in response to ajaszek

    Hi ajaszek,

     

    I reckon it's an Apple error, I have a LACIE 1TB Thunderbolt drive that I'm trying to copy data to a Seagate USB3 external drive, and it's been driving me nuts.

     

    It would start to copy, speed was awesome, but then it would pause for long periods of time, I tried several times to copy large folders across and everytime I came back a few hours late, would see the Error 36 message.

     

    I tried to do individual copies and this seemed to work fine, but as soon as I tried to choose several files, I would keep getting this hanging issue, so would cancel and try again.

     

    In the end I have given up using my Macbook Air with the thunderbolt port and gone to my trusty old 2007 iMac to transfer via USB2 instead.

     

    It's been going for a good while now, copied 38GB of 177GB and no errors are showing, also the amount of data copied is a constant stream slowly increasing, unlike on my Macbook Air that would scream along and then just hang and hang and hang.

     

    I have an appointment with Genius Bar tomorrow over error with Instant Hotspot not working, so will be sure to put this slow copy issue to them also. If they can tell me anything will update on here for you.

  • by baka26,

    baka26 baka26 Feb 15, 2015 7:00 AM in response to TheMayneEvent
    Level 1 (0 points)
    Feb 15, 2015 7:00 AM in response to TheMayneEvent

    Gone through previous post, and basically my problem is the roughly the same.

    MBP with Yosemite 10.10.2 connecte via firewire with external 2TB HDD.   Error 36 occurs when copying files from 2TB ext HDD to a locally networked NAS via WIFI.  I verified copying any files / folders from MBP's internal HDD to the same NAS is smooth without any hiccups.

    Tried unplugged all USD devices to the MBP and changing different cables with the ext HDD, but the error persists.

     

    APPLE please rectify this issue ASAP as this is very annoying and disturbing.

  • by ajaszek,

    ajaszek ajaszek Feb 16, 2015 7:53 AM in response to scott252
    Level 1 (0 points)
    Feb 16, 2015 7:53 AM in response to scott252

    Hi scott252,

     

    with the help of Lacie support I isolated the problem to be on the Thunderbolt port as the USB3 cable worked without error. 

     

    I sent the drive to Lacie and they ran HDTunes, flashed and tested the ports then returned the drive to me unrepaired.  I was disappointed they did not use a Mac to try to reproduce the issue.  Lacie then sent out a new drive and it works fine. 

     

    When I get time I will look into how to find more information in the console logs on Error 36. 

  • by Tangier Clarke1,

    Tangier Clarke1 Tangier Clarke1 Feb 16, 2015 4:29 PM in response to TheMayneEvent
    Level 2 (279 points)
    Desktops
    Feb 16, 2015 4:29 PM in response to TheMayneEvent

    I've had this issue for a while as well since Mavericks came out copying to our Mac Mini OS X server.  Here's what I've come across as various unsuccessful solutions:

     

    - repair permissions: didn't do anything

    - check drive status: drive(s) are fine, no solution here

    - your drive(s) must be failing: nope - had the issue with a new Late 2013) Mac Pro with external RAID, used a second new Mac Pro and tried copying to the same OS X Server with totally new hard drives and the same issue persists.

    - copy using Terminal.app and invoking a "dot_clean" command: this is crazy to have to do this every time you want to copy

    - use DeTox My Mac: don't want to pay for fixing an OS that should work right in this regard.

     

    I have no solution and it's baffling.  It all started for us when Mavericks came out and has persisted ever since.

     

    On top of that search broke when Mavericks came out so now Spotlight on local and remote volumes is unreliable.

     

    Two key things that have really negatively affected out productivity.

  • by L1212,

    L1212 L1212 Jun 2, 2015 11:47 AM in response to Tangier Clarke1
    Level 1 (0 points)
    Jun 2, 2015 11:47 AM in response to Tangier Clarke1

    Hey Tangier,

     

    I am running into this same problem too, with music and video files on the drive in question. Did you ever find a solution to the problem. I have done the verify and repair on the drive. I have not done the cot_clean as its just a band aid, I don't want to have to do that every single time I download an album from iTunes and it gets all messed up. Any help would be great

  • by todd231,

    todd231 todd231 Aug 3, 2016 10:57 AM in response to TheMayneEvent
    Level 1 (4 points)
    Aug 3, 2016 10:57 AM in response to TheMayneEvent

    I came across this same issues with a brand new Lacie 4tb drive and a Mac Pro running Yosemite. 

    When I was transferring files from a glyph drive to my new lacie I was inconsistently getting -36 and -50 errors at sporadic times.  Sometimes a folder would give me the error then I would try again and it was fine.  The drive seems to be working ok although it does keep giving me a disk not ejected properly prompt even though it is still plugged in. 

     

    Anyway..the workaround I found although not ideal because it was time consuming:

     

    I noticed that certain folders that had sub folders in them were the ones causing the problems.  If I opened the main folder then transferred the sub folders individually the transferred much smoother.  So, that got me thru it but much slower than I would have liked.

     

    Please let me know if anyone else has solutions.
    Thanks

    Todd

  • by Alissymccracken,

    Alissymccracken Alissymccracken Sep 12, 2016 1:34 AM in response to TheMayneEvent
    Level 1 (8 points)
    Desktops
    Sep 12, 2016 1:34 AM in response to TheMayneEvent

    Hi,

     

    After years of using Seagate hard drives on my iMac i've unfortunately ran into this problem too now. It's happening with all three of my external drives and two of my WD drives too. They all have different content so it's unlikely the drives are failing or even files are causing this. I've done a lot of reading about this because it's a nasty little problem that we shouldn't have to deal with.

    Some people say it's a fault in Finder, some people say that changing settings on your sharing folders work. Can anyone confirm this? has anyone actually fully fixed this?

    I've been trying the drives on my MBP 2012 running Yosemite 10.10.4 and the drives seem to be working. I've even verified the disks and it says they're okay. But on my iMac, that was a different story, it wouldn't let me check the drives health, and it wouldn't even let me eject them properly anymore. I don't know whats going on, but this problem has only been going on for four days for me so far and it's really causing some serious anger inside me. I would be grateful for any fixes, tips or just knowing people are going through the same thing. I hope if this IS an Apple bug that it gets solved ASAP.

Page 1 Next