Copying To Network Drive Error Code 36
Contents |
completely halts the copy or move process in the OS X Finder. The full error is
Mac Error Code 36 Network Drive
usually read as "The Finder can't complete the operation because some data error code 36 copying files in "FileName" can't be read or written. (Error code -36)". The filename is sometimes .DS_Store, but it can happen
Error Code 36 When Copying Iphoto Library
with just about any file. If you run into Error Code -36 on a Mac, there's usually a really simple solution thanks to a handy command line tool called "dot_clean". If finder copy error code 36 you've never heard of dot_clean, you're certainly not alone, and the manual page for the command explains that it "merges ._* files with corresponding native files." which may not sound like much to the casual user, but given the oft cause of Error 36 are files prefixed with a dot, that can be exactly what you need to do. How to Resolve Error external hard drive error code 36 36 in OS X Finder with dot_clean To use dot_clean, you'll want to point it at the directory which is being copied and throwing the Error Code 36, the basics look like this: Launch the Terminal (found in /Applications/Utilities/ or with Spotlight) At the command prompt, type: dot_clean /Path/To/Directory/With/Problem/ When dot_clean is finished, attempt the file copy again and it should succeed with no error code For example, if copying ~/Documents/FileBackups/ is the problematic directory, use: dot_clean ~/Documents/FileBackups/ That should be all that is necessary to resolve the issue, just be sure to attempt the file/directory transfer immediately after the command is run. Technically you could point dot_clean at an entire volume but that's probably not necessary unless the -36 error is continuously triggered in Finder when trying to backup an entire drive manually. If the problem is recurrent and you get it constantly when trying to copy files to and from a networked Mac, a network share, external drive of some sort, or to and from a Windows computer, you can also try to delete all .DS_Store files on a Mac using the command line, whi
-36 and other I/O errors in OS X 2 Replies While rare, in OS X you may run across a problem where upon copying or accessing files and folders, the system
Error Code 36 Mac External Drive
will stop and display an warning that simply states the operation could not the finder can't complete error code 36 be completed because of an error. For the most part when this occurs, you will see error code -36 displayed,
The Finder Can't Complete The Operation Because Some Data In Error Code 36
but it can also include other numbers. If these happen, there may be a quick fix you can try, but generally they indicate unknown low level problems with your Mac. If you run http://osxdaily.com/2015/02/21/fix-error-code-36-finder-mac-os-x/ into this error, first check whether or not it occurs randomly, or only when you attempt to manage specific files, especially files that you might have had around for a long time as you migrated through different Macs and upgraded them to newer versions of OS X. The HFS+ filesystem format that Apple uses for OS X supports two modes of saving data for files: a data https://www.macissues.com/2015/05/25/what-to-do-about-error-36-and-other-io-errors-in-os-x/ fork, and a resource fork. Classically these had specific purposes, and while both can technically be accessed, in OS X Apple gave up the use of the resource fork and almost exclusively uses the data fork for file. However, support for the resource fork still exists and some files use them. Some filesystems that you can use with your Mac (such as FAT32 for Windows compatibility) do not support the resource fork, so to handle these and manage files OS X will split the data and resource forks, keeping the data fork for files and reserving the resource fork as a file named with a "._" prefix so it remains hidden. However, this may cause some problems with accessing the file as the system needs to manage two of them. If this is the case, then the errors you experience will only show up at specific times, such as when attempting to copy a certain file or folder. To fix this, you can use a tool in OS X to merge and otherwise manage these hidden "._" files (aka "AppleDouble" or "dot-underscore" files): Open the OS X Terminal. Type "dot_clean -n" followed by a single space. Drag
running 10.6.2, are experiencing a widespread problem related to copying directories to Windows-formatted volumes in Finder. I recently got a new USB flash drive and ran into a serious issue as I was http://www.macyourself.com/2010/01/07/solution-to-finder-error-code-36-in-10-6-when-copying-folders/ loading it with data. Some of the files I temporarily copied to my Mac's http://apple.stackexchange.com/questions/216696/finder-reports-error-code-36-when-copying-some-files Desktop from my old flash drive would not successfully copy to the new one. Both flash drives were formatted as FAT volumes (known as MS-DOS in Disk Utility) and only files that resided in a folder seemed to be affected. I could copy the files individually just fine, but not an entire folder at once. Finder would have error code none of it. If you're running Mac OS X 10.6.2 and have a MS-DOS/FAT-formatted disk handy, here is a quick way to replicate the problem. Create a new folder on the MS-DOS drive with Finder and copy any file from your Mac right into that folder. It could be anything… I used a random image on my Desktop, for example. Copy the entire folder from the MS-DOS drive to your Mac's Desktop. error code 36 Copy the folder from your Desktop right back onto the MS-DOS drive. Boom! You just got slapped with the following error, didn't you? "The Finder can't complete the operation because some data can't be read or written. (Error code -36)." Every time, without fail, this has occurred on all Snow Leopard machines I've tried. Sure, you can reformat the USB flash drive to Mac OS Extended to get around the error, but that kills Windows compatibility. Instead, let's dig deeper. It turns out the problem stems from the "dot-underscore" companion files that Mac OS X's HFS+ filesystem creates for files when they get moved to FAT16 or FAT32 volumes. These hidden files – which start with "._" followed by the original filename – contain extra information to go along with the main file's data. Apparently things get screwy in 10.6.2 and don't go well when folders from a Windows-compatible volume get moved to a Mac and then back again. The dreaded "Error code -36" message is the result. If you run into this horribly inconvenient bug, there is a temporary solution until Apple gets their act together. It involves stripping the main file of its unneeded dot-underscore buddy. Don't worry, you won't lose anything important in the process. Here's what you can do: Launch Te
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Ask Different Questions Tags Users Badges Unanswered Ask Question _ Ask Different is a question and answer site for power users of Apple hardware and software. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Finder reports error code -36 when copying some files up vote 1 down vote favorite I have a 4.6GB file on my hard drive. Today when I tried to copy it to another machine through network, I got the following error message from Finder halfway through the copy: The Finder can't complete the operation because some data in "(name of my file)" can't be read or written. (Error code -36) In addition to copying that file to another machine through network, I also did the following: checked some other files on my hard drive and found another one with the same problem; tried copying those files to another folder on the same hard drive, and got the same error; tried to open one of those files, which was a .dmg file, by double clicking on its icon, and got a different message when Finder tried to verify it, saying there was an input/output error. Then I tried the following to fix the problem: Disk Utility: I ran Verify Disk and it said my disk is OK; fsck -fy: it also said my disk is OK; dot_clean as suggested here: didn't work, the error remained. So what else can I try? Is this an indication that my hard drive is failing? osx mac finder hard-drive error share|improve this question edited Nov 22 '15 at 8:42 asked Nov 22 '15 at 7:38 ycsun 1063 1 'read or written' doesn't actually give any indication of which end of the transaction is failing. What is the format of the drive you are copying to, & over what mechanism? FAT32, for example, has a maximum file size of 4GB, FAT16 only 2GB. –Tetsujin Nov 22 '15 at 7:52 I tried to copy the file again. Instead of copying to another machine, this time I copied it to a different folder on the same hard drive, and Finder showed the error again. So I don't think it's about FAT32 or FAT 16. Thanks for your suggestion anyway, I'll update my post. –ycsun Nov 22 '15 at 8:02 So, are you saying that it could be the file that is damaged? Have you been able to open the files no problem? –fabrice d Nov 22 '15 at 8:22 @fabrice: Yes, it appears that the file