Time Machine just stopped working, Disk Repair & Read Only errors

So my TM backups have been running fine for at least six months now.
Today I started to get this error:
"Disk Repair
The disk "xxxxxx" was not repairable by this computer. It is being made available to you with limited functionality. You must back up your data and reformat the disk as soon as possible."
followed by
"Time Machine Error
The backup volume is read only.
To select a different volume, open System Preferences and choose Time Machine"
I've searched high and low for a solution to no avail.
Here's what I've tried so far.
Attached disk to iMac, repaired the disk. It now verifies with no errors.
Changed permissions on the disk to 644 through terminal as per an Apple article.
Rebooted iMac several times, zapped PRAM.
Anyone have any ideas as to why this is suddenly happening? I would really hate to have to reformat the disk and start from scratch. This is very frustrating, I've changed nothing.
Here's the log from Time Machine Buddy:
Starting standard backup
Disk image /Volumes/FreeAgent Drive/Thomas Torrillo’s iMac_002332917af9.sparsebundle mounted at: /Volumes/Backup of Thomas Torrillo’s iMac
Backing up to: /Volumes/Backup of Thomas Torrillo’s iMac/Backups.backupdb
The target volume is read-only.
Backup failed with error: The target volume is read-only.
Ejected Time Machine disk image.
Message was edited by: Tom Torrillo (added log info)

See if this helps:
What to do if Time Machine reports you don't have permission
This was posted in the Apple Discussions by V.K. I have only modified it slightly to be more generic.
The problem seems to be that 10.5.6 changes permissions on a file so that even the root user doesn't have write peivileges. I have no idea why they did this. The workaround suggested in [an]other post will probably work, too, but i did something less drastic. Instead of deleting the file I changed permissions on it, and it worked just fine. An added benefit is that the permission change seems to stick, so you don't have to delete the file every time you change a drive.
[Open the Terminal application in your Utilities folder. At the prompt [enter] the following command:
sudo chmod 644 /volumes/"TM drive name"/.xxxxxxxxxxxx
The name of the file .xxxxxxxxxxxx is based on the MAC address of your computer and will be different for every computer. Put the name of the TM drive in the above and keep the quotes.
You'll have to enter your admin password (which you won't see) which is normal.
This was edited by Kappy just for cleanup.
Enable Finder to Show Invisible Files and Folders
Open the Terminal application in your Utilities folder. At the prompt enter or paste the following command line then press RETURN.
defaults write com.apple.finder AppleShowAllFiles TRUE
To turn off the display of invisible files and folders enter or paste the following command line and press RETURN.
defaults write com.apple.finder AppleShowAllFiles FALSE
Alternatively you can use one of the numerous third-party utilities such as TinkerTool or ShowHideInvisibleFiles - VersionTracker or MacUpdate.

Similar Messages

My time machine just stopped working. No power. I had it since 2011

I had my time machine for about 20 months, and it just stopped working. no power. I have a lot of backups on it. Anyone had the same issue? I read on some forums that it was reccurent, and that apple is not addressing this issue. Please help. Too expensive to just go in the trash.

Do you have any computer with current applecare?? If so apple will replace the TC as it is covered.
Less than 2years for a current TC.. that would be Gen3 or early Gen4 is a little bit short for these models.. mostly they do last to 3years now.
What is the A1xxx model number from the rubber foot?
Leave it to cool for several hours.. overnight.. and start it fresh after that..
Pay particular attention to everything..
The boot sequence should go something like this..
Power on.. green front led.. change to solid amber after a few seconds.
All the ethernet LEDS will flash green for a moment.
Front LED will start flashing amber and the hard disk will spin up.. place your hand on it to hear it spin up.
Other things happen and eventually if there are no errors the front led will go solid green... but flashing amber is fine.
Do you get any LED on at all?
Where in the world are you?

Since hard drive restore, backup gives Disk Repair, Read-only errors

