BackUp plan/the finder can't copy files

I am trying to backup some files manually from one hd to another, and everytime i do this i get this error message :
The finder cannot complete the operation because some data in "any file.psd" could not be read or written. (Error code -36)
what i found extremely strange is that thoses files work perfectly well with the application that produced them, and it does happen with all kind of files: video, photo, text...
Does this mean my finder is corrupted? and what can i do about it, those files are extremly important to me, as it is my working files. i would need to back tem up before i do anything on the finder
G4 mirrored door dual boot Mac OS X (10.4.3)

Well it turns out there was a bad firewire port on the external drive. Now if I can just keep it from losing contact with my trackball when it sleeps.
Some people say to never let the Mac sleep, but others say you have to leave it on at night so it can do some Unix maintenance. Anybody know what the answer is?

Similar Messages

Trying to copy iPhoto Library to external hard drive for backup. Error message: The Finder can't complete the operation because some data in "iPhoto Library" can't be read or written (Error code -36).

Trying to copy iPhoto Library to external hard drive for backup. Error message: The Finder can't complete the operation because some data in "iPhoto Library" can't be read or written (Error code -36).

That code is
-36
ioErr
I/O error (bummers)
Make sure the EHD is formatted OS X Extended (journaled) and run Disk Utilty on the EHD and repair the disk. If that fails to help I'd try the following:
Using iPhoto Library Manager to Rebuild Your iPhoto Library
Download iPhoto Library Manager and launch.
Click on the Add Library button,
navigate to your Home/Pictures folder and select your iPhoto Library folder.
Now that the library is listed in the left hand pane of iPLM, click on your library and go to the Library ➙ Rebuild Library menu option
In the next window name the new library and select the external HD as the location of the newly rebild library.
Click on the Create button.
Note 1: This creates a new library based on the LIbraryData.xml file in the library and will recover Events, Albums, keywords, titles and comments. However, books, calendars, cards and slideshows will be lost.
Note 2: Your current library will be left untouched for further attempts at a fix if so desired.
OT

Thunderbolt file copy - the Finder can't complete the operation because some data in can't be read or written.

I have a Promisse 4 disk Thundebolt enclosure. To this I did install 4 new 2TB Samsung disks. (it had 512GB disks before). After the disks were replaced a randomly get messages like "the Finder can’t complete the operation because some data in can’t be read or written". If I retry it sometimes work - sometimes dont work.
To close down on the problem I have mounted one disk as a single partition, and it still happen. Then I take the disk out, mount it in an USB enclosure and I have no problem. (I have more than once written the disk completly full using USB without any problem).
To me it seems like OSX has some weird problem with these big disks on thunderbolt. Any ideas?

