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

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?

  • 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?

  • 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.

    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

    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.

  • Time machine has stopped working - 'the backup volume could not be found'

    i'm not sure what happened, but my macbook pro hasn't been able to backup to my time machine for the past few weeks. i get a 'delayed' message, then in time machine prefs it says 'the backup volume could not be found.' i can manually mount the backup image, but it still won't backup. my wife's 12" powerbook is backing up perfectly. we both have 10.5.4. i was having the problem before the 7.3.2 firmware update, so that doesn't seem to be the cause. has this happened to anyone else? could my computer somehow lost track if the backup? is there prefs that can be trashed? i don't mind losing my old backups if i need to start over, but i can't figure out how to force it to backup because i keep getting the 'backup volume can't be found' no matter what i do.
    my setup: dsl modem into time machine / my macbook pro, my wife's powermac 12", and our apple tv are the only clients.

    There is a Time Machine preferences file at
    <your startup drive root>/Library/Preferences/com.apple.TimeMachine.plist
    Note: This is be main Library folder, not the one in your user folder.
    You might try moving that to the Desktop so that the system creates a new one.

  • 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

  • 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.

  • My time capsule has stopped working since installing Yosemite. It says to wait to tell me how much longer but it stays that way for hours.

    My time machine has stopped working since I upgraded to Yosemite. It gets to the point that says it will estimate the time remaining, but it never gives me that answer and it just stays on that page and never completes it's backup. This is a brand new macpro, so I wanted to capture the previous info on my computer I was able to put my external hard drive on new computer and it did the migration and all my old info returned. However, two days later I wanted to do a backup using Time Machine with my Western Digital Mac external hard drive but it won't progress past saying how much time remaining, even after several hours of sitting there.

    You do need to wait a long time.. as it takes a long while for Yosemite to index the existing backup if it is large.
    Here is Apple's List of bad things that happen to TM in Yosemite.
    OS X Yosemite: Time Machine problems
    It is clearly no where near as comprehensive as it needs to be.
    I presume your disk has your old backup.. it may be better to keep the old backup.. save that for the future.. and get a new disk and start a fresh clean backup.
    I would also recommend using Carbon Copy Cloner or similar for the time being. Make a bootable clone backup of your drive to a new external drive.. it is really superior in lots of ways to Time Machine. And does show you what it is doing.
    For TM at least you can still use the widget so you have some log access to that TM does.
    A1 here. http://pondini.org/TM/Troubleshooting.html

  • Started using my Time Capsule as a base station; now Time Machine won't work

    Dear community,
    I had been using my Time Capsule just for Time Machine backups, but I recently switched to using it as an internet base station as well. Now I can connect to internet via Wi-Fi, but Time Machine no longer works (it throws a "backup disk cannot be found" error). I assume this is related to the fact that the name of my Wi-Fi network differs from the name that my Time Machine used to have back when it was only my backup disk. Does anyone have any ideas for how to get Time Machine working again, hopefully without losing all my backup history? Thanks for your help.
    I am using a Time Capsule (circa 2012) and a late-2011 MacBook Pro with OS X 10.9.3.

    This is just typical Mavericks behaviour.
    You must find the hard disk for it. Poor Mavericks cannot find its own tail let alone a network device as complex as a hard disk.
    Does anyone have any ideas for how to get Time Machine working again, hopefully without losing all my backup history?
    Let me say, that killing your backups is harder than simple resets or changing functions. In fact the only way to wreck the backups is erase them deliberately from airport utility, or have TM working over a faulty link and corrupt them.
    The issue is simply that the hard disk is lost. And Bo Peep doesn't know where to find it.
    Step in and mount the hard disk manually.
    In Finder.. use Go, Connect to server.
    Type in AFP://TCname.local
    Where TCname is the actual network name of the TC. (Hopefully you are now using short names with no spaces and pure alphanumeric.. in which case network name = name. If not then you need to translate the name to the network name.
    So Fred Blog's Airport Time Capsule which you name it in the utility comes out.
    fred_blogs_airport_time_capsule as network name. Spaces and apostrophe are illegal.
    Let me encourage you to go back to the airport utility and rename the TC something sensible like TCgen4 (it is a gen4) and use TCwifi for the wireless name. Then the network name is at least something like the actual name.
    So in my case I would type in AFP://TCgen4.local
    Local is the default domain and using it can also help.
    The caps are irrelevant.
    The other and better way of doing it in Mavericks is use IP address of the TC if it is static. ie if the TC is main router it will have IP 10.0.1.1 by default.
    Then you type AFP://10.0.1.1
    You will be asked for the password.. type that in and keep it in your keychain.
    (BTW you can discover the actual names of everything via the netstat scan from network utilities. In Mavericks Network Utilities has gone walkabout, so you will need to search for it in finder). You should see the actual network names of everything listed here. Along with MAC address and other info.
    Now you can reset TM and point it at the TC disk which is already open in finder.
    See info on TM reset here.
    A4 http://pondini.org/TM/Troubleshooting.html
    Please note when TM starts up it will show it is going to do a full backup.. this will not happen. It will discover the existing backup and then simply do incremental. (I hope!!) Nowadays with Mavericks nothing can be certain.
    Good Luck.. !
    Sorry I have made it over complicated.. Early morning here and not suitably caffeinated yet.
    If you run into trouble post back.

  • Time Machine doesn't work

    Hi guys,
    I’m new on Mac. I have a new MBP retina display running on OSX 10.8.2. I used time capsule 2Tb as a external hard drive for Time Machine. It worked fine for about 10 days. Then it stopped backing up, not sure if it coincided in time with an upgrade of the operative system I did some days ago. At the beginning, TM didn’t report any error (for days). Airport is updated. TC has a lot of free GBs.
    Since I noticed the problem I surfed the communities and found this is a common issue of users after upgrading to Mountain Lion. I tried many different solutions that were useful for many people, none of them worked for me. Let me show you some of these ways other people found to fix the bug.
    Checked the names of the MBP, TC and network, remove appostrophies and spaces in those names.
    Switched time machine off and on several times
    Tried to reconnect to the TC server by the finder, so trying to avoid a ghost hard drive it appeared on time machine
    Looked for a button to “Verify backups” that never appeared on my time machine menu
    Soft reset of the TC
    Full reset of the time machine
    Around a pair of dozens restarts (TC, TM, MBP, networks…)
    Excluded antivirus and dropbox files as potentially source of troubles
    Disable the option “Put the hard disks to sleep when possible” on the energy saver preferences
    Right now, TM says it has None backups done, and I cannot use Time machine. When forcing a “Back up now” it spends a minute “Looking for backup disks” but it never finds anything. Today a couple of error messages have finally come up: one said something like The backup disk image “/Volumes/Data/xxxxxxx.sparsebundle” could not be accessed (error -1).
    The other was an error number of four digits, starting in 6 (sorry I didn’t copy it).
    I don’t care if I have to delete previous backups, it would be ok for me. However, I don’t want to erase other big amount of data stored in the TC that is different from the backup image. I tried to delete the backup image file from the TC but I couldn’t.
    I need help, please. MANY THANKS IN ADVANCE

    My Time capsule didn't work for reasons unknown.
    I'm posting this because the solution i found was not posted.
    I reinstalled my Operating system. Here are the steps for anyone who needs them.
    1. Goto Applications.
    2. Then look for the "Utilities" Folder.
    3. Click on the app called "Disk Utilities"
    4. In the White box on the left, you will see your internal Hard Drive Icon.
    Click on the very first Drive at the top of the list.
    5. Look for the two buttons: "Verify Disk" and "Repair Disk". Click on the "Verify Disk" button ONLY!
    This will verify if your hard drive has any internal problems.
    6. After it finishes verifcation, the Details box will who the following list:
    Verifying volume “Whatever the name of your drive”
    Checking file systemPerforming live verification.
    Checking Journaled HFS Plus volume.
    Checking extents overflow file.
    Checking catalog file.
    Checking multi-linked files.
    Checking catalog hierarchy.
    Checking extended attributes file.
    Checking volume bitmap.
    Checking volume information.
    The volume "Whatever the name of your drive" appears to be OK. (in Green Letters)
    7. If your hard drive shows a green message like the one above, your drive is ready
    to reinstall your operating system on it.
    If your hard drive (SHOWS A RED MESSAGE) INSTEAD of a green message, your drive is NOT ready
    to reinstall your operating system on it AND it will need to be taken to an Apple Genius Bar.
    8. If your drive appears to be OK (in green), turn your computer off, wait 10 seconds and restart it.
    9. Once the grey screne shows, hold down the "Option" button until something pops up on the screne.
    10. Look for the "Recovery HD" grey Hard Drive icon.
    11. Use the Up and Down buttons to choose your internet connection
    (or none at all if it's automatically connected).
    12. Use the Left and Right buttons to choose your Recovery HD Hard Drive icon. Click Return.
    13. Wait for the Window called "Mac OSX Utilites" to pop up.
    14. Choose the icon that says (Reinstall Mac OSX).
    15. Everything else will be self explanatory.
    16. Hope this helps. Your system will be reinstalled without any problems to the files on your computer.
    This only works for Mac computers made 2012 and after. I have no knowledge of any computer systems before OSX 10.7.
    My Time Capsule works perfectly. Hope yours does as well.

  • Time machine is not working on imac intel i7

    I just got a new imac intel core i7 which is an upgrade from my power mac G4 MDD which I got in 2003. I transferred all the information from the power G4 using time machine and it worked fine. I then upgraded the OS to 10.6.4 given imac is intel core. All programs are working fine except I am unable to use time machine. It runs for a few gb and then the following error come on time machine buddy:
    Starting standard backup
    Backing up to: /Volumes/Backups/Backups.backupdb
    Ownership is disabled on the backup destination volume. Enabling.
    Backup content size: 237.9 GB excluded items size: 818.0 MB for volume Macintosh HD
    No pre-backup thinning needed: 284.58 GB requested (including padding), 930.57 GB available
    Waiting for index to be ready (101)
    Indexing a file failed. Returned 1 for: /System/Library/Frameworks/Python.framework/Versions/2.5/Extras/lib/python/wx-2 .8-mac-unicode/wx/lib/floatcanvas/Utilities/_init_.py, /Volumes/Backups/Backups.backupdb/van (5)/2010-08-17-184416.inProgress/75B311E0-7C50-4BD3-B7AD-03E3A1B883B2/Macintosh HD/System/Library/Frameworks/Python.framework/Versions/2.5/Extras/lib/python/wx -2.8-mac-unicode/wx/lib/floatcanvas/Utilities/_init_.py
    Aborting backup because indexing of file failed.
    Stopping backup.
    Copied 70375 files (17.4 GB) from volume Macintosh HD.
    Copy stage failed with error:11
    Backup failed with error: 11
    Then when I try to verify and repair the disk, it does do it and keep on showing: " invalid node structure, invalid key length and invalid record count"
    I have changed the external hard drive twice so I doubt that is the problem. Please help

    Rajiv,
    I'd recommend going to the Time Machine forum for Snow Leopard. First start out reading the Troubleshooting FAQ at the top. The forum is located at:
    http://discussions.apple.com/forum.jspa?forumID=1342
    Regards,
    Roger

  • Time machine is not working

    I just got a new imac intel core i7 which is an upgrade from my power mac G4 MDD which I got in 2003. I transferred all the information from the power G4 using time machine and it worked fine. I then upgraded the OS to 10.6.4 given imac is intel core. All programs are working fine except I am unable to use time machine. It runs for a few gb and then the following error come on time machine buddy:
    Starting standard backup
    Backing up to: /Volumes/Backups/Backups.backupdb
    Ownership is disabled on the backup destination volume. Enabling.
    Backup content size: 237.9 GB excluded items size: 818.0 MB for volume Macintosh HD
    No pre-backup thinning needed: 284.58 GB requested (including padding), 930.57 GB available
    Waiting for index to be ready (101)
    Indexing a file failed. Returned 1 for: /System/Library/Frameworks/Python.framework/Versions/2.5/Extras/lib/python/wx-2 .8-mac-unicode/wx/lib/floatcanvas/Utilities/_init_.py, /Volumes/Backups/Backups.backupdb/van (5)/2010-08-17-184416.inProgress/75B311E0-7C50-4BD3-B7AD-03E3A1B883B2/Macintosh HD/System/Library/Frameworks/Python.framework/Versions/2.5/Extras/lib/python/wx -2.8-mac-unicode/wx/lib/floatcanvas/Utilities/_init_.py
    Aborting backup because indexing of file failed.
    Stopping backup.
    Copied 70375 files (17.4 GB) from volume Macintosh HD.
    Copy stage failed with error:11
    Backup failed with error: 11
    Then when I try to verify and repair the disk, it does do it and keep on showing: " invalid node structure, invalid key length and invalid record count"
    I have changed the external hard drive twice so I doubt that is the problem. Please help

    Rajiv Jauhar wrote:
    I excluded both files and it just worked. It seems to have backed up all the files.
    That's a bit surprising (but good).
    Is there a way to check?
    If the backup completed normally, everything should be fine. If you want, you can browse your backups, and perhaps restore a few selected things to alternate locations (such as your desktop), and compare them, just to be sure. (If you're not sure how to do that, see #16 in the FAQ.)
    Also are the files that I excluded important?
    They're not critical, and reinstalling OSX would get fresh copies.
    I did talk to AppleCare 4 days ago. The gentleman was very nice and helpful. He did not understand how to fix the problem so he was going to push it up to the next level but they have not responded. I must say that I am very disappointed. I have 3 IMAC computers, 1 power mac G4, a macbook pro laptop, an ipad, 2 iphones and several itouches and ipods. I love Apple but I am very disappointed with the service. I always get apple care when available and, fortunately, have never had to use it. Now I did and I really have not gotten the help that I wanted. Just my ranting. No matter, I am still going to stay with apple.
    They will get back to you, sooner or later. Some of them don't seem to know a great deal about Time Machine, unfortunately, and this is not a common situation.
    As long as you do have completed backups, you're probably ok. I'd suggest just keeping an eye on it for a while; if nothing else goes wrong, and you haven't heard from AppleCare, then decide if you want to go farther.
    If you do, I'd suggest reinstalling OSX from your Install disc (that won't touch anything else). Then
    download and install the 10.6.4 "combo" update. Info and download available at: http://support.apple.com/kb/DL1048 Be sure to do a +Repair Permissions+ via Disk Utility (in your Applications/Utilities folder) afterwards.
    That will get you a new, fresh copy of OSX. Try a backup to make sure everything's still ok, then remove the exclusions and see what happens. If it runs ok, then something in those two files was corrupted -- unusual, but as they say, "stuff happens."
    Keep us posted.

Maybe you are looking for