Hi all -
After a hard drive crash last week, I restored the new HD using my historically reliable wireless Time Capsule (TC) with Time Machine (TM). But ever since, backups have ceased to work. Now, TM spins for about an hour before returning the following errors in sequence:
(1) DISK REPAIR: "The disk 'Backup of [my name] Macbook' was not repairable by this computer. It is being made available to you with limited functionality. You must back up your data and reformat the disk as soon as possible."
(2) TIME MACHINE ERROR: The backup volume is read only. To select a different volume, open System Preferences and choose Time Machine."
I very much doubt there is an actual problem with the TC disk itself; my wife's iBook G4 continues to backup to it without any problem whatsoever. Related threads have suggested:
a) doing clever things with Preferences, such as deleting the com.apple.TimeMachine.plist file and re-booting. However, for some reason (perhaps related to the source of the problem?) I have no such file...
b) using Disk Utility to re-format and/or re-partition (these terms mean little to me) the TC disk. But my Disk Utility doesn't see the TC. (Perhaps related, I no longer actually see the little backup disk icon on the desktop.) And as I've said, I doubt very much it's the TC disk itself that it is the problem.
I have of course tried re-booting everything, as well as un-mounting and re-mounting the TC: Computer, heal thyself! No luck.
Any guidance is appreciated...
(PS If there's a log file I should post that might help with diagnostics, just let me know where to find it.)

I have suffered the same error messages, but without a hard disk crash before it.
I copied the backup-file from the TC to a separate drive, erased the TC, re-installed it, copied the backup-file to the TC en re-initiated TM only to be welcomed with the 'The backup volume is read only'-message again.
Beats me why this happened. Most frustrating part, however, is that I am not able to restore from the backup-file. Any suggestions are highly appreciated!

HT2284 My Time Capsule just stopped working.

Thank you in advance for any help. My Time Capsule just stopped working and I do not get the 'Connection Failed' error message as the Time Capsule is not showing up in the finder window. The light continues to flash amber on the Time Capsule. I am using it with my iMac running Lion. Any help will be really appreciated.

This is just typical Lion.. reboot the TC.. if that doesn't work.. reboot the whole network from fully off.. in order.. modem.. router/TC.. clients. 2min gap between each.
If still has issues.. press reset on the TC and redo it.
Download a utility that has tool properties..
http://support.apple.com/kb/DL1482
Just ignore the toyland version in Lion.
Next time it happens go to disk page in the utility and hit disconnect all users..
C12 and C17 can suggest some other things.
http://pondini.org/TM/Troubleshooting.html

Why am I facing so many problem after upgrading to ios7, my phone hangs/stuck many times, applications just stop working and close themselves, battery drainage,Facebook and all applications don't work properly. What should I do? They punished me for upgra

I'm using iPhone 5
Why am I facing so many problem after upgrading to ios7, my phone hangs/stuck many times, applications just stop working and close themselves, battery drainage,Facebook and all applications don't work properly. What should I do? They punished me for upgrading to ios7. I now hate apple and I'm thing of getting samsung.

Basic troubleshooting
Reset
Restore with backup
Restore as new ( better )

HT3275 My Time Machine has stopped backing up and now it errors out everytime I make another attempt.

My Time Machine has stopped working and now errors out everytime I try to re-connect ?

What is the error.. ??
We cannot help much without details.
Look at the pondini troubleshooting.
http://pondini.org/TM/Troubleshooting.html
The vast majority of issues are C12 or C17.. especially with ML.. which rather than fixing issues left over from Lion exacerbated them.

So my first iPod 4th generation charger just stopped working and I've only had it for about 2 months! Please help!!!!

My iPod touch 4th generation charger just stopped working and I've only had it for about 2 or 3 months. Please help!!!

Then it should still be under warranty, so make an appointment at your local apple store and have them take a look at it.
If that's not a possibility and you want to troubleshoot, what do you mean by 'just stopped working'? What were you doing? Maybe some more info could help with troubleshooting.

HT4628 The time machine has stopped working and I get this message about every 20 minutes while I am work. This backup is too large for the backup disk. The backup requires 104.9 MB but only 38.4 MB are available.

Has any found a resolution for this problem?

wittsjk wrote:
Can I use this external drive with another one? Or do I get rid of this one and just purchase one that is twice as big as the internal drive?
I would reccommend buying another one. You need your Time Machine backups in one folder. You can always use the older one for backing up media etc,
Cheers
Pete

Time Machine has stopped working, HD errors

Time Machine has suddenly stopped working on my 2008 24" iMac. I have tried two separate drives, but neither work.
When I try and verify my internal HDD it comes back with a number of errors, and it has started to click recently. I expect the two must be linked!
I can't find my install disk to try to repair the main disk and some advice says that might be a bad thing to do anyway if the drive is physically damaged.
I have a full TM back up from two days ago, and I use Carbon Copy Cloner to backup my iPhoto/iTunes library separately.
My questions are:
1. What are the issues with running the iMac without TM until the disk finally dies? If it lasts, say, 6 months, can I just restore my Oct 2011 TM back up and rebuild my media libraries from CCC backups or will I lose something else?
2. Does anyone know the approx cost of getting Apple to replace the HDD? I have seen the online guides to doing it myself and don't really fancy trying!

Time Machine has suddenly stopped working on my 2008 24" iMac. I have tried two separate drives, but neither work.
When I try and verify my internal HDD it comes back with a number of errors, and it has started to click recently. I expect the two must be linked!
I can't find my install disk to try to repair the main disk and some advice says that might be a bad thing to do anyway if the drive is physically damaged.
I have a full TM back up from two days ago, and I use Carbon Copy Cloner to backup my iPhoto/iTunes library separately.
My questions are:
1. What are the issues with running the iMac without TM until the disk finally dies? If it lasts, say, 6 months, can I just restore my Oct 2011 TM back up and rebuild my media libraries from CCC backups or will I lose something else?
2. Does anyone know the approx cost of getting Apple to replace the HDD? I have seen the online guides to doing it myself and don't really fancy trying!

Time machine effectively stopped working

Ever since I upgraded to Mavericks my Time Machine backups started failing. I can't even unmount the file system at that point and have to Force Eject the TimeMachine partition.
I looked at open files using sudo lsof | grep /Volumes/TimeMachine, which shows several files open by mds_store and one by mds. However, killing these processes (kill -HUP <PID>) so that lsof shows no open files anymore does not free the disk for ejecting nor does it allow Time Machine to start backing up again.
Time Machine logs this mysterious message to the system logs:
24/11/13 10:16:34,621 com.apple.backupd[20727]: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/TimeMachine/Backups.backupdb/Hollewijn size:37
I did a search for this issue on Google and found several references, but none with a solution that worked for me or applied to my case.
The disk is a WD My Book that is brand new. It's split into 2 partitions, one named TimeMachine (about 250GB) and another that I use for extra storage.
The file system is fine, repair disk or repair permissions shows up nothing. To make sure the source of my backups isn't the cause, I did a repair disk on my Macintosh HD as well - nothing out of the ordinary.
One of the first things I did was to disable "Put hard disks to sleep" in the power management options.
I then upgraded the firmware of the drive to 3.2.0.10.
I tried excluding the Time Machine partition from Spotlight searches, but that's not allowed apparently. Besides, it's entirely possible that Spotlight is just another victim of the same underlying issue and fails to update it's indexes at some point, just as Time Machine is running into attributes it can't change.
Another possible cause was that something in my old backups (I carried this disk over from before Mavericks) was causing issues, so I recreated the file system on the TimeMachine partition and created a new base backup (which was successful). After a couple of days the issue reappeared, though.
Nothing seems to help, it's almost as if some kernel thread gets stuck when the disk is idle.
I just changed when my Mac goes to sleep from 3hrs to Never, I don't know yet what the results of that change will be.

I read your message, but that sounds dubious since this is a new disk I got just before upgrading to Mavericks - I didn't trust the old disk (rightly so, some part of that disk turned out to be unreadable at the block level), so postponed my upgrade until I was confident about my backups.
Still, even new disks can be broken, so you have a valid point. It's a bit hard to verify though.
It's starting to look like this is something USB related.
Yesterday evening both my trackball and keyboard (both USB) stopped working. The USB disk from earlier had already been "lost" to the OS earlier that evening; I got a message that it wasn't "Ejected properly".
I have quite a few USB devices connected; the backup disk, a powered USB hub, a KVM switch and a DVD drive are connected directly to the Mini - the KVM switch is connected to my Cinema display that, in turn, has the keyboard and trackball plugged in - the USB hub has the iPad and my android phone plugged in. I'm not counting any USB sticks, none are plugged in at the moment. A Mini only has 4 USB ports...
In earlier situations where I lost input devices, it helped to put the Mini to sleep using the power button on the back and input devices would come back to wake it up - not this time. I had to push the power button again to wake it up and still had no mouse or keyboard, a situation that then got detected by Mavericks with a somewhat unhelpful message to plug in such devices. Some replugging didn't fix that. Obviously something in the USB subsystem had gotten confused, leaving me with no way to access the menus to reboot the system.
I'm not that easy to stop - I did a remote login from my iPad using ssh and issued
sudo shutdown -r now
to reboot it (I have ServerAuditor on the iPad. It's really free, not some tuned down version of a commercial app that isn't useful until you "upgrade" to the paid version).
When the Mac came back up, keyboard, trackball and backup disk were working and Time Machine hasn't given an error since. Yay! It's probably a matter of time that it'll start failing again though.
I did change a few things over the last couple of days, as I had a theory that the backup disk might be getting just a bit too hot. For that reason, I turned the options to allow disks to go to sleep back on and set the Mini to sleep after 3 hrs.
For the record; the disk never felt hot, but it has a plastic casing, so heat conductivity could be an issue (also for whether it feels hot or not). Since I don't turn the Mac off unless I really have to (**** you, pesky updates!) it tends to be running for stretches of weeks and months. With Time Machine frequently attempting its backups, that might not give the USB disk enough time to cool off.
My bets are on an USB related issue, though.

Time Machine has stopped working - ideas?

A couple of days ago Time Machine stopped working on my iMac. It continues to try to backup, but each time gives the following error message - "The backup was not performed because an error occurred while copying files to the backup disk. The problem may be temporary. Try again later to back up. If the problem persists, use Disk Utility to repai your backup disk."
After getting this message several times I used Disk Utility. It told me everything is fine with the backup disk. I shut down and restarted the iMac and the backup disk. No luck. Just for fun, I tried Disk Utility again; still says the backup disk is fine.
Any ideas how to proceed from here? Any other info you need to diagnose what might be happening?

There are a lot of error messages on Console, beginning May 27. Most of them are the same, and relate to an application called FocalPoint 2. Here is the most comon error message -
May 27 00:52:44 Toms-iMac com.apple.backupd[3886]: Error: (-36) SrcErr:NO Copying /Applications/FocalPoint 2/FocalPoint 2.app/Contents/Frameworks/ONPSEmulator2.framework/Versions/A/Headers/ONPSEmulat or2.h to /Volumes/Backup Drive/Backups.backupdb/Tom's iMac/2011-05-26-205219.inProgress/CE8C7406-3014-4F66-A0BD-81DA7CF959EA/Macintos h HD/Applications/FocalPoint 2/FocalPoint 2.app/Contents/Frameworks/ONPSEmulator2.framework/Versions/A/Headers
Other error messages, the second is really long but all from the same attempted backup (I think) -
May 27 03:52:26 Toms-iMac com.apple.backupd[3886]: Copy stage failed with error:11
May 27 03:52:31 Toms-iMac com.apple.backupd[3886]: Backup failed with error: 11
May 27 04:52:19 Toms-iMac com.apple.backupd[3886]: Starting standard backup
May 27 04:52:19 Toms-iMac com.apple.backupd[3886]: Backing up to: /Volumes/Backup Drive/Backups.backupdb
May 27 04:52:23 Toms-iMac com.apple.backupd[3886]: No pre-backup thinning needed: 3.54 GB requested (including padding), 571.59 GB available
May 27 04:52:26 Toms-iMac com.apple.backupd[3886]: Stopping backup.
May 27 04:52:26 Toms-iMac com.apple.backupd[3886]: Error: (-36) SrcErr:NO Copying /Applications/FocalPoint 2/FocalPoint 2.app/Contents/Frameworks/ONPSEmulator2.framework/Versions/A/Headers/ONPSEmulat or2.h to /Volumes/Backup Drive/Backups.backupdb/Tom's iMac/2011-05-26-205219.inProgress/27D4C090-7BAF-4773-9DA8-44D38F98CE18/Macintos h HD/Applications/FocalPoint 2/FocalPoint 2.app/Contents/Frameworks/ONPSEmulator2.framework/Versions/A/Headers
May 27 04:52:26 Toms-iMac com.apple.backupd[3886]: Copied 81 files (64.7 MB) from volume Macintosh HD.
May 27 08:29:30 Toms-iMac com.apple.backupd[4307]: Starting standard backup
May 27 08:29:30 Toms-iMac com.apple.backupd[4307]: Backing up to: /Volumes/Backup Drive/Backups.backupdb
May 27 08:29:50 Toms-iMac com.apple.backupd[4307]: No pre-backup thinning needed: 3.54 GB requested (including padding), 571.46 GB available
May 27 08:29:55 Toms-iMac com.apple.backupd[4307]: Error: (-36) SrcErr:NO Copying /Applications/FocalPoint 2/FocalPoint 2.app/Contents/Frameworks/ONPSEmulator2.framework/Versions/A/Headers/ONPSEmulat or2.h to /Volumes/Backup Drive/Backups.backupdb/Tom's iMac/2011-05-26-205219.inProgress/86E09E21-DFE0-48D3-A206-D7AF82E9C0AC/Macintos h HD/Applications/FocalPoint 2/FocalPoint 2.app/Contents/Frameworks/ONPSEmulator2.framework/Versions/A/Headers
May 27 08:29:55 Toms-iMac com.apple.backupd[4307]: Error: (-36) SrcErr:NO Copying /Applications/FocalPoint 2/FocalPoint 2.app/Contents/Frameworks/ONPSEmulator2.framework/Versions/A/Headers/ONPSEmulat orBase.h to /Volumes/Backup Drive/Backups.backupdb/Tom's iMac/2011-05-26-205219.inProgress/86E09E21-DFE0-48D3-A206-D7AF82E9C0AC/Macintos h HD/Applications/FocalPoint 2/FocalPoint 2.app/Contents/Frameworks/ONPSEmulator2.framework/Versions/A/Headers
May 27 08:29:55 Toms-iMac com.apple.backupd[4307]: Error: (-36) SrcErr:NO Copying /Applications/FocalPoint 2/FocalPoint 2.app/Contents/Frameworks/ONPSEmulator2.framework/Versions/A/Headers/ONPSEmulat orCB.h to /Volumes/Backup Drive/Backups.backupdb/Tom's iMac/2011-05-26-205219.inProgress/86E09E21-DFE0-48D3-A206-D7AF82E9C0AC/Macintos h HD/Applications/FocalPoint 2/FocalPoint 2.app/Contents/Frameworks/ONPSEmulator2.framework/Versions/A/Headers
May 27 08:29:55 Toms-iMac com.apple.backupd[4307]: Error: (-36) SrcErr:NO Copying /Applications/FocalPoint 2/FocalPoint 2.app/Contents/Frameworks/ONPSEmulator2.framework/Versions/A/Headers/ONPSPlugin .h to /Volumes/Backup Drive/Backups.backupdb/Tom's iMac/2011-05-26-205219.inProgress/86E09E21-DFE0-48D3-A206-D7AF82E9C0AC/Macintos h HD/Applications/FocalPoint 2/FocalPoint 2.app/Contents/Frameworks/ONPSEmulator2.framework/Versions/A/Headers
May 27 08:29:55 Toms-iMac com.apple.backupd[4307]: Error: (-36) SrcErr:NO Copying /Applications/FocalPoint 2/FocalPoint 2.app/Contents/Frameworks/ONPSEmulator2.framework/Versions/A/Headers/ONPSPlugin Emulator.h to /Volumes/Backup Drive/Backups.backupdb/Tom's iMac/2011-05-26-205219.inProgress/86E09E21-DFE0-48D3-A206-D7AF82E9C0AC/Macintos h HD/Applications/FocalPoint 2/FocalPoint 2.app/Contents/Frameworks/ONPSEmulator2.framework/Versions/A/Headers
May 27 08:29:55 Toms-iMac com.apple.backupd[4307]: Error: (-36) SrcErr:NO Copying /Applications/FocalPoint 2/FocalPoint 2.app/Contents/Frameworks/ONPSEmulator2.framework/Versions/A/ONPSEmulator2 to /Volumes/Backup Drive/Backups.backupdb/Tom's iMac/2011-05-26-205219.inProgress/86E09E21-DFE0-48D3-A206-D7AF82E9C0AC/Macintos h HD/Applications/FocalPoint 2/FocalPoint 2.app/Contents/Frameworks/ONPSEmulator2.framework/Versions/A
May 27 08:29:55 Toms-iMac com.apple.backupd[4307]: Error: (-36) SrcErr:NO Copying /Applications/FocalPoint 2/FocalPoint 2.app/Contents/Frameworks/ONPSEmulator2.framework/Versions/A/Resources/English. lproj/InfoPlist.strings to /Volumes/Backup Drive/Backups.backupdb/Tom's iMac/2011-05-26-205219.inProgress/86E09E21-DFE0-48D3-A206-D7AF82E9C0AC/Macintos h HD/Applications/FocalPoint 2/FocalPoint 2.app/Contents/Frameworks/ONPSEmulator2.framework/Versions/A/Resources/English. lproj
May 27 08:29:55 Toms-iMac com.apple.backupd[4307]: Error: (-36) SrcErr:NO Copying /Applications/FocalPoint 2/FocalPoint 2.app/Contents/Frameworks/ONPSEmulator2.framework/Versions/A/Resources/Info.pli st to /Volumes/Backup Drive/Backups.backupdb/Tom's iMac/2011-05-26-205219.inProgress/86E09E21-DFE0-48D3-A206-D7AF82E9C0AC/Macintos h HD/Applications/FocalPoint 2/FocalPoint 2.app/Contents/Frameworks/ONPSEmulator2.framework/Versions/A/Resources
May 27 08:29:55 Toms-iMac com.apple.backupd[4307]: Error: (-36) SrcErr:NO Copying /Applications/FocalPoint 2/FocalPoint 2.app/Contents/Frameworks/ONPSEmulator2.framework/Versions/A/Resources/PSProgre ss.nib to /Volumes/Backup Drive/Backups.backupdb/Tom's iMac/2011-05-26-205219.inProgress/86E09E21-DFE0-48D3-A206-D7AF82E9C0AC/Macintos h HD/Applications/FocalPoint 2/FocalPoint 2.app/Contents/Frameworks/ONPSEmulator2.framework/Versions/A/Resources
May 27 08:29:55 Toms-iMac com.apple.backupd[4307]: Error: (-36) SrcErr:NO Copying /Applications/FocalPoint 2/FocalPoint 2.app/Contents/Info.plist to /Volumes/Backup Drive/Backups.backupdb/Tom's iMac/2011-05-26-205219.inProgress/86E09E21-DFE0-48D3-A206-D7AF82E9C0AC/Macintos h HD/Applications/FocalPoint 2/FocalPoint 2.app/Contents
May 27 08:29:55 Toms-iMac com.apple.backupd[4307]: Error: (-36) SrcErr:NO Copying /Applications/FocalPoint 2/FocalPoint 2.app/Contents/MacOS/FocalPoint 2 to /Volumes/Backup Drive/Backups.backupdb/Tom's iMac/2011-05-26-205219.inProgress/86E09E21-DFE0-48D3-A206-D7AF82E9C0AC/Macintos h HD/Applications/FocalPoint 2/FocalPoint 2.app/Contents/MacOS
May 27 08:29:55 Toms-iMac com.apple.backupd[4307]: Error: (-36) SrcErr:NO Copying /Applications/FocalPoint 2/FocalPoint 2.app/Contents/PkgInfo to /Volumes/Backup Drive/Backups.backupdb/Tom's iMac/2011-05-26-205219.inProgress/86E09E21-DFE0-48D3-A206-D7AF82E9C0AC/Macintos h HD/Applications/FocalPoint 2/FocalPoint 2.app/Contents
May 27 08:29:55 Toms-iMac com.apple.backupd[4307]: Error: (-36) SrcErr:NO Copying /Applications/FocalPoint 2/FocalPoint 2.app/Contents/PlugIns/FocalPointAutomation.plugin/Contents/Info.plist to /Volumes/Backup Drive/Backups.backupdb/Tom's iMac/2011-05-26-205219.inProgress/86E09E21-DFE0-48D3-A206-D7AF82E9C0AC/Macintos h HD/Applications/FocalPoint 2/FocalPoint 2.app/Contents/PlugIns/FocalPointAutomation.plugin/Contents
May 27 08:29:55 Toms-iMac com.apple.backupd[4307]: Error: (-36) SrcErr:NO Copying /Applications/FocalPoint 2/FocalPoint 2.app/Contents/PlugIns/FocalPointAutomation.plugin/Contents/MacOS/FocalPointAut omation to /Volumes/Backup Drive/Backups.backupdb/Tom's iMac/2011-05-26-205219.inProgress/86E09E21-DFE0-48D3-A206-D7AF82E9C0AC/Macintos h HD/Applications/FocalPoint 2/FocalPoint 2.app/Contents/PlugIns/FocalPointAutomation.plugin/Contents/MacOS
May 27 08:29:55 Toms-iMac com.apple.backupd[4307]: Error: (-36) SrcErr:NO Copying /Applications/FocalPoint 2/FocalPoint 2.app/Contents/PlugIns/FocalPointAutomation.plugin/Contents/PkgInfo to /Volumes/Backup Drive/Backups.backupdb/Tom's iMac/2011-05-26-205219.inProgress/86E09E21-DFE0-48D3-A206-D7AF82E9C0AC/Macintos h HD/Applications/FocalPoint 2/FocalPoint 2.app/Contents/PlugIns/FocalPointAutomation.plugin/Contents
May 27 08:29:55 Toms-iMac com.apple.backupd[4307]: Error: (-36) SrcErr:NO Copying /Applications/FocalPoint 2/FocalPoint 2.app/Contents/PlugIns/FocalPointAutomation.plugin/Contents/Resources/English.l proj/FPLocalizable.strings to /Volumes/Backup Drive/Backups.backupdb/Tom's iMac/2011-05-26-205219.inProgress/86E09E21-DFE0-48D3-A206-D7AF82E9C0AC/Macintos h HD/Applications/FocalPoint 2/FocalPoint 2.app/Contents/PlugIns/FocalPointAutomation.plugin/Contents/Resources/English.l proj
May 27 08:29:55 Toms-iMac com.apple.backupd[4307]: Error: (-36) SrcErr:NO Copying /Applications/FocalPoint 2/FocalPoint 2.app/Contents/PlugIns/FocalPointAutomation.plugin/Contents/Resources/English.l proj/FPSuiteSpecificLocalizable.strings to /Volumes/Backup Drive/Backups.backupdb/Tom's iMac/2011-05-26-205219.inProgress/86E09E21-DFE0-48D3-A206-D7AF82E9C0AC/Macintos h HD/Applications/FocalPoint 2/FocalPoint 2.app/Contents/PlugIns/FocalPointAutomation.plugin/Contents/Resources/English.l proj
May 27 08:29:55 Toms-iMac com.apple.backupd[4307]: Error: (-36) SrcErr:NO Copying /Applications/FocalPoint 2/FocalPoint 2.app/Contents/PlugIns/FocalPointAutomation.plugin/Contents/Resources/English.l proj/Localized.rsrc to /Volumes/Backup Drive/Backups.backupdb/Tom's iMac/2011-05-26-205219.inProgress/86E09E21-DFE0-48D3-A206-D7AF82E9C0AC/Macintos h HD/Applications/FocalPoint 2/FocalPoint 2.app/Contents/PlugIns/FocalPointAutomation.plugin/Contents/Resources/English.l proj
May 27 08:29:55 Toms-iMac com.apple.backupd[4307]: Error: (-36) SrcErr:NO Copying /Applications/FocalPoint 2/FocalPoint 2.app/Contents/PlugIns/FocalPointAutomation.plugin/Contents/Resources/English.l proj/OnOneErrorDialog.nib to /Volumes/Backup Drive/Backups.backupdb/Tom's iMac/2011-05-26-205219.inProgress/86E09E21-DFE0-48D3-A206-D7AF82E9C0AC/Macintos h HD/Applications/FocalPoint 2/FocalPoint 2.app/Contents/PlugIns/FocalPointAutomation.plugin/Contents/Resources/English.l proj
May 27 08:29:55 Toms-iMac com.apple.backupd[4307]: Error: (-36) SrcErr:NO Copying /Applications/FocalPoint 2/FocalPoint 2.app/Contents/PlugIns/FocalPointAutomation.plugin/Contents/Resources/FocalPoin tAutomation.rsrc to /Volumes/Backup Drive/Backups.backupdb/Tom's iMac/2011-05-26-205219.inProgress/86E09E21-DFE0-48D3-A206-D7AF82E9C0AC/Macintos h HD/Applications/FocalPoint 2/FocalPoint 2.app/Contents/PlugIns/FocalPointAutomation.plugin/Contents/Resources
May 27 08:29:55 Toms-iMac com.apple.backupd[4307]: Stopping backup.
May 27 08:29:55 Toms-iMac com.apple.backupd[4307]: Error: (-36) SrcErr:NO Copying /Applications/FocalPoint 2/FocalPoint 2.app/Contents/PlugIns/FocalPointAutomation.plugin/Contents/Resources/German.lp roj/Localized.rsrc to /Volumes/Backup Drive/Backups.backupdb/Tom's iMac/2011-05-26-205219.inProgress/86E09E21-DFE0-48D3-A206-D7AF82E9C0AC/Macintos h HD/Applications/FocalPoint 2/FocalPoint 2.app/Contents/PlugIns/FocalPointAutomation.plugin/Contents/Resources/German.lp roj
May 27 08:29:55 Toms-iMac com.apple.backupd[4307]: Copied 81 files (64.7 MB) from volume Macintosh HD.
May 27 08:29:55 Toms-iMac com.apple.backupd[4307]: Copy stage failed with error:11
May 27 08:30:00 Toms-iMac com.apple.backupd[4307]: Backup failed with error: 11
It appears that there is a problem with the FocalPoint Plugin?
Looking at Disk Utility, it tells me the Partition Map Scheme is Apple Partition Map.
Anything else you'd like to know?

My time capsule just stopped working

I just p[urchased the unit last weee, was able to partly set it up then it just stopped working

By stopped working do you mean the front LED is off?
When you boot it do any LED even flash??
Have you tried a factory reset?
The Factory Reset universal
Unplug your TC/AE. Hold in reset. and power the TC/AE back on.. all without releasing reset and keep holding in for about 10sec. The time is not important.. it is the front LED rapid flashing that indicates you are in factory mode.
Release reset.
If it doesn’t flash rapidly you have released reset at some point and try again.
Be Gentle! Feel the switch click on. It has a positive feel.. add no more pressure after that.
TC/AE will reboot after a couple of minutes with default factory settings and will wipe out previous configurations.
No files are deleted on the hard disk.. No reset of the TC deletes files.. to do that you use erase from the airport utility.
No luck then the TC is faulty and has to go back to Apple for replacement.

Time machine just stops.

I upgraded to leopard a few days ago, and have been trying to get time machine working. Whenever I try to back up, it goes until about 13 or 14 GB have been copied, and then stops suddenly. Sometimes it says that the latest back up failed due to an unnamed error, but usually it just doesn't list any. I tried what the sight says to do, re-partitioning the drive so it uses GUID instead of the other one it came with. I have also tried with two different drives, a Toshiba External USB 250GB, and a DiskGO Edge External USB 160GB, and they both fail at about the same point. To be clear, I have the drives set up according to this article, TS1550. I spent a lot of money on these drives, I would like at least one of them to work as the back up drive. One last thing, the DiskGo was recommended by a certified Mac distributor.

Welcome to Discussions.
Double check the partitioning scheme in Disk Utility as sometimes the formatting doesn't "take". Click on the upper icon for your drive. At the bottom right of the window "Partition Map Scheme :" should be GUID. If it isn't try following the directions for formatting this article

Time machine simply stopped working

I backed up my iMac weekly to a Lacie 500 GB HD, then went away for a few weeks so I disconnected (as I normally do when not in use). Now, when I want to back up it gets to 78 MB of 6 GB to back up then it stops. I tried with a different partition of the HD which doesn't work either.
Also, when I turned on the Lacie, I went into Time Machine but it's frozen, won't let me look at previous back ups, won't let me do anything apart from exit.
I'm puzzled as 2 weeks ago I would've said this is a rock solid and useful part of Leopard. Now?

Jon,
On every drive, there is first written a "partition map." It is this map that describes what volumes (partitions) exist on the drive, how large each one is, where they begin and end, etc. In a sense, it is like the "Table of Contents" in a book, and the partitions within it are like chapters. There are several schemes that are used to write this map, like different languages, or different dialects. PCs can access drives that use various schemes, but WIndows can only be installed on one that uses the "Master Boot Record" method of writing the map.
PPC Macs used the traditional Apple scheme, the "Apple Partition Map" scheme. Just like PCs, they can access drives that use other schemes, but the PPC version of OS X can only be installed on a drive that uses the "APM" scheme. The Intel version of OS X, on the other hand, requires a drive that uses the newer "GUID" scheme.
A side-effect of this is that Time Machine must have the a drive with the same scheme as the host, in order to correctly store the backup from that machine. For an Intel Mac, the external drive must use the "GUID" scheme. For a PPC Mac, the "APM" scheme. Does this clarify things?
I am trying to save all my data - 95 GB onto a partition that is more than twice that size and it saves about 20 MB before freezing yet again....
Are you saying that you have repartitioned your external drive, and yet your new attempts at running Time Machine are failing? If so, I am concerned. I mentioned a potential disk error earlier, but in the context of your external drive. When some form of copy action fails by "freezing," the most likely cause is a disk error, somewhere. In the case of copying from one drive to another, that disk error could be on the source, or on the destination. Since the fact that the external has just been formatted would tend to rule it out, I am concerned that you might have one on your Mac's internal drive.
If you are trying and failing to run Time Machine or make copies after having formatted that external, please use Disk Utility to check your internal drive for errors.
Something else, though: Are you absolutely certain that the Time Machine backup is "freezing?" In many cases, when making the initial backup, Time Machine can and does take a very long time to copy data during the first half of the backup process. It might copy 20 MBs, then "think" for 5 minutes, then copy 200 MBs, then think for 1, then copy a whole 6 GBs before stopping to think again. Are you certain that you have given it long enough?
Scott

Time machine has stopped working.

I just noticed that the green light on my time machine has gone out. So, I checked the connections, replaced the fuse in the plug and plugged it into a different socket. It still doesn't work. I am concerned that the problem is in the time machine itself. Does anyone have an answer?

Hi Peter,
It sure would seem that it's likely failed.

Time Machine just stopped working, Disk Repair & Read Only errors

Similar Messages

Maybe you are looking for