Pretty sure it`s not the promise. It could of course be the FW in the Promise having problem with 2TB disks or the Samsung brand in some way.
Had 4 Toshiba disks in it until quite recently. No problem. They were running in RAID 0 for about 6 months.
I have right now 2 x 2TB disks in a RAID 0 in it with no problem. So - I am down two 2 possible answers
a) OSX don´t handle copy correct (or actually finder - have not tested cp from command line)
b) I have been unlucky and got 2 similar disks that have the same problem (2 of 4 disks - all brand new 3 weeks ago)
The one thing a find most annoying is OSX lack of telling what`s going on. The "Failed to read or write" error is stupid - tell me what`s the problem. Like "could not write to block XXXX". An os is also supposed to re-allocate bad blocks. However I see no way in OSX to see number of bad blocks etc. Is this possible?
When googling the error -36 it seems like this is something that has been troubling OSX for some time, but not that many users that have problems after 10.7 was released.
I think what I will do is to send in the disk for replacement - that will at least give some answers.

The Finder can't complete the operation because some data in "FILE NAME" can't be read or writen. (Error code -36)

I have a RAID that my Mac says is damaged. It does mount, so I want to copy as much of the data as I can. I tried SuperDuper!, but it crashed (or gave me error and stopped). I tried copying and pasting entire drive (1.75TB) but it stopped with this error, and same error happens with some of the files when I try to copy and paste (Drag and Drop) them individually.
I get this error: The Finder can't complete the operation because some data in "FILE NAME" can't be read or writen. (Error code -36)

Well, in pure Apple File System talk... -36 ioErr I/O error (bummers)
Not very helpful, but generally means a Drive quit being Readable or Writable since starting the operation...
http://fuzzy.wordpress.com/2006/12/10/ioerror-36/
If Disk Utility or fsck should fail to repair it, your best bet is DiskWarrior from Alsoft, you'll need the CD to boot from if you don't have another boot drive...
http://www.alsoft.com/DiskWarrior/
Might try the free trial of my favorite, Tri-Backup, it does a better copy/clone job in that it usually doesn't quit copying at every error, & has a nice log afterwards to try certain files agin if you wish....
http://www.tri-edre.com/english/products/tribackup.html

Time Machine will not complete a system backup and terminates with "Unable to complete backup. An error occurred while copying files to the backup volume. This follows a problem when Time machne terminated when the volume was almost full.

On 11/1/2011, Time Machine (TM) terminated with an error message I did not record. I noted that the drive was full and decided to do a separate complete bootable system backup using Carbon Copy Clone (CCC), before clearing the TM volume and trying to start it over clean. Part way through the full system backup CCC put up a message that there was a Physical Problem "Library/Application Support/Techtool Protection/McIntosh HD/Directory Backup 2011-11-01-16-28-16". That was about the time that TM malfunctioned, so I assumed they were related. After starting CCC over a couple of times, and getting the same error message, I let it go through to completion of the backup, which took three or four hours. I then ran tests using Disk Utility and verified that there was nothing physically wrong with both the internal hard drive and the TM volume. I also erased and reformatted the TM volume. However, every time I started Time Machine, it would record a few GB and terminate with "Unable to complete backup. An error occurred while copying files to the backup volume". I restarted the computer with no change in results. Note that prior to starting the CCC backup, I "Repaired Permissions", "zapped the PRAM" and "re-set the SMC", hoping to have a clean bootable system on the backup. I ran Techtool and no problems were found.
I'm running this on an Intel iMac under 10.5.8 and recording to a 500GB My Passport drive. My hard drive is only about half full at 246 GB. My assessment is that something happened at 16-28-16 on 11/1/2001 to screwup the Backup Directory in the file at "Library/Application Support/Techtool Protection/McIntosh HD/Directory Backup 2011-11-01-16-28-16". My question is, how do I fix it?
I had just completed writing everything above here, explaining the problems I had been encountering for the past 24 hours. I had the Time Machine window standing open on the desktop where I could see it, having recentlycleared it after the last termination. As I was proofing what I had written, I looked at the window and noted that the clock had started a new run for a full back up, since all prior efforts had failed and the TM volume was empty. As I watched and waited for it to fail again, as it had been doing at about 13 GB, it kept going and going until it just finished a complete backup, about 4.5 hours later, with my having done nothing. Now my question would have to be - what could possiibly have happened to make it perform this way? It will be interesting to see if it continue to operate normally, or if the problem will return, in a later backup run.

jcm21 wrote:
CCC put up a message that there was a Physical Problem "Library/Application Support/Techtool Protection/McIntosh HD/Directory Backup 2011-11-01-16-28-16"
You should not keep those files for long, and probably shouldn't back them up (if you need them at all -- since you do regular backups, I'm doubtful just how worthwhile that feature is).
"Unable to complete backup. An error occurred while copying files to the backup volume".
One of Apple's maddeningly incomplete messages. Most likely, there's a problem with a file (quite possibly the one CCC didn't like). See #C3 in Time Machine - Troubleshooting for details and instructions on finding and fixing it.
If you continue running the Directory Protection app, be sure to exclude your Time Machine drive from it (as it will just take up lots of room, and won't help repair your backups if there's a problem); and exclude the folders it creates from being backed-up by Time Machine (as they'll create large backups, and you probably can't use the backed-up folders anyway), per #10 in Time Machine - Frequently Asked Questions.

Keep getting this message when trying to back up iMac to time Machine: Unable to complete backup. An error occurred while copying files to the backup volume.

Keep getting this message when trying to back up iMac to time Machine: Unable to complete backup. An error occurred while copying files to the backup volume. tried everything.

Pondini's Time Machine FAQ for help with TM problems. Also you can select Mac Help from the Finder's Help menu and search for "time machine" to locate articles on how to use TM. See also Mac 101- Time Machine.
Time Machine- Troubleshooting backup issues

Recent backups fail: "An error occurred while copying files to the volume."

I recently moved to a new place and set up Time Capsule as a bridge. Backups were working fine for the first couple days but then, out of the blue, I got a message that said the password I entered for Time Capsule was incorrect. I entered the correct password and hit OK. Time Machine was able to connect but now backups fail with this error: "Unable to complete backup. An error occurred while copying files to the backup volume."
Time Machine indicates it is "preparing backup" for a few minutes, then sits at "zero of __MB completed" for a long while, finally starts backing up and gets to the end but then fails. Console indicates "unexpected reply from backup server; ignored."
None of these attempts have fixes my problem:
--I have deleted my TC passwords in Keychain Access.
--I have tried downloading the latest Airport Utility and re-entering the TC disk's password in both Airport Utility and in Time Machine preferences.
--I have restarted my computer and unplugged & plugged back in TC.
My Internet connection works fine; TC's light is solid green. I can enter Time Machine to restore backups without a problem. The backups just fail every time now. Any ideas?

The problem really isn't the speed of the backup; it's done in 5-10 minutes, but each time it finishes, TM reports it has failed. I don't believe plugging it in overnight or letting TM try over and over will fix the problem. I've tried to manually start backups a number of times, and have let TM try to start and complete them on its own but they consistently fail.
It would be an awful shame if I had to delete my old backup--I bought the Time Capsule for the specific purpose of having backups that go back months and I don't want to lose what I've already backed up.

HT3275 Time Machine error. Unable to complete backup. An error occurred while copying files to the backup volume. Tried restarting, remounting external WD drive. Still cannot backup.

Time Machine quit backing up files. Bought a new WD external drive. Worked for awhile, then quit backing up. Tried restarting computer, remounting drive. Message: Time Machine Error. Unable to complete backup. An error occurred when copying files. Suggestions?

Thanks so very much for your help!! I'm boggled by it and now just about ready to dump the whole idea of Time Machine and backup using a cloning program. Maybe TM is only guaranteed to work well with Time Capsule these days?
Today there again was no backup. I did as you suggested, looked into Console. It showed many lines of "(Error) DiskStore: No block in wakeup" and also repeatedly "(Warning) DiskStore: Ignored bogus fetch...".
So I created a marker and attempted to initiate a backup, keeping Console open and refreshed. Here's what I got:
8/19/13 5:18:40.385 PM Console: Marker - Aug 19, 2013 5:18:40 PM
8/19/13 5:19:48.844 PM com.apple.backupd: Starting standard backup
8/19/13 5:20:00.484 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.484 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.484 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.507 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.507 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.507 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.508 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:38ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.510 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:40ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.511 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:41ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.511 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:41ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.511 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:41ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:20.000 PM kernel: USBF:          58091.976          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:20:51.000 PM kernel: USBF:          58122.985          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:21:22.000 PM kernel: USBF:          58153.992          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:21:53.000 PM kernel: USBF:          58185. 2          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:22:24.000 PM kernel: USBF:          58216. 14          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:22:55.000 PM kernel: USBF:          58247. 25          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:23:26.000 PM kernel: USBF:          58278. 41          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:23:57.000 PM kernel: USBF:          58309. 51          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:24:28.000 PM kernel: USBF:          58340. 59          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:24:59.000 PM kernel: USBF:          58371. 68          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:25:30.275 PM xpchelper: for uid: 501 -- timeout while waiting on FSEvents flush; clearing cache.
8/19/13 5:25:30.000 PM kernel: USBF:          58402. 82          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:26:01.000 PM kernel: USBF:          58433. 96          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:26:32.027 PM com.apple.backupd: Backing up to: /Volumes/TMBackups/Backups.backupdb
8/19/13 5:26:32.000 PM kernel: USBF:          58464.112          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:27:02.653 PM com.apple.backupd: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/TMBackups/Backups.backupdb/David‚Äôs iMac size:37
8/19/13 5:27:02.657 PM com.apple.backupd: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/TMBackups/Backups.backupdb/David‚Äôs iMac size:37
8/19/13 5:27:03.000 PM kernel: USBF:          58495.121          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:27:12.668 PM com.apple.backupd: Backup failed with error: 2
During this 9-minute timeframe Finder also was inoperative - according to Activity Monitor: "Not Responding".
I'm thinking it's the standalone Buffalo backup drive not waking up, and so everything comes to a screeching halt. Do you also think I should abandon TM and just do manual backups every day using a clone program?

Unable to complete backup. An error occurred while copying files to the...

Add me to the list of those with TIme Machine backup failures.
I am repeatedly getting the following error message:
"Unable to complete backup. An error occurred while copying files to the backup volume."
I do have work-around.
1. Open Time Machine Preferences... (from the Time Machine menu in the menu bar)
2. Change Disk...
3. Re-select the disk you are already using and select "Use for Backup"
4. Back Up Now (from the Time Machine menu in the menu bar)
The error eventually comes back, but following the above procedure keeps it at bay for a few days.
I have only had these errors since 10.5.3.

Mle,
Take a look at the following...
*_“Unable to Complete Backup. An Error Occurred While Copying Files to the Backup Volume.” (Console: “Error: (-43) copying”, “Copy stage failed with error:11”)_*
There are several reasons why this error message can appear. Consider each topic individually. If one does not resolve the issue, move on to the next one. The following topics have resolved this issue for others.
*If A Backup Is Interrupted* #
“If an interruption occurs, Time Machine will wait for a period of time to see if the Time Capsule becomes available again. After this time expires you will see a alert message stating "Time Machine Error. Unable to complete backup. An error occurred while copying files to the backup volume." In Time Machine preferences, the "Latest Backup:" field will state "Failed".” [http://support.apple.com/kb/HT1176]
You will need to reestablish communication with the Time Machine backup disk.
*Anti-Virus Software* #
Have you been running anti-virus software? xClav, Norton, Sophos, Macaffe etc... According to many posters in the forums this software can play havoc with Time Machines attempt to function properly.
*Firewire Devise Interferes with Time Machine Backups* #
If you are backing up to an external hard disk by means of firewire, do you happen to have another firewire device attached as well? An iSight camera or video recorder maybe? Sometimes additional firewire devises can interfere with the signal/power to the backup drive. Unplug it and attempt a backing up again.
*Corrupt File / Incorrect Permissions* #
One poster observed: “I searched my system logs and found a file that caused my connection to the TC to fail. I erased that file (after checking what it was - a temporary file connected to my Epson scanner) and tried again to back up for the first time. This time it worked, and in under 10 hours (I had been expecting about 20-24 hours, based on the data transfer speed).”
Initially this might be resolved without deleting the offending file. Simply use Disk Utility to “Repair Disk Permissions”. Or failing that, booting from the Mac OS X Installation DVD and running “Repair Disk” on the Mac’s internal hard disk. Now try backing up
Otherwise, you may need to track down the specific file causing Time Machine to choke.
Before attempting another backup, go into Applications --> Utilities --> and launch Console.
Under “LOG FILES” on the left select "system.log".
In the search field in the upper right, type in backupd. This is the process Time Machine uses to perform backups. By searching just for this process we'll isolate only Time Machine activities.
With the Console open, attempt another backup and note the time it starts and the time it stops. Often, the activities reported will identify the very file or event that caused the attempt to choke. (You can copy and paste the events for this backup attempt from the log into a post here and we may be able to tell you exactly what is happening.)
Once you determine which file or event it is, you can decide whether to move, delete, or modify certain things and then attempt another backup. For Instance, if the logs report something like this:
+Error: (-43) copying /Users/Home/Library/Application Support/Quicksilver/Actions.plist to+
+/Volumes/Backup HD/Backups.backupdb/My Mac Pro//Users/Home/Library/Application+
Support/Quicksilver
Then it’s telling you Time Machine is choking on the file labeled Actions.plist and it’s having trouble copying to the backup disk.
On your computer, Navigate to that file ( Actions.plist ) and move it to the Trash, but DON’T empty it yet. Now try backing up again. If it succeeds, you can launch Time Machine and go back 24-48 hours and restore a copy of Actions.plist and replace it. Then empty trash.
*Partition Scheme/Formatting Issue*
This KB article explains one reason you may be seeing that error message [http://support.apple.com/kb/TS1550]. It's a partition scheme issue. Time Machine is incompatible with disks partitioned as Master Boot Record (MBR). Unfortunately, this describes nearly every hard drive you can buy because MBR is a Windows partition scheme. You will likely need to repartition the drive and start again. (Naturally, this DOES NOT apply to Apples’ Time Capsule.)
One article on Time Machine made this observation: “Virtually everybody will have to open Disk Utility and repartition the disk as APM or GUID. It doesn't really matter which one because the Time Machine disk will not be bootable anyway. APM allows a disk to boot a PowerPC, GUID allows the disk to boot an Intel processor but both are easily digestible by Time Machine on either kind of processor.” (http://www.girr.org/mac_stuff/backups.html)
Once the external hard disk is repartitioned, select it again in Time Machine preferences and use it for your backups.
Let us know if any of the suggestions above resolved your issue.
Cheers!

My time machine always stops at some point... It always shows this message: "Time Machine Error. Unable to complete backup. An error occurred while copying files to the backup volume.

My time machine always stops at some point... It always shows this message: "Time Machine Error. Unable to complete backup. An error occurred while copying files to the backup volume. I have tried everything and even did time machine in safe boot as told by an apple suppoprt advisor. still the same error after 16gb

If you have more than one user account, these instructions must be carried out as an administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Enter the word "Starting" (without the quotes) in the String Matching text field. You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard." Note the timestamp of the last such message that corresponds to a failed backup. Now
CLEAR THE WORD "Starting" FROM THE TEXT FIELD
so that all messages are showning, and scroll back in the log to the time you noted. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them (command-C) to the Clipboard. Paste (command-V) into a reply to this message.
If all you see are messages that contain the word "Starting," you didn't clear the text field.
If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.
When posting a log extract, be selective. Don't post more than is requested.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Some personal information, such as the names of your files, may be included — anonymize before posting.

Can't copy file to network drive as "The operation can't be completed because the [Filename] is in use

Following upgrade to Yosemite I now can't copy files from iMac to my network HDD in external media center. I have iMac connected by wi-fi to airport extreme and media center connected to airport extreme by cable. I can see the HDD as a network drive on my iMac and can initiate the copy but right when copy process is finished I see "The operation can’t be completed because the [Filename] is in use". I am trying to copy different media files downloaded from internet which are not used by any program and stored on my hard drive. I actually can copy small files of 1mb and it works but anything above 20mb is halted. I can also move/copy/delete the file on iMac. Cant understand the nature of the problem. I tried to format external HDD as EXT2/EXT3/NTFS but same outcome.
OS X Yosemite 10.10.3 | iMac late 2009 | Apple Airport Extreme | Dune HD Base 3D mediacenter

Have you tried a restart or logging out/in?
Some more ideas.
Re: The operation can’t be completed because the item “ " is in use.

While transferring several files to the G-Raid, the G-Raid device locks up with the following warnings: "The Finder can't complete the operation because some data in (whatever file) can't be read or written (Error code - 36)."

While transferring several files to the G-Raid, the G-Raid device locks up with the following warnings: "The Finder can't complete the operation because some data in (whatever file) can't be read or written (Error code - 36).” NOt sure this is a G-Raid problem, can anyone help?

This is likely a problem with the drive itself. This error indicates unspecified I/O errors with the drive, which can be from a hardware fault, or a formatting issue. If the drive has valuable data on it, then try connecting it to another PC to get the data off, and then try fully partitioning and formatting the drive with Disk Utility. If this corrects the error then you should be able to use the drive again as it was likely a formatting issue, but if the problem continues then it is likely a hardware fault and the best solution is to be safe and replace the drive.

HT3275 I keep getting the "Unable to complete backup. An error occurred while copying files to backup volume. The solution on the website is try try again. Its been trying for 5 days now. Now what? Obviously something else needs to be done.

I'm using an airport extreme and I keep getting the "Unable to complete backup. An error occurred while copying files to backup volume. The solution on the website is try try again. Its been trying for 5 days now. Now what? Obviously something else needs to be done.

Verify the backup.
Is this TM you are using? TM to airport extreme connected hard disk are known to be fragile at best.
A5 http://pondini.org/TM/Troubleshooting.html
make sure the disk is available and online..
But if it is not working.. then you will have to wipe and start again.
http://pondini.org/TM/Airport.html
If this is not TM then also verify the source disk.

HT1578 I have found that I can't access the contents of the encrypted disk in time machine backups. The Finder window displays a grayed-out icon representing the disk. Can this be remedied?

I have found that I can't access the contents of the encrypted disk in time machine backups. The Finder window displays a grayed-out icon representing the disk. Can this be remedied?

Time Machine error: Apple Support Communities
OSStatus 5 when trying to use Lion...: Apple Support Communities

Hi guys, an empty folder is stuck in my trash & I get this message: "The Finder can't complete the operation because some data in the folder can't be read or written. (Error code -36). It won't shift no matter how I try to Secure Empty trash. Any ideas?

Hi guys, an empty folder is stuck in my trash & I get this message: "The Finder can’t complete the operation because some data in the folder can’t be read or written. (Error code -36). It won't shift no matter how I try to Secure Empty trash. Any ideas?

The Time Machines Backup is formated as Mac OS Extended (Case Sensitive, Journaled), my mac is formated as Mac OS Extended (Journaled).
The names on the file are all Uppercase
When I try to copy the Aperture file, it copies about 70% of the file (it's about 33GB in size), and halfway through I get this error.
I'm able to copy 99.99% of all of the images if I open the Aperture Folder using the "show package contents" under the backups using finder (Time Machine Backups>Backups.backupdb>CQ Macbook Air>2012-04-30-070933>HD.....>Pictures>Aperture Library). The only file I can't copy is that picture, which I'm totally ok with deleting, but Finder won't delete it for me. If nothing else works, I could copy the individual masters and re-create the folders, however I'd hate to do this as I would have to go through 10,000+ pics

BackUp plan/the finder can't copy files

Similar Messages

Maybe you are looking for