sp1te

Q: Error code -36

Just updated to 10.9.2 on both my imac and my mac mini server.

 

I share a drive on my mac mini server using server's file sharing, and I mount it with SMB on my iMac. Well I should say prior to 10.9.2 I did now everytime I do and I move a file to the mounted drive from my imac to my server I get this error.

 

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

 

As far as I can tell the files copy perfectly and if I mount the drive with afp it works just fine as well same drive mounted over SMB well same error. Anyone else notice anything like this? Id like to use SMB as it seems to work a little faster.

 

The drive in question is a drobo but it seems to affect any drive mounted with SMB after the update.

iMac (27-inch Mid 2011), OS X Mountain Lion (10.8.2)

Posted on Feb 26, 2014 9:49 PM

Close

Q: Error code -36

  • All replies
  • Helpful answers

first Previous Page 3 of 3
  • by michalmaria,

    michalmaria michalmaria Mar 22, 2014 2:16 AM in response to michalmaria
    Level 1 (0 points)
    Mar 22, 2014 2:16 AM in response to michalmaria

    Just FYI: I was contacted by Apple again, they asked for various pieces of information, like sysdiagnose output and a TCP dump for the copy operation. They are definitely working on that, but of course nobody knows when the fix will appear. In the meantime, I'll stick to my workaround.

  • by FlyingLemming,

    FlyingLemming FlyingLemming Mar 23, 2014 5:06 AM in response to michalmaria
    Level 1 (0 points)
    Mar 23, 2014 5:06 AM in response to michalmaria

    Thanks for the info, that sounds promising. :-)

     

    By now I found the perfect solution/workaround for me, which allows to force Mac OS to use the old SMB1 implementation all the time. Credit goes to Michael Larsen at "Cammodude's Blog" (http://cammodude.blogspot.de/2013/10/os-x-109-mavericks-workaround-for-smb.html).

     

    To sum it up: You have to create a file nsmb.conf within ~/Library/Preferences/ with the following content:

    [default]

    smb_net=smb1_only

     

    After a reboot all smb connections are now handled by the legacy smb version and therefor work quite fine. In his blog Michael Larsen states that this implementation might be slower than Apple's SMB2. While I did not perform any speed tests, I did not feel any difference on a wifi connection from a rMBP to my Mac mini server.

     

    As soon as Apple finally fixes this issue, you just have to delete the mentioned file and reboot the machine.

  • by Larry Goldman,

    Larry Goldman Larry Goldman Mar 23, 2014 6:38 PM in response to FlyingLemming
    Level 1 (9 points)
    Servers Enterprise
    Mar 23, 2014 6:38 PM in response to FlyingLemming

    A client-side patch is not really feasible when several far-flung machines are in play.

     

    I can confirm that the Error Code -36 appears when using 10.9.2 on the client, with the OS X server running 10.9.2/Server 3.1, for Finder-sidebar (smb) mounts. afp:// mounts work OK.

     

    The problem does not appear when peer-to-peer OS X desktop (smb) file sharing is used.

  • by FlyingLemming,

    FlyingLemming FlyingLemming Mar 24, 2014 1:51 AM in response to FlyingLemming
    Level 1 (0 points)
    Mar 24, 2014 1:51 AM in response to FlyingLemming

    CAUTION: There has been a little typing error in my posting of the workaround. The correct lines for nsmb.conf would be:

    [default]

    smb_neg=smb1_only

     

    Mind the "neg" instead of "net" on the second line...

  • by Smokinjoe17,

    Smokinjoe17 Smokinjoe17 Apr 25, 2014 2:35 PM in response to sp1te
    Level 1 (0 points)
    Apr 25, 2014 2:35 PM in response to sp1te

    Just adding a +1 to a client of mine who is seeing this issue as well. We are working around it for now. Can't believe a bug like this has been our there for that long.

  • by Patrick Savelberg (Private),Helpful

    Patrick Savelberg (Private) Patrick Savelberg (Private) May 8, 2014 8:30 AM in response to sp1te
    Level 1 (113 points)
    Servers Enterprise
    May 8, 2014 8:30 AM in response to sp1te

    We have a reseach situation running because of this problem. We did not have any problems any more with the

    10.9.3D62 version (ore all versions before that) We now can safly copy file swithout any -36 eroros or strange slowdowns on SMB and AFP. No speed diffrenece.

     

    We tested Client 10.9.3 -> Server 10.9.3 and Client 10.9.2  -> Server 10.9.3

     

    Hope the update is out soon !!!

  • by Bryan Schramm,

    Bryan Schramm Bryan Schramm May 9, 2014 9:39 PM in response to Patrick Savelberg (Private)
    Level 1 (15 points)
    May 9, 2014 9:39 PM in response to Patrick Savelberg (Private)

    Thanks Patrick!  Hopefully this makes it into the final release.  I think I'll "do the right thing", and not deploy the developer version on my production system, and rather, wait for the final.  Thanks again!

  • by k6rtm,

    k6rtm k6rtm May 11, 2014 11:38 AM in response to FlyingLemming
    Level 1 (0 points)
    May 11, 2014 11:38 AM in response to FlyingLemming

    The patch forcing smb1 connects did it for me -- I only have a few machines and they're all local.

     

    Still, this is a vast pain.

     

    Many thanks to Patrick and Michael!

  • by k6rtm,

    k6rtm k6rtm May 14, 2014 8:32 PM in response to k6rtm
    Level 1 (0 points)
    May 14, 2014 8:32 PM in response to k6rtm

    This problem is well recognized. If you don't feel like diving into terminal, you can do it with an app:

     

    http://www.macparc.ch/apps/SMBconf/

     

    lets you force SMB1, or allow SMB2 to be used.

  • by k6rtm,

    k6rtm k6rtm May 15, 2014 12:36 PM in response to k6rtm
    Level 1 (0 points)
    May 15, 2014 12:36 PM in response to k6rtm

    Installed 10.9.3 update (released 15 May). After making backups, installed on server, and two client systems.

     

    Using SMB2 on clients still generates -36 error when trying to copy files to server.

     

    Switching back to SMB1 on clients eliminates the -36 error.

  • by Patrick Savelberg (Private),

    Patrick Savelberg (Private) Patrick Savelberg (Private) May 15, 2014 12:49 PM in response to k6rtm
    Level 1 (113 points)
    Servers Enterprise
    May 15, 2014 12:49 PM in response to k6rtm

    Will try it after update. I see this is D65. I had it also on one update, check if you don't have deleted users / groups in your ACL list of your share,

  • by ad6922,

    ad6922 ad6922 Aug 26, 2014 2:50 PM in response to sp1te
    Level 1 (0 points)
    Aug 26, 2014 2:50 PM in response to sp1te

    I have the same problem as stated over here.

     

    When copying to my QNAP NAS error 36 is there all the time.

    Copying takes place from my Imac - 10.9.4

     

    Unfortunately it has the problem with afp, smb1, smb2 and cifs.

     

    Any one any other ideas as it seem that the solutions in this thread are not helping my case.

  • by TomRodant,

    TomRodant TomRodant Sep 21, 2014 4:14 PM in response to ad6922
    Level 1 (0 points)
    Sep 21, 2014 4:14 PM in response to ad6922

    Setting SMB1.0 on the NAS did the trick for me.

     

    Its in Control panel, Network services, Advanced, Highest SMB version. I have a QNAP 469L, Running software 4.1. and is on OSX 10.9.5.

  • by chintamaniv,

    chintamaniv chintamaniv Jun 14, 2016 1:22 AM in response to FlyingLemming
    Level 1 (4 points)
    Jun 14, 2016 1:22 AM in response to FlyingLemming

    This solution worked  100% for me. Thanks a million.

first Previous Page 3 of 3