Time Machine - hung

I was doing my first backup and TimCapsule is hung... Just sits there with the message Stopping Backup. It is on a new iMac and there is nothing loaded yet so shouldn't take this long.... it has been over 5 hours.
Should I unplug the TIme Capsule?
Thanks for your help

First, see #D6 in [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html] (or use the link in *User Tips* at the top of the +Time Machine+ forum).
Second, do the initial backup via Ethernet if at all possible; it will be much faster.
You should expect somewhere in the neighborhood of 24 GB/hour via Ethernet, and perhaps 12 GB/hour via a good WIFI connection, although the rate will vary widely during the backup, depending on what's being backed-up at the time.
If your backup is considerably slower than that, over a period of time, see #D2 in Troubleshooting.

Similar Messages

  • Time Machine hung: a solution!

    I've just found a solution to a persistent Time Machine problem: at first doing incredibly large and time consuming backups (e.g. 16.8 Gb – twice in a row) each time even when there has been no activity, then taking forever Indexing Backup, then getting hung completely on Indexing Backup. AppleCare for a month was of absolutely no help – until today I managed to connect to a very useful and helpful senior advisor who actually did what he promised to do.
    So, the problem was that my external hard drive was not formatted correctly. It should be formatted: Mac OS Extended (Journalled). Be careful: there are other options that look almost the same, but are not. I was directed to Applications/Utilities/Disk Utilities. Then I selected the external hard drive on the left pnae, then in the centre the proper formatting such as above. Then Delete. Then go to Time Machine Preferences, and select the disk as the Time Machine. Problem solved! The first complete backup started almost immediately and took 2 hours. Normal. Subsequent backups have been taking just seconds.
    So, why are these various formatting options for the Time Machine external disk? I just followed the instructions in the Time Machine, never given an option or an instructions about formatting. And it seems that not all AppleCare advisors are aware of this, which I am now learning may be a common problem, especially with Lion.
    So, now I can feel more secure about my backups. And spend my time using my new MacBookPro rather than on trying to fix it.

    Time Capsule is the only Apple supportrf network drive for Time Machine.
    Since you have have eliminated that then I have to say no.

  • Time Machine hung while intial backing up to external HD

    Hello all,
    I am trying to help a client here to do an intial back up with her Time Machine and external HD but it kept on hung up every time.
    Here's the picture:
    She have iMac 21.5" with Snow Leopard OS (10.6.8) connected to  2TB Seagate external hd for Time Machine use only.
    I formatted the seagate external HD to Mac Journaled format and everything looks good. The Time Machine starts to back up for very first time and it got stuck in the middle of back up. I formatted the external HD again and tried to do intial back up again and it got stuck again on 111.17 GB out of 278.8 GB for a over 2 hours. It hasn't moved.
    I downloaded "Time Machine buddy" widget and it shows:
    Starting standard backup
    Backing up to: /Volumes/Time Machine/Backups.backupdb
    Ownership is disabled on the backup destination volume.  Enabling.
    Error parsing SystemMigration.log to determine source volume of system migration.
    Backup content size: 278.8 GB excluded items size: 3.0 GB for volume mac_HD
    No pre-backup thinning needed: 330.92 GB requested (including padding), 1.82 TB available
    Waiting for index to be ready (101)
    Copied 74.4 GB of 275.8 GB, 225989 of 1215218 items
    I've tried the troubleshooting with this link and it doesn't work:
    http://pondini.org/TM/Home.html
    Hope this issue can be resolved soon!
    Thanks,
    Matt

    First, a terminology problem:  this is the Time Capsule forum -- a piece of Apple hardware combining a wireless router and HD, usually used as a destination for Time Machine backups.
    Time Machine is the Apple software that performs backups, to external HDs, Time Capsules, etc.
    Does the HD have the GUID partition map scheme?  If not, reformat it that way.  I doubt that's the problem, but you never know.
    From the messages, it looks like Time Machine finished the initial backup "pass." Normally, if more changes are made while it's backing-up, it will do a small, quick second pass to catch up.  But there's no message starting the second pass (another of the "requested" and "available" messages), and the amount copied doesn't match the 111.17 GB where it stuck. 
    Try verifying the internal HD; there might be a directory problem that Time Machine's tripping over.
    If that doesn't help, look directly at the system.log via Console, for the time of the backup.  There may be some related messages there, but sent by other processes than backupd, that will provide a clue.

  • Time Machine hung up while "backing up"

    Time Machine's first attempt at a back up failed this morning. And as this has happened before, I simply did what I had done in the past ... a manual "back up now". But today, it didn't work. Instead, the Time Machine preferences states that it is "backing up" and seems to get hung up like that. When you check the TM Buddy widget, the following line is listed over and over 10-15 times ...
    Waiting for index to be ready (915 > 0)
    TM has been hung up for hours ... seriously hours ... like this. I've manually stopped the back up, restarted the computer, etc. all to no avail. And now when I've tried to b/u, my widget displays nothing. So, I don't even have anything to post to aid in assistance. TM is currently turned off.
    Any help on where to go from here is greatly appreciated.

    Hjeirce wrote:
    Waiting for index to be ready (915 > 0)
    Hi, and welcome to the forums.
    This can be caused by several things.
    First, are you sure it's formatted properly? Use Disk Utility (in your Applications/Utilities folder). Select the top line (with the make and size). Down towards the bottom, *Partition Map Scheme* should be GUID for an Intel Mac, +Apple Partition Map+ for a PPC Mac.
    Then select the second line. Down towards the bottom, Format should be +Mac OS Extended (Journaled)+
    If you're running any anti-virus scans, exclude your TM disk from them.
    Also exclude it from Spotlight, at least temporarily, via System Preferences > Spotlight > Privacy.
    If those don't help, that leaves the drive itself:
    Is it FireWire or USB?
    If USB, does it have it's own power supply, or does it get power from your Mac? If it uses your Mac's power, try another port (not one on your keyboard), and try unplugging other USB devices such as printers.
    The drive may be "spinning down" at idle. Try System Preferences > Energy Saver and de-select +Put the hard drives to sleep ...+ Some drives respond to that setting, some don't.
    Does it have an automatic "Spin down" mode of it's own? If so, can you disable it? Check with the manufacturer's web site, support, and/or forums. Some WD drives, I think, have a recent firmware update that may fix this.

  • Time Machine Hung Up

    I set up Time Machine to a Seagate Free Agent Drive about 5 weeks ago. It's worked fine until recently; I noticed yesterday that the TM icon was continually spinning, & when I go into TM Preferences it shows that it is backing up "1 kb of 42 kb". About half an hour ago I clicked on "Stop Backing Up." Now I have a "Stopping Backup" & "Stop Backing Up" in gray, & it is still spinning around showing the "1 kb" message. Any thoughts???? Thanks.

    Terence Norman wrote:
    Pondini, thanks for your real-time assistance on this - I hope I'm not being presumptious posting blow-by-blow - I'm retired so I sometimes forget that others may have things (like work!) to do So don't let me impose on your good nature.
    I'm retired, too, but in and out today doing yard work.
    I wondered about running Software Update and looking for any new(er) drivers? - Terry.
    I doubt there's anything from Apple, especially since you're on Leopard. Then again, updating to 10.5.8 might be worth a shot, if you're really still on 10.5.6. I'd suggest downloading and installing the "combo" update. That's a combination (thus the clever name) of all the updates to Leopard since it was first released, so installing it should fix anything that's gone wrong since then, such as with one of the normal "point" updates. Info and download available at: http://support.apple.com/downloads/MacOS_X_10_5_8_ComboUpdate Be sure to do a +Repair Permissions+ via Disk Utility (in your Applications/Utilities folder) afterwards.
    And/or try the things in #D2 of the Time Machine - Troubleshooting *User Tip* at the top of this forum. The last item (not necessarily the least likely) may be what you need.

  • Time machine "hung up" and won't finish a backup

    TM was working fine for me. But it has sat at the same place for almost 20 hours now. I have plenty of disk space. The progress shows it is stuck at 40.3MB of 145.9MB. An OSX update was installed yesterday, is that the reason? Any steps to get this back on track would be greatly appreciated! Thanks.

    Normally, a long 'Preparing' session after an update is OK. If you take a look at the Console logs Time Machine is reporting that your backups need "deep traversal". That's fine. Time Machine knows what is wrong and how to fix it. Let it do it's thing. If you have alot if data, it may take quite awhile.
    After your update to 10.5.5 Time Machine realized the system no longer matched what it looked like during the previous backup. So it has determined that it's earlier catalogue of what-should-be-where is 'untrustable'. So it is going to go item-by-item comparing the before and after of your system.
    However, in your instance, it is simply taking too long and seems to have choked.
    *Anti-Virus Software*
    Running anti-virus software can interfere with the backup process. Either disable it altogether, or try the suggestion outlined here, “If you use third-party anti-virus scanning software and have issues, make sure your Time Machine back up folder (Backups.backupdb on the Time Machine disk) is excluded from virus scanning.” (http://support.apple.com/kb/TS1516)
    *Reselect Backup Disk*
    There is the possibility that the first backup after a major OS update will fail. The Console may report that the backup disk is ‘not owned by backupd’. Essentially, Time Machine no longer recognizes the backup disk.
    Go to System Preferences --> Time Machine.
    Click the "Change Disk..." button.
    Select "None" and click "Stop Backing Up".
    Now click "Choose Backup Disk" and reselect your drive again.
    Close System Preferences and try backing-up again.
    Let us know if this helps.

  • Restore from Time Machine hung on "Looking for source"

    Had to buy a new Macbook Air to replace my old one which was water damaged.
    I have a full Time Machine backup on a portable USB hard drive which is divided into two partitions: Time Machine backup and a storage partition.
    Old Macbook air has the previous operating system, updated.
    New MA has mavericks of course.
    Setup assistant didn't see the Time Machine backup when attached.
    So I setup an account on the new computer, got to the main screen, started migration assistant to see if that would work.
    (With the new account, the portable USB drive is recognized and both partitions show in the finder.)
    Same problem. Migration assistant sits with spinning icon at "Looking for source".
    What can I do to show it where the Time Machine backup is?
    Thanks.

    mjmorris11733 wrote:
    I start TM, I can see the NAS drive as a TM-mount point, I select it
    Does that mean you selected it on the Time Machine Preferences window?  If not, do that.
    If that doesn't help, the preferences file may be damaged.  Try a "full reset" per #A4 in Time Machine - Troubleshooting.
    If still no help, the backups themselves may be damaged.  Try to repair them, per #A5 in the same link.

  • Time machine hung on calculating changes (stuck at 99%)

    Im experiencing a few problems with time machine which is currently set to back up wirelessly to a time capsule. This has been working great for about a year now never any problems with any backup in the past but over the last day i can not get a backup to complete.
    N.B; i have been staying away for the past two weeks as i am at university so i'm aware the first backup will be large with a two week gap. Though this is not usually a problem. The other change is i have recently changed the net work set up, before Time capsule was connected to another router (BT Voyager 205) in bridge mode, now i have a new router (BT home hub 2.0) and have re-configured time capsule to simply join the wireless network for back up and storage purposes.
    Heres what i have tried:
    Powering down the time capsule and my laptop several times
    unselecting the disk in the time machine options, selecting none and then re-selecting the disk
    a full reset of time machine (followed the steps found here; http://discussions.apple.com/thread.jspa?threadID=2057525)
    Heres the console log messages:
    05/03/2010 12:09:02 com.apple.backupd[281] Starting standard backup
    05/03/2010 12:09:02 com.apple.backupd[281] Attempting to mount network destination using URL: afp://James%20Clough@James%20Clough's%20Time%20Capsule.afpovertcp.tcp.local/Data
    05/03/2010 12:09:02 com.apple.backupd[281] Mounted network destination using URL: afp://James%20Clough@James%20Clough's%20Time%20Capsule.afpovertcp.tcp.local/Data
    05/03/2010 12:10:41 com.apple.backupd[281] Disk image /Volumes/Data-1/James MacBook_0023df8f4ff4.sparsebundle mounted at: /Volumes/Backup of James MacBook
    05/03/2010 12:10:47 com.apple.backupd[281] Backing up to: /Volumes/Backup of James MacBook/Backups.backupdb
    05/03/2010 12:10:53 mds[36] (Normal) DiskStore: Rebuilding index for /Volumes/Backup of James MacBook/Backups.backupdb
    05/03/2010 12:13:35 com.apple.backupd[281] Event store UUIDs don't match for volume: Macintosh HD
    05/03/2010 12:16:33 com.apple.backupd[281] Node requires deep traversal:/ reason:must scan subdirs|new event db|
    05/03/2010 12:16:36 mds[36] (Normal) DiskStore: Creating index for /Volumes/Backup of James MacBook/Backups.backupdb
    05/03/2010 12:20:16 com.apple.backupd[281] Node requires deep traversal:/Users/James/Pictures/iPhoto Library reason:contains changes|must scan subdirs|found in deep scan|missed reservation|
    also noticed for the first time that when clicking into spotlight search at the right of the screen i see:
    "Indexing backup of James' Macbook"
    with an estimating time bar below which keeps spinning giving no time, just says estimating??
    thankyou to anyone who can help shed some light on this problem.

    vengenceJC wrote:
    also noticed for the first time that when clicking into spotlight search at the right of the screen i see:
    "Indexing backup of James' Macbook"
    with an estimating time bar below which keeps spinning giving no time, just says estimating??
    The combination of symptoms sounds like your backups may be corrupted. Cancel the backup and Repair them per #A5 in the Troubleshooting Tip.
    You might want to exclude the drive from Spotlight indexing temporarily, until the backup is done, via +System Preferences > Spotlight > Privacy.+
    And since Time Machine has to do a "deep traversal," connect to the Time Capsule via Ethernet if at all possible -- both the "deep traversal" and actual backup will be faster that way.

  • Time machine hung?  reboot?

    I bought a new 2TB drive and installed it and I am using TM to transfer everything. It took two hours for it to do the back up -then the screen said 'less than a minute' for the last ten hours - transferring files - moving support applications. Is it hung? Should I reboot or leave it? (125g was on it before)

    you may have a drive that 'fell asleep' or fell off the channel.
    Green 2TB or not?
    FW400 or USB or eSATA?
    Do you really want to use timemachine? or perhaps CCC and SuperDuper would fit your needs and be better (even if you use TM I'd use something else as well) - not your primary backup method - but maybe to get people that never backed up before to start doing so.
    I think TimeMachine does what you are seeing and was very much "1.0" in too many ways.
    Leopard TimeMachine
    http://www.apple.com/support/timemachine

  • Time Machine Error ( Hung on Preparing)

    Running the latest Lion software 10.7.4 ..Time machine is looping " preparing backup' ...using Time Capsule  500 gb storage...2 MBP back up to this system..one Snow Leopard and the one Lion.
    Time machine is showing 30 MB available... problem appears to be that the old backups are not being deleted no storage is available and it fails to create any additional new backups.. Problem occured in March and I needed to erase the entire backup disk and start over to clear the issue.. It went successfully..now the same prob 3 months later.
    My backup is about 181 gb the other is about 100 gb..
    Any suggestions why this may be occurring? Obviously the root cause issue was not resolved by deleting the entire disk..
    Thanks for any help!!
    Tony

    tonal wrote:
    Tony Sparsebundle was 431gb with an HD of 126gb (Lion 10.7.4)
    Barb Sparsebundlle was 66gb with an HD of 76gb (Snow Leopard 10.6.8)
    Don't know why the sparsebundle is so huge?
    Time Machine keeps backing-up new and changed items.  Once it runs out of room for new backups, it starts deleting old backups, but only from the Mac it's running on.  That way, it keeps as many old backups as it can, filling all the available space.
    Usually, that's not a problem, but in your case, Tony's backups have "hogged" most of the drive.  See Time Machine - Frequently Asked Question #33, especially the pink box, for an explanation and some possible workarounds.
    Should I delete the Tony Sparebundle and then backup over ethernet as the best choice at this point?
    That's certainly the fastest, easiest thing to do.    But it may not work for long. 
    Would would cause this problem(storage depletion) to start to occur... was fine for 3 years...problem started in March..
    As detailed in the link, that Mac must have needed a number of extra-large backups, so took up a lot of space very quickly.  Whatever you do, monitor the size of future backups.  If they seem too large, see #D4 in Time Machine - Troubleshooting.
    One solution would be to limit the size of each sparse bundle, per #A8 in the same link.
    Another, probably better, option would be to connect a USB drive to the TC, and back up one of the Macs to it, instead of the TC's internal HD. See #Q2 in Using Time Machine with a Time Capsule for details.

  • Time machine restore hung up for hours

    The system HD for my mac pro crashed. Had a new drive installed with 10.5.
    I initiated a transfer of info from my 1tb WD book drive. All seemed to go well until the process seemingly ground to a halt with the progress window stating less than a minute to go , Transferring files to support applications. This has been static on this for a couple of hours. Am completely stalled at this point.

    old Bill wrote:
    Perhaps someone out there could answer this for me. When I use MS Word for Mac 2008, and save a file to my internal hard drive, the (external) Time Machine disc spins up also. This is mildly irritating, since a file save takes a few extra seconds. I'm just curious. What's going on?
    That will happen whether you're using Time Machine or not. Any time OSX gives you a selection of where you want to save something, it checks everything that's attached, to be sure it's still there and can be used for the kind of thing you're saving. If an external HD is attached, but sleeping, OSX will wake it up as part of that process. There doesn't seem to be any way to prevent it.
    I thought Time Machine buffered up stuff to be saved for 30 minutes before writing to the disc.
    No. When it does it's hourly backups, it writes to the TM drive immediately. There's no doubt a temporary buffer, but there's no particular delay.

  • Can't Access Recent Backups in Time Machine

    I was in the middle of installing OSX 10.10.1 and the installation hung on "setting up your mac", so I did a restart with the intention of restoring my whole system from a recent backup. I restarted with the option key, selected restore from Time Machine backup, then selected the backup I wanted my system restored from (dated 17 November), and left it to restore overnight. In the morning I discovered it had actually restored from an old backup dated 17 February 2013! And all the backups from that date forward appeared as blank pages inside Time Machine. It actually restored that old backup, then made several backups of the system it just restored. So in time machine I have several accessible backups of the old system (backups made today). Inaccessible backups which appear as blank pages inside time machine from 17 November all the way back to 17 February 2013. All backups prior to this date are accessible in Time Machine.
    I have tried updating the operating system, so I am now running a fully functioning version of OSX 10.10.1, but this did not enable me to acces the recent backups. When I actually browse the backup disc using Finder I can see the backup files I want to restore the system from all appear to be there. When I go back into Time Machine the dates of these backups all appear on the time line along the right hand side, but for some reason I just cannot access them.
    Please help, I have no idea how to restore my system.
    MacBook Pro (13-inch, Mid 2010)
    2.66 GHz Intel Core 2 Duo
    4 GB 1067 MHz DDR3

    While in Time Machine, press the key combination shift-command-C. The front window will show all mounted volumes. All snapshots should now be accessible. Select the one you want and navigate to the files you want to restore.

  • Lost the ability to Spotlight Index my Time Machine drive

    I have an external, Firewire Time Machine drive which has been working without problems up to now. This evening I had a backup which hung up in the "preparing" stage (no file transfers begun yet). When I went to look in the console, there was a device error apparently related to trying to detect the powered-on state of my Time Machine drive. Apparently Time Machine did not handle this gracefully. In the course of trying to clear that I got into a state where I had to force shutdown of the system (holding the power button). (I accidentally clicked on the Time Machine icon which got hung up trying to display the histories, and left me with no access to the Desktop....)
    Things appeared to check out fine when I brought the machine back up (including Verify Disk of both the main and Time Machine drives and Repair Permissions of the main drive), and I finally did a Back Up Now in Time Machine. Due to the forced shut down, this became a "Deep Traversal" "preparing"stage. We'll I've seen those before, so no worries. However it lasted quite a bit longer than it should, at which point I noticed that Spotlight was indexing the Time Machine drive.
    So at this point I dragged the Time Machine into the Spotlight Privacy list. Rather than going away completely as I expected, the indexing of the Time Machine drive apparently went into some sort of clean-up phase that said it was still indexing for another 5 minutes (where it had, just prior, said it was going to be indexing for another 2 hours). The progress bar advanced normally as if it really did do 5 minutes more of indexing of the Time Machine drive. I've not seen this before
    When that finished, the backup which had been "preparing" during all of this also finished "preparing", transferred the several MB of files I expected, and finished normally. There were no errors in the console related to any of this.
    I rebooted, and once again did a pair of Disk Verifies and a Repair Permissions without problems. Opened up the console to track things, and poked around in the Time Machine. All was normal as far as I can tell. I also explored the Time Machine drive via the Finder. No problems.
    So I now went into Spotlight Privacy and removed the Time Machine drive from the privacy list expecting it to do the re-indexing I had stopped above. Spotlight started indexing the drive and a couple seconds later it stopped. I tried again -- into and out of privacy -- same result, a couple seconds of indexing and then it stopped.
    At this point I noticed the console was saying I had some bus errors in the I/O system, and that's what was terminating the md worker process and stopping the indexing.
    So I shut down, unplugged the Time Machine drive, and went through my maintenance ritual.
    I reset the PMU (this is a powerbook), reset PRAM, booted once in Safe Mode, booted normally, and ran Disk Utility again to Verify and Repair Permissions on the main hard drive. All of that went without a hitch. No failures, faults or funnies.
    I ran through the list of Applications I use, keeping an eye on the console. Again no problems.
    So I shut down, plugged the Time Machine drive back in and booted back up. I put the drive into Spotlight Privacy and turned off Time Machine backups. I then did a Verify Disk on that drive. No problems. I went into the Time Machine history display. No problems. And no problems looking at it in the Finder either. In particular, no bus errors or anything else funny in the console.
    I rebooted and did a new Back Up Now. It completed without problems. It was another Deep Traversal backup due to the Safe Mode Boot, but it went without a hitch. I rebooted and did another Back Up Now and got a normal speed incremental backup again without a hitch. The bottom line is that as far as I can see that Time Machine drive is working just fine.
    So I went into Spotlight Privacy and removed it from the list. Once again it started to index and stopped in a couple seconds. But this time there were NO Console error messages.
    I moved my main hard drive into Spotlight Privacy and removed it and it re-indexed from scratch just fine. Tried again with the Time Machine drive -- indexing stopped in a couple of seconds with no message in the Console. Spotlight searches find all the right stuff in the main drive. Spotlight and finder searches find only the top level Time Machine folders in the Time Machine drive.
    I also tried removing the Spotlight plist from my account's Library / Preferences. Spotlight created a new plist as expected but it still won't index that darned Time Machine drive.
    Apparently there is something left over from when I originally aborted the Spotlight indexing of that drive which is causing Spotlight to think it has no work to do. I'm not seeing any I/O errors of any sort any more (I think my maintenance pass took care of that) and Time Machine backups and history access continue to work just fine. And again, the Time Machine disk Verifies just fine.
    So I've run out of things to try.
    Is there a hidden file that I need to remove from that drive so that Spotlight no longer thinks it already has it indexed?
    --Bob

    Well unfortunately the command
    sudo mdutil -E /Volumes/MyDiskName
    didn't help.
    The command itself echoed the name of the volume and then said "Indexing Enabled", which looked good. But the Spotlight indexing stopped after a couple seconds. The Console reported the Terminal sudo command and nothing else.
    I tried moving the Time Machine drive in and out of Spotlight privacy and once again the indexing started and stopped a couple seconds later with no Console messages.
    I then tried another trick I've learned to make Spotlight indexing happen which is to do a Finder search for, say, all folders (limited to the one drive) via Command-f and while Including both System Files and files both Visible and Invisible. And indeed Spotlight indexing started but again stopped a few seconds later.
    However, this time there were console messages and a crash report.
    The Console shows (with personal information x'ed out):
    12/31/07 1:30:38 PM mds[28] (/)(Error) IndexCI in openindex_filelazy:open file error: 2, 0.indexGroups
    12/31/07 1:30:41 PM ReportCrash[146] Formulating crash report for process mds[28]
    12/31/07 1:30:42 PM com.apple.launchd[1] (com.apple.metadata.mds[28]) Exited abnormally: Bus error
    12/31/07 1:30:42 PM com.apple.launchd[1] (0x10ba40.mdworker[96]) Exited: Terminated
    12/31/07 1:30:42 PM com.apple.launchd[1] (0x1004a0.mdworker[108]) Exited: Terminated
    12/31/07 1:30:42 PM mds[147] (/Volumes/Xxxxxx Time Machine/.Spotlight-V100/Store-V1/Stores/80F3EC85-D77A-49FE-8BDC-BB7C3B3EC1CF)(E rror) IndexCI in ContentIndexOpenBulk:Unclean shutdown of /Volumes/Xxxxxx Time Machine/.Spotlight-V100/Store-V1/Stores/80F3EC85-D77A-49FE-8BDC-BB7C3B3EC1CF/0. ; needs recovery
    12/31/07 1:30:43 PM ReportCrash[146] Saved crashreport to /Library/Logs/CrashReporter/mds2007-12-31-133038Xxxxxx-Xxxxxx-Computer.crash using uid: 0 gid: 0, euid: 0 egid: 0
    The Crash Report reads as follows (again with personal information x'ed out):
    Process: mds [28]
    Path: /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Support/mds
    Identifier: mds
    Version: ??? (???)
    Code Type: PPC (Native)
    Parent Process: launchd [1]
    Date/Time: 2007-12-31 13:30:38.746 -0500
    OS Version: Mac OS X 10.5.1 (9B18)
    Report Version: 6
    Exception Type: EXCBADACCESS (SIGBUS)
    Exception Codes: KERNPROTECTIONFAILURE at 0x0000000000000030
    Crashed Thread: 15
    Thread 0:
    0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
    1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
    2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
    3 mds 0x00059ab8 0x1000 + 363192
    4 mds 0x0000cfa0 0x1000 + 49056
    5 mds 0x00005580 0x1000 + 17792
    Thread 1:
    0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
    1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
    2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
    3 mds 0x00059ab8 0x1000 + 363192
    4 mds 0x0005987c 0x1000 + 362620
    5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
    6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
    Thread 2:
    0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
    1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
    2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
    3 mds 0x00059ab8 0x1000 + 363192
    4 mds 0x0005987c 0x1000 + 362620
    5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
    6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
    Thread 3:
    0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
    1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
    2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
    3 mds 0x00059ab8 0x1000 + 363192
    4 mds 0x0005987c 0x1000 + 362620
    5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
    6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
    Thread 4:
    0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
    1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
    2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
    3 mds 0x00059ab8 0x1000 + 363192
    4 mds 0x0005987c 0x1000 + 362620
    5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
    6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
    Thread 5:
    0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
    1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
    2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
    3 mds 0x00059ab8 0x1000 + 363192
    4 mds 0x0005987c 0x1000 + 362620
    5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
    6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
    Thread 6:
    0 libSystem.B.dylib 0x92eda3ec _semwaitsignal + 12
    1 libSystem.B.dylib 0x92f16fa0 pthread_condwait + 1580
    2 mds 0x00009648 0x1000 + 34376
    3 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
    Thread 7:
    0 libSystem.B.dylib 0x92ee0ea0 read$UNIX2003 + 12
    1 mds 0x000091b4 0x1000 + 33204
    Thread 8:
    0 libSystem.B.dylib 0x92f15438 kevent + 12
    1 mds 0x0007e584 0x1000 + 513412
    Thread 9:
    0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
    1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
    2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
    3 mds 0x00059ab8 0x1000 + 363192
    4 mds 0x0005987c 0x1000 + 362620
    5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
    6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
    Thread 10:
    0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
    1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
    2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
    3 mds 0x00059ab8 0x1000 + 363192
    4 mds 0x0005987c 0x1000 + 362620
    5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
    6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
    Thread 11:
    0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
    1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
    2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
    3 mds 0x00059ab8 0x1000 + 363192
    4 mds 0x0005987c 0x1000 + 362620
    5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
    6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
    Thread 12:
    0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
    1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
    2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
    3 mds 0x00059ab8 0x1000 + 363192
    4 mds 0x0005987c 0x1000 + 362620
    5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
    6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
    Thread 13:
    0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
    1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
    2 com.apple.spotlight.index 0x00207f0c _handleExceptions + 208
    3 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
    Thread 14:
    0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
    1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
    2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
    3 mds 0x00059ab8 0x1000 + 363192
    4 mds 0x0005987c 0x1000 + 362620
    5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
    6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
    Thread 15 Crashed:
    0 com.apple.spotlight.index 0x002046cc ContentIndexContainsContentByDocId + 204
    1 com.apple.spotlight.index 0x00164358 QueryFunctionCallbackContext::findContent(db_obj*, __CFString const*, char*, int) + 244
    2 com.apple.spotlight.index 0x001634d0 qpContentIndexMatch(datastoreinfo*, dblazyobj*, query_piece*, void*, int) + 328
    3 com.apple.spotlight.index 0x0015587c comparefile_againsttree + 828
    4 com.apple.spotlight.index 0x00155d30 comparefile_againsttree + 2032
    5 com.apple.spotlight.index 0x00155d5c comparefile_againsttree + 2076
    6 com.apple.spotlight.index 0x001e307c -[SISearchCtx isObjectInQuery:withQuery:shortcut:] + 144
    7 com.apple.spotlight.index 0x001fa268 -[SISearchCtx_FSWalk performSearch:] + 996
    8 com.apple.spotlight.index 0x001e2cbc -[SISearchCtx executeSearchContextCracked_2:jobNum:] + 136
    9 com.apple.spotlight.index 0x00177e80 siwork_queueprocess + 752
    10 com.apple.spotlight.index 0x0017811c sischeduleronce + 356
    11 com.apple.spotlight.index 0x0017816c sischeduleronce + 436
    12 com.apple.spotlight.index 0x001784f8 sischeduler_run_waitingtimeout + 640
    13 com.apple.spotlight.index 0x0016529c runLoop + 72
    14 com.apple.spotlight.index 0x00165308 query_runLoop + 32
    15 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
    Thread 15 crashed with PPC Thread State 32:
    srr0: 0x002046cc srr1: 0x0200f030 dar: 0x00000030 dsisr: 0x40000000
    r0: 0x002046a4 r1: 0xf09a4380 r2: 0x00000000 r3: 0x00000000
    r4: 0xf09a43c0 r5: 0x00000000 r6: 0x000074d1 r7: 0x00000000
    r8: 0x003fc080 r9: 0x00000000 r10: 0x00000000 r11: 0x44000444
    r12: 0x92ede094 r13: 0x00000000 r14: 0x00000000 r15: 0x00373410
    r16: 0x00000000 r17: 0x00239e98 r18: 0x00000001 r19: 0x00227b9c
    r20: 0x00000000 r21: 0x00245554 r22: 0x00000001 r23: 0x00000001
    r24: 0x00000000 r25: 0x00000005 r26: 0x00000000 r27: 0x00000000
    r28: 0x00000000 r29: 0x00000005 r30: 0xf09a43c0 r31: 0x00204610
    cr: 0x24000444 xer: 0x20000004 lr: 0x002046a4 ctr: 0x92ede094
    vrsave: 0x00000000
    Binary Images:
    0x1000 - 0xc1ffb mds ??? (???) <af9cc958b4b030835101ff024186c7d3> /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Support/mds
    0xde000 - 0xe0ffd com.apple.MDSChannel 1.0 (1.0) /System/Library/PrivateFrameworks/MDSChannel.framework/Versions/A/MDSChannel
    0x139000 - 0x23fffb com.apple.spotlight.index 10.5.0 (398.1) <5843125c709dd85f22f9bd42744beea5> /System/Library/PrivateFrameworks/SpotlightIndex.framework/Versions/A/Spotlight Index
    0x1ca9000 - 0x1caaffc liblangid.dylib ??? (???) <5f078ac1f623f5ce432ea53fc29338c0> /usr/lib/liblangid.dylib
    0x2198000 - 0x22bdffb libmecab.1.0.0.dylib ??? (???) <cd875e74974e4ec3a0b13eeeb236fa53> /usr/lib/libmecab.1.0.0.dylib
    0x8fe00000 - 0x8fe309d3 dyld 95.3 (???) <a7be977c203ec5c76b2f25a7aef66554> /usr/lib/dyld
    0x90123000 - 0x9016effb com.apple.Metadata 10.5.0 (398) <b6bb1fd5a7a9135f546b2d8cbd65eafc> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
    0x901ab000 - 0x902d0ff3 com.apple.CoreFoundation 6.5 (476) <9073c2bfdf6842562c8b7f0308109c02> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x9060a000 - 0x90612fff libbsm.dylib ??? (???) <c1fca3cbe3b1c21e9b31bc89b920f34c> /usr/lib/libbsm.dylib
    0x90683000 - 0x90688ff6 libmathCommon.A.dylib ??? (???) /usr/lib/system/libmathCommon.A.dylib
    0x90757000 - 0x907d2fff com.apple.SearchKit 1.2.0 (1.2.0) <1b448fbae02460eae76ee1c6883f45d6> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
    0x9088a000 - 0x9090ffff libsqlite3.0.dylib ??? (???) <7b379cb4220346e99c32c427d4539496> /usr/lib/libsqlite3.0.dylib
    0x90aa7000 - 0x90ab5fff libz.1.dylib ??? (???) <1a70dd3594a8c5ad39d785af5da23237> /usr/lib/libz.1.dylib
    0x90b50000 - 0x90be2fff com.apple.framework.IOKit 1.5.1 (???) <591b8b0cc4261db98a6e72e38eef5f9a> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
    0x91105000 - 0x9116cffb libstdc++.6.dylib ??? (???) <a4e9b10268b3ffac26d0296499b24e8e> /usr/lib/libstdc++.6.dylib
    0x9116d000 - 0x912b5ff3 libicucore.A.dylib ??? (???) <250daed2fb2e6bf114480e2e4da0728b> /usr/lib/libicucore.A.dylib
    0x91c3c000 - 0x91d32ffc libiconv.2.dylib ??? (???) <05ae1fcc97404173b2f9caef8f8be797> /usr/lib/libiconv.2.dylib
    0x91d3a000 - 0x91db4ffd com.apple.CFNetwork 220 (221) <00b882d3d3325526b78ded74880759fe> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork
    0x9236a000 - 0x92382ffb com.apple.DictionaryServices 1.0.0 (1.0.0) <fe37191e732eeb66189185cd000a210b> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Diction aryServices.framework/Versions/A/DictionaryServices
    0x92383000 - 0x9238effb libgcc_s.1.dylib ??? (???) <ea47fd375407f162c76d14d64ba246cd> /usr/lib/libgcc_s.1.dylib
    0x92742000 - 0x92769fff libxslt.1.dylib ??? (???) <3700d04090629deddb436aa2d516c56d> /usr/lib/libxslt.1.dylib
    0x92777000 - 0x92860fff libxml2.2.dylib ??? (???) <6f383df1e1e775be0158ba947784ae13> /usr/lib/libxml2.2.dylib
    0x928aa000 - 0x928b9fff com.apple.DSObjCWrappers.Framework 1.2 (1.2) <2411674c821a8907449ac741ce6a40c3> /System/Library/PrivateFrameworks/DSObjCWrappers.framework/Versions/A/DSObjCWra ppers
    0x92a17000 - 0x92afafeb libobjc.A.dylib ??? (???) <4a90e315bd1718c3f5ae09ee6c23e36c> /usr/lib/libobjc.A.dylib
    0x92afb000 - 0x92bc9ff7 com.apple.CoreServices.OSServices 210.2 (210.2) <bad4943629f870d305f2bc7c6dfffe2d> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
    0x92bde000 - 0x92dbfffb com.apple.security 5.0.1 (32736) <15632bf9bbdb223194b3d79a2e48e02d> /System/Library/Frameworks/Security.framework/Versions/A/Security
    0x92e9a000 - 0x92ec5ff7 libauto.dylib ??? (???) <c1f2bd227817ad7c7bf29ec74729ac7c> /usr/lib/libauto.dylib
    0x92ed2000 - 0x9306bfe3 libSystem.B.dylib ??? (???) <8a6cd873dfa7ada786efac188f95ed1b> /usr/lib/libSystem.B.dylib
    0x931a7000 - 0x934a7ff3 com.apple.CoreServices.CarbonCore 783 (783) <fd2acaf23e95472f78b8a077fa039986> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
    0x946f2000 - 0x9472afff com.apple.SystemConfiguration 1.9.0 (1.9.0) <d925dde7699e6231c88a41b0254a7591> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
    0x94933000 - 0x9494eff3 com.apple.DirectoryService.Framework 3.5 (3.5) <3246a5d1c6a3d678798a90e8c5cd3677> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryServi ce
    0x9494f000 - 0x9494fffa com.apple.CoreServices 32 (32) <42b6dda539f7411606187335d9eae0c5> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
    0x94c68000 - 0x94c9dfff com.apple.AE 402 (402) <a4b92c8ac89cc774b85fb44c48b9d882> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.fram ework/Versions/A/AE
    0x96831000 - 0x9683afff com.apple.DiskArbitration 2.2 (2.2) <9c8f8ade43fa25b32109ef9dcc0cb5d5> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
    0x9683b000 - 0x968d1ff7 com.apple.LaunchServices 286 (286) <a3a0b2af862e9a8945072f8cb523678f> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
    0x969bc000 - 0x96c00ffb com.apple.Foundation 6.5.1 (677.1) <4152239382fb0f48abbcbf35bd04afa6> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
    0xfffec000 - 0xfffeffff libobjc.A.dylib ??? (???) /usr/lib/libobjc.A.dylib
    0xffff8000 - 0xffff9703 libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib
    Apparently the mdutil command didn't actually delete the Spotlight index file which is causing the problem, or at least didn't leave the indexing files in a consistent, empty state to start indexing over again. I may have to Erase this Time Machine disk and start over.
    I should point out that except for Spotlight indexing this disk is otherwise working just fine. It passes Verify Disk with no errors and both new Time Machine backups and viewing and restoring via Time Machine and Finder work without problem.
    Any suggestions before I just Erase the disk and start over with a new backup?
    --Bob

  • Time Machine - TROUBLESHOOTING

    This article provides some troubleshooting tips for common Time Machine errors and problems.
    It does not cover problems specific to Time Capsule or other wireless backups. See the Airport and Time Capsule forum, in the Digital Life section.
    Nor does it include general information about Time Machine. For those, see the Frequently Asked Questions *User Tip* at the top of this forum.
    _*C o n t e n t s*_
    *Section A. _TOOLS YOU MAY NEED*_
    *A1. Time Machine Buddy widget*
    *A2. Time Tracker*
    *A3. Tinker Tool*
    *Section B. _SET - UP PROBLEMS*_
    |
    *B1. I can't select my drive for use with Time Machine*
    *B2. The Change Disk option doesn't work*
    *B3. No last or oldest backup date shown*
    *B4. Wrong icon shown for TM drive/partition on desktop and/or Finder sidebar*
    *Section C. _BACKUP FAILURES*_
    |
    *C1. Initial Backup Failed*
    *C2. Other Backup Fails*
    *C3. "An error occurred while copying files to the backup volume"* or *"Aborting backup because indexing a file failed"*
    *C4. "This backup is too large"*
    *C5. "You do not have appropriate access privileges to save file “.<nnnnnnn>” in folder <Name>"*
    *C6. The backup volume is read only*
    *C7. "Error (12): Link of previous volume failed."*
    *C8. Backup fails after Logic Board replacement*
    *C9. "The back-up disk image could not be created."*
    *C10. Error: (-50) Creating directory*
    *C11. Drive does not appear to be the correct backup volume for this computer (Cookies do not match)*
    *Section D. _OTHER PROBLEMS RUNNING BACKUPS*_
    |
    *D1. Stuck in Preparing*
    *D2. Backup is Slow or "hung"*
    *D3. TM is doing a full backup for no good reason*
    *D4. My backups seem too large*
    *Section E. _PROBLEMS VIEWING, RESTORING, or DELETING BACKUPS*_
    |
    *E1. Backups were deleted unexpectedly*
    *E2. I can't see some backups*
    *E3. I can't see backups for a disk/partition that's no longer connected*
    *E4. Time Machine Interface ("Star Wars") won't display properly, or crashes*
    *Section A. _TOOLS YOU MAY NEED*_
    There are some free 3rd-party tools that may be useful in diagnosing problems with Time Machine. You'll see references to them in several places below.
    _*A1. Time Machine Buddy widget*_
    |
    Click here to download the +*Time Machine Buddy*+ widget.
    It shows the messages from your logs for one TM backup run at a time, in a small window. An explanation of some of the error messages is in section #C2 below. Other common messages are explained in item #7 of the Frequently Asked Questions *User Tip* at the top of this forum.
    You can copy these messages by selecting them via dragging your mouse over them (be sure to get them all, as they may overflow the small window), then pressing CMD-C. This copies them to your "clipboard," so you can post them in a thread here (via CMD-V) to get help diagnosing a problem. (Occasionally, the widget won't let you copy while a backup is running.)
    If the message area is blank, but you know there were backups, your user account may not have permission to view your logs. Try signing-on as an Admin User. You can grant "read" rights to the folder /var/log for the other user.
    Note that the widget may only let you look back a few days. If you need to look back farther, you'll need the Console app (in your Applications/Utilities folder) to look at your older system logs (named +*system.log.1.bz2, system.log.2.bz2,+* etc). Click +*Show Log List*+ in the toolbar, then navigate to the desired logs in the sidebar that opens up. You can select only the messages from TM backups by typing backupd in the Filter box in the toolbar.
    |
    _*A2. Time Tracker*_
    |
    Click here to download the TimeTracker app. It shows most of the files saved by TM for each backup (excluding some hidden/system files, etc.). This can help you figure out just what is (or is not) being backed-up.
    |
    _*A3. Tinker Tool*_
    |
    Click here to download the +*Tinker Tool*+ app. It allows you to change the Finder to show hidden files (among many other things). Select the first option under Finder, then click +Relaunch Finder+ at the bottom. Reverse this when done.
    Do not use any of the other options unless you know the possible consequences.
    |
    *Setcion B. _SET - UP PROBLEMS*_
    _*B1. I can't select my drive for use with Time Machine*_
    If the drive/partition you want to use for TM backups doesn't appear in the list when you select TM Preferences > Change Disk, it's probably not formatted correctly. See item #C1 for help determining whether it's right, and how to fix it.
    |
    _*B2. The Change Disk option doesn't work*_
    If the +*Change Disk*+ button in TM Preferences doesn't do anything, try turning-off the +*Back To My Mac*+ application temporarily.
    |
    _*B3. No last or oldest backup date shown*_
    |
    If these dates don't appear when selecting the TM icon in your Menubar, or TM Preferences, try the following:
    1. Do a +*Back Up Now.*+ That will often recover the info.
    2. De-select your TM Drive via TM Preferences (select "none"), quit System Preferences, then re-select it and do a +*Back Up Now.*+
    3. A Log Out or Restart may fix it.
    4. If they're still not shown, try a *"Full Reset:"*
    |
    a. Turn TM Off, de-select the drive (select "none"), note any exclusions in Options, quit System Preferences.
    b. Eject, disconnect, and power-off the drive for a few moments, then reconnect it.
    c. Delete the file /Library/Preferences/com.apple.TimeMachine.plist (in your top-level Library folder, not your home folder).
    d. Re-select your drive (and re-enter any exclusions).
    e. Do a +*Back Up Now*+ or wait for the next scheduled backup.
    |
    _*B4. Wrong icon shown for TM drive/partition on desktop and/or Finder sidebar*_
    |
    Try de-selecting, then re-selecting the "Show" option in Finder > Preferences > General and/or Sidebar.
    Try a "Full Reset" as in item #B3.
    |
    *Section C. _BACKUP FAILURES*_
    _*C1. Initial Backup Failed*_
    The most common cause is the TM drive not being formatted correctly (even, on occasion, if TM formatted it!). Use Disk Utility (in your Applications/Utilities folder) to verify the setup:
    First, select the second line for your internal HD (usually named "Macintosh HD"). Towards the bottom, the Format should be +Mac OS Extended (Journaled),+ although it might be +Mac OS Extended (Case-sensitive, Journaled).+
    Next, select the line for your TM partition (indented, with the name). Towards the bottom, the *Format must* be the same as your internal HD (above). If it isn't, you must erase the partition (not necessarily the whole drive) and reformat it with Disk Utility.
    Sometimes when TM formats a drive for you automatically, it sets it to +Mac OS Extended (Case-sensitive, Journaled).+ Do not use this unless your internal HD is also case-sensitive. All drives being backed-up, and your TM volume, should be the same. TM may do backups this way, but you could be in for major problems trying to restore to a mis-matched drive.
    Last, select the top line of the TM drive (with the make and size). Towards the bottom, the *Partition Map Scheme* should be GUID (preferred) or +Apple Partition Map+ for an Intel Mac. It must be +Apple Partition Map+ for a PPC Mac. If this is wrong, you must completely erase the disk and reformat it. See item 5 of the Frequently Asked Questions *User Tip* at the top of this forum.
    Once you're sure your disk/partition is formatted correctly, if your backups still fail, continue to the next item:
    |
    _*C2. Other Backup Fails*_
    If this is your first backup, or the first one to a new external drive/partition, the most common cause is the drive not being formatted properly (even, on occasion, when Time Machine formatted it for you!). So if there's any question, see the previous item.
    If a backup fails, note any message it sends, and start with this Apple article: Troubleshooting Time Machine backup issues. It includes a wide range of problems, and has links to many other Apple technical articles.
    Those messages/problems are not repeated here, except for a couple that Apple doesn't cover completely.
    If that doesn't solve your problem, get the Time Machine Buddy messages (see #A1). Many of the common and normal messages are detailed in item 7 of the Frequently Asked Questions *User Tip* at the top of this forum. Only the ones that might indicate a problem are repeated here.
    *Messages that might indicate trouble:*
    Event store UUIDs don't match naming your internal HD (or any other drive/partition being backed-up). TM can't be sure the OSX internal log of file changes that it normally uses is correct. This is seen on your first backup of a disk, or after an improper shutdown, a full restore, certain hardware repairs, removal of certain exclusions, a large volume of changes (such as an OSX update), or many days without a successful backup. It may cause a lengthy backup, so if you see it frequently, without a good reason, you need to figure out why.
    Event store UUIDs don't match naming an external drive/partition. TM isn't sure that everything on it is what TM expects. This may be because the drive was disconnected improperly, or it doesn't appear to be the drive TM expects. Again, if you see this without a good reason, investigate.
    . . . node requires deep traversal. Instead of the log of file changes TM normally uses, it must examine every file and folder on the named drive/partition, and compare it to the last backup, to figure out what's changed and needs to be backed-up. Obviously, this is a lengthy procedure; and especially lengthy if you're doing wireless backups. As this is part of the "Preparing" phase, you may not see any more messages for quite a while. Try not to interrupt the backup, as this must be done again (and again) until a backup is completed successfully.
    Error: backup disk is full - all nn possible backups were removed, but space is still needed. This is pretty clear. TM deleted as many old backups as it could (and they're all listed in the first failed backup's messages). See item #C4.
    Bulk setting Spotlight attributes failed. or Waiting for index to be ready. There may be a problem with your TM drive, or difficulty communicating with it. See item #D2.
    Error: (-36) SrcErr:YES Copying {a file path} to {"null" or another file path}
    or Indexing a file failed. Returned -12 for: {a file path}, {another file path}
    These may indicate a problem with the first file referenced. See the next item.
    If you don't see any of these messages, or nothing here seems to help, copy and post all the messages from the failed backup in a new thread here, along with specifics of your set up.
    |
    _*C3. "An error occurred while copying files to the backup volume"* or *"Aborting backup because indexing a file failed"*_
    Occasionally, backups will fail with this message for no good reason, and the next one will complete normally. So either wait for the next scheduled backup, or do a +*Back Up Now*+ from the TM icon in your Menubar, or by control-clicking (right-clicking) the TM icon in your dock. If that backup completes normally, there's no real problem.
    If the next one fails also, then there most likely is something wrong -- the question is, what?
    Get the Time Machine Buddy messages (see #A1). Look for the message(s) about a file that couldn't be copied, such as:
    |
    Error: (-36) SrcErr:YES Copying {a file path} to {"null" or another file path}
    or Indexing a file failed. Returned -12 for: {a file path}, {another file path}
    |
    If you're not familiar with file "paths," it can be a little difficult to read these messages. They look something like this:
    /Users/<Name>/iMovie Events.localized/clip-2008-04-02.mov to /Volumes/TM Backups/ . . . etc.
    The end of the file in question is usually indicated either by " to " or just a comma and space before the next one.
    If it's a file you're sure you don't need, you can delete it. If not, for now, don't touch it. Instead, exclude it from TM:
    Go to TM's Preferences and click Options.
    In the next panel, click the plus sign at the bottom.
    In the sidebar of the next panel, select your computer name, internal HD, or home folder as necessary; then navigate to the file listed, or, perhaps, it's enclosing folder.
    Select it, click Exclude, then Done.
    Then do a +*Back Up Now*+ from the TM icon in your Menubar, or by control-clicking (right-clicking) the TM icon in your dock.
    If the backup runs ok, then you need to figure out what's wrong with that file.
    If it fails again, check it's messages. If it's the *exact same* file, you didn't exclude the right one, or you need to do a "full reset" (see item #B3).
    If you get the same message for a different file, you may need stronger stuff:
    a. Exclude your TM disk from any anti-virus scanning.
    b. Also exclude it from Spotlight indexing, via System Preferences > Spotlight > Privacy.
    c. Do a +*Repair Disk*+ (not permissions) on your TM drive/partition, via Disk Utility (in your Applications/Utilities folder).
    d. If the original file is on an external disk, do a +*Repair Disk*+ on it, too.
    e. If the original file is on your internal HD, do a +*Verify Disk*+ (not permissions) on it. If that reports errors, you'll have to boot from your Leopard Install disc and use it's copy of Disk Utility to repair it:
    1. Insert your Leopard Install disc and restart while holding down the "C" key. This will take a few moments.
    2. Select your language when prompted.
    3. On the next screen select Utilities in the Menubar, then +*Disk Utility.*+
    4. Do a +*Repair Disk*+ on your internal HD. If it doesn't fix all the errors, run it again (and again), until it either fixes them all, or can't fix any more.
    5. Reboot normally.
    If all else fails, you may have a problem with the drive, or communicating with it. Try all the suggestions in #D2 below.
    |
    _*C4. "This backup is too large"*_
    |
    For one reason or another, TM is out of room on the backup disk/partition. When it's space gets near full, TM will normally delete as many old and expired backups as it can to make room for new ones.
    There are some backups that Time Machine *will not delete,* however. It won't delete the most recent backup, or any backups from a different Mac. Sometimes TM will start a new "sequence" of backups, as if you had a different Mac, and it won't delete any from the prior sequence, either.
    Also note that, although it deletes a backup, it doesn't necessarily delete it's copies of all the items that were on that backup. It only deletes it's copies of items that no longer exist on any other backup. Thus you won't lose the backup of anything that's currently on your system.
    When this happens, you have a few options:
    1. De-select the +*Warn when old backups are deleted*+ option in TM Preferences > Options, and try again.
    2. Erase the TM disk/partition and let TM start over, with a new, full backup of your entire system.
    3. Manually delete some old backups via the TM interface (do not use the Finder!). This is rather tedious, as it must be done one at a time, and there's no way to tell in advance which ones will be quick (and not gain much room) and which will take a long time and recover more space. See item #12 of the Frequently Asked Questions *User Tip* at the top of this forum for detailed instructions.
    4. Get a different disk/partition for your Time Machine backups. Then either:
    Give it a different name, and use the +Change Disk+ button in TM Preferences to select it. Let TM start fresh on the new drive/partition, with a full backup of your entire system. Keep the old drive/partition for a while (disconnected) until you're sure everything is working and you don't need the old backups anymore.
    Or, duplicate the current backups to it via the Restore tab of Disk Utility in your Applications/Utilities folder. Note that you must duplicate an entire disk/partition to another entire disk/partition. See item #18 in the Frequently Asked Questions *User Tip* at the top of this forum for detailed instructions.
    |
    _*C5. "You do not have appropriate access privileges to save file “.<nnnnnnn>” in folder <Name>"*_
    |
    Open the Terminal app (in your Applications/Utilities folder).
    Be extremely careful when using Terminal. It is a direct interface into UNIX, the underpinning of OSX. Unlike the Finder, there are few protections against making a mistake, which can cause untold damage.
    In Terminal, the prompt looks like this: user-xxxxxx:~ <your name>$
    (where <your name> is your short user name). It's followed by a non-blinking block cursor (unless it's been changed via Terminal > Preferences).
    At the prompt, type the following exactly as shown in the example, substituting the name of your TM drive exactly, including any spaces, between the quotes; and the string of numbers & letters from the message where the series of x's are (keep the dot):
    <pre> *sudo chmod 644 /volumes/"TM drive name"/.xxxxxxxxxxxx*</pre>
    example: *sudo chmod 644 /volumes/"TM Backups"/.0a1b2c3d4e5f*
    Press Return. You'll get some warnings and a request for your Administrator's password. Type it in (it won't be displayed) and press Return again.
    Then try a +*Back Up Now*+ from the TM icon in your Menubar, or by control-clicking (right-clicking) the TM icon in your dock.
    |
    _*C6. The backup volume is read only*_
    First, follow the Apple article mentioned above: Troubleshooting Time Machine backup issues.
    If that doesn't correct it,
    If you only have a partial backup, or don't need the ones you've done, the simplest thing to do is just erase the disk/partition with Disk Utility (in your Applications/Utilities folder).
    If you don't want to erase it, here's a workaround:
    First, you need to find the name of the hidden file that's causing the problem. If the Time Machine Buddy (see #A1) shows a message like the one in item #C5, follow the instructions there.
    If not, use the TinkerTool app (see #A3) to show hidden files.
    In a Finder window, select your Time Machine drive/partition. The very first file shown should have a name consisting of a period (dot) followed by 12 numbers and/or letters. (This is your Mac's Ethernet address). Copy or make a note of it.
    Then follow the rest of the instructions in item #C5.
    |
    _*C7. "Error (12): Link of previous volume failed."*_
    |
    This usually happens when you replaced a drive with a different one, but with the same name as the original.
    Because of the way Time Machine keeps track of drives, at one point it thinks they're the same, but later on realizes they aren't.
    Either rename the drive (append "_2" or something), or delete all previous backups of it, via the instructions in item 12 of the Frequently Asked Questions *User Tip* at the top of this forum.
    And note that TM will probably do a full backup of the drive. If there isn't much space on your TM drive/partition, see #C4. You may need to do item 2, 3, or 4 listed there.
    |
    _*C8. Backup fails after Logic Board replacement*_
    The logic board contains your Ethernet "Mac Address", which is a unique number that TM uses to be sure it knows which Mac is which. So, to TM, it is now a *different computer.*
    This is so it can keep each Mac's backups separate (you can back multiple Macs up to the same external disk or Time Capsule). It does this by putting a hidden file containing this address on the TM disk.
    There is a fairly elaborate way to attempt to persuade TM that the existing backups really are for your "new" Mac: http://www.macosxhints.com/article.php?story=20080128003716101
    It is very easy to make an error with Terminal, get no error message, and have it not work, or worse, so try it at your own risk.
    But there is an alternative: hold down the Option key while selecting the TM icon in your Menubar, or control-click (right-click) the TM icon in your Dock. Then use the (badly named) +*Browse Other Time Machine Disks*+ option. It will take you into the normal TM interface where you can see and restore from the old set of backups.
    Even if you're successful with the Terminal work, your first backup with the new logic board may be a full one -- every file and folder on your system. If TM decides to do that, you cannot prevent it.
    So if your TM disk/partition isn't over twice the size of the data it's backing-up, your best bet may be to just erase it with Disk Utility (in your Applications/Utilities folder) and let TM start over.
    |
    _*C9. "The back-up disk image could not be created."*_
    |
    If you get this message when backing-up wirelessly, check your +*System Name*+ at the top of the System Preferences > Sharing panel.
    It must not be blank; it should not be more than 25 characters long; and you should avoid punctuation (except periods and underscores), and unusual characters.
    |
    _*C10. Error: (-50) Creating directory*_
    |
    This may indicate a problem with your TM drive. Use Disk Utility (in your Applications/Utilities folder) to do a +*Repair Disk*+ (not permissions) on it. If any errors are found that Disk Utility can't fix, run it again (and again) until they're all fixed or it can't fix any more.
    If no errors are found, or they're all found and fixed, but you still get the message, try a "full reset" as in item #B3.
    If Disk Utility can't fix them all, the disk may be failing. Copy the messages from the last run of Disk Utility and post them in a new thread in this forum for advice.
    |
    _*C11. Drive does not appear to be the correct backup volume for this computer(Cookies do not match)*_
    |
    If this happens after getting a new Logic Board, see item #C8.
    This also happens on occasion after switching a TM drive from one Mac to another, erasing your TM disk/partition, or attaching a new TM drive with the same name as an old one.
    You can usually fix this by simply re-selecting your TM drive in TM Preferences > Change Disk.
    If that doesn't help, try a complete reset. See item #B3.
    |
    *Section D. _OTHER PROBLEMS RUNNING BACKUPS*_
    _*D1. Stuck in Preparing*_
    |
    See this Apple Support document: Time Machine may display "Preparing" for a longer time
    Try not to interrupt the backup, as this procedure must be done again (and again) until a backup is completed successfully.
    Also see the next topic:
    |
    _*D2. Backup is slow or "hung"*_
    |
    Get the Time Machine Buddy messages (see #A1).
    If it shows Event store UUIDs don't match
    and/or . . . node requires deep traversal, it may not be "hung" at all. See item #C2.
    If it shows Waiting for index to be ready and/or Bulk setting Spotlight attributes failed messages, there may be a problem with your TM drive, or difficulty communicating with it. Unfortunately, any of a number of things may cause this. The list of things to try is:
    1. Exclude your TM disk/partition from any anti-virus scanning.
    2. Exclude it from Spotlight (System Preferences > Spotlight > Privacy).
    _*If backing up to a Time Capsule or External Disk connected to an Airport Extreme:*_
    3. Check your System Name via System Preferences > Sharing. It it's blank, that's likely the problem. If it's over 26 characters long, trim it. If it has any unusual characters, try removing them.
    4. Try moving the TC or AEBS and Mac closer together.
    5. Look for interference with another wireless device. Turn anything else off, or move it farther away.
    6. Try repairing the Sparse Bundle with Disk Utility (in your Applications/Utilities folder). Mount the Sparse Bundle, then drag it into the Disk Utility sidebar, then use +*Repair Disk*+ (not permissions).
    _*If backing up to an External hard drive:*_
    7. Do a +*Repair Disk*+ (not permissions) on it via Disk Utility (in your Applications/Utilities folder).
    8. At least temporarily, de-select +*Put the hard disk(s) to sleep ...+* in System Preferences > Energy Saver.
    9. Be sure it's connected directly to your Mac (no hubs, and not the USB port on the keyboard).
    10. Try different port(s), cable(s).
    11. See if your drive has an automatic sleep or "spin down" feature you can disable.
    12. Check the maker's web site (support or forum) for any updates.
    If nothing helps, your drive may be failing.
    |
    _*D3. TM is doing a full backup for no good reason*_
    Time Machine may do a full backup after any of the following:
    Using a new disk or partition for backups (always).
    A full restore (probably).
    Some hardware repairs, especially a new internal hard drive (probably) or logic board (always, but see #C8).
    Changing your computer's name via System Preferences > Sharing (probably).
    Renaming a disk/partition that's being backed-up (probably).
    Going several days without a backup (probably; also seems to depend on the volume of changes).
    Exactly why it doesn't always do full backups for the items marked "probably" is not clear, so to be safe, assume it will.
    |
    _*D4. My backups seem too large*_
    |
    Time Machine may be doing a full backup of your entire system. See item #D3.
    Doing an OSX update can cause a large backup, as it may add or update several thousand files.
    Removing exclusions, such as your top-level System and/or Library folders, can be sizeable.
    Renaming a folder or disk drive, or moving a file or folder, will cause the entire item moved or renamed to be backed-up. This includes all files and sub-folders in a moved or renamed folder.
    There are some OSX features and 3rd-party applications that cause large Time Machine backups. Common ones are FileVault, vmWare Fusion, Parallels Desktop, Entourage, and Thunderbird. Any application that uses a single large file or database may do this. See item 9 of the Frequently Asked Questions post.
    You can use the +Time Tracker+ app (see item #A2) to see just what was copied on any particular backup. There may be ways to minimize the size of such backups; search and/or post in this forum for help.
    |
    *Section E. _PROBLEMS VIEWING, RESTORING, or DELETING BACKUPS*_
    _*E1. Backups were deleted unexpectedly*_
    |
    Time Machine manages it's space for you, automatically. When it's drive/partition gets near full, it will begin deleting your oldest backups to make room for new ones. See item #C4 for more info and your options.
    Usually when this happens unexpectedly, it's because TM has done a new full backup, which of course requires a lot of space. See item #D3 for the common reasons.
    If in doubt, get the widget messages (see #A1). They'll show how much it was trying to back up. See item #7 of the Frequently Asked Questions *User Tip* at the top of this forum for explanation of those messages.
    |
    _*E2. I can't see some backups*_
    |
    TM keeps the backups for each Mac separate, and normally only shows the ones for the Mac it's running on, even if there are other Macs' backups on its disk/partition.
    Also, sometimes TM will start a new "sequence" of backups, as if they were from a different Mac. See item #D3.
    To see these "other" backups, you need the (badly named) +*Browse Other Time Machine Disks*+ option. It's available by holding down the Option key while selecting the TM icon in your Menubar, or by control-clicking (right-clicking) the TM icon in your Dock.
    You'll see a selection screen showing all the disks/partitions that have TM backups on them. Select the one you want, and you'll be taken to the normal TM "Star Wars" interface, where you should see all the backups on that disk/partition.
    Note that, unfortunately, you cannot merge or combine two different "sequences" of backups.
    Also note that you cannot use the normal Restore button at the bottom of the screen to restore items, since they're from a different Mac. Instead, select the desired item(s), then click the "Gear" icon in the Finder window's toolbar and select the +*Restore <item> to ...+* option. You'll then get a prompt to specify the destination.
    |
    _*E3. I can't see backups for a disk/partition that's no longer connected*_
    |
    Open a Finder window and press ShiftCmdC (or select your computer name in the Finder Sidebar).
    Then either +*Enter Time Machine*+ or +*Browse Other Time Machine Disks*+ (see #E2).
    On the first Finder window in the "cascade," labelled +*Today (Now),+* you'll see all the volumes currently attached to your Mac.
    Select the Finder window for any backup, and you'll see a folder for each drive/volume that was backed-up, including any that are no longer connected. Navigate from there to whatever you're looking for.
    |
    _*E4. Time Machine Interface ("Star Wars") won't display properly, or crashes*_
    |
    Do a +*Repair Disk*+ (not permissions) on your TM drive, via Disk Utility (in your Applications/Utilities folder).
    Re-select your TM drive via TM Preferences > Change Disk.
    If you're using Spaces, try disabling it, at least temporarily.
    If you have any sort of video out cable, especially HDMI, try disconnecting it, at least temporarily.
    Do a "complete reset" of TM, as in item #B3.

    This article provides some troubleshooting tips for common Time Machine errors and problems.
    It does not cover problems specific to Time Capsule or other wireless backups. See the Airport and Time Capsule forum, in the Digital Life section.
    Nor does it include general information about Time Machine. For those, see the Frequently Asked Questions *User Tip* at the top of this forum.
    _*C o n t e n t s*_
    |
    *Section A. _TOOLS and PROCEDURES YOU MAY NEED*_
    |
    *A1. Time Machine Buddy widget*
    *A2. Time Tracker*
    *A3. Tinker Tool*
    *A4. Full Reset of Time Machine*
    *A5. How to do a Repair or +Verify Disk+*
    *Section B. _SET - UP PROBLEMS*_
    |
    *B1. I can't select my drive for use with Time Machine*
    *B2. The +Change Disk+ button doesn't work*
    *B3. No last or oldest backup date shown*
    *B4. Wrong icon shown for TM drive/partition on desktop and/or Finder sidebar*
    *Section C. _BACKUP FAILURES*_
    |
    *C1. Initial Backup Failed*
    *C2. Other Backup Fails*
    *C3. "An error occurred while copying files to the backup volume"* or *"Aborting backup because indexing a file failed"*
    *C4. "This backup is too large"*
    *C5. "You do not have appropriate access privileges to save file “.<nnnnnnn>” in folder <name of TM drive>"*
    *C6. The backup volume is read only*
    *C7. "Error (12): Link of previous volume failed."*
    *C8. Backup fails after Logic Board replacement*
    *C9. "The back-up disk image could not be created."*
    *C10. Error: (-50) Creating directory*
    *C11. Drive does not appear to be the correct backup volume for this computer (Cookies do not match)*
    *Section D. _OTHER PROBLEMS RUNNING BACKUPS*_
    |
    *D1. Stuck in "Preparing" or "Calculating changes"*
    *D2. Backup is Slow or "hung"*
    *D3. TM is doing a full backup for no good reason*
    *D4. My backups seem too large*
    *Section E. _PROBLEMS VIEWING, RESTORING, or DELETING BACKUPS*_
    |
    *E1. Backups were deleted unexpectedly*
    *E2. I can't see some backups*
    *E3. I can't see or restore from backups for a disk/partition that's no longer connected*
    *E4. Time Machine Interface ("Star Wars") won't display properly, or crashes*
    *Section A. _TOOLS and PROCEDURES YOU MAY NEED*_
    There are some free 3rd-party tools that may be useful in diagnosing problems with Time Machine. You'll see references to them in several places below.
    _*A1. Time Machine Buddy widget*_
    |
    Click here to download the +*Time Machine Buddy*+ widget.
    It shows the messages from your logs for one TM backup run at a time, in a small window. An explanation of some of the error messages is in section #C2 below. Other common messages are explained in item #7 of the Frequently Asked Questions *User Tip* at the top of this forum.
    You can copy these messages by selecting them via dragging your mouse over them (be sure to get them all, as they may overflow the small window), then pressing Cmd+C. This copies them to your "clipboard," so you can post them in a thread here (via Cmd+V) to get help diagnosing a problem. (Occasionally, the widget won't let you copy while a backup is running.)
    If the message area is blank, but you know there were backups, your user account may not have permission to view your logs. Try signing-on as an Admin User. You can grant "read" rights to the folder /private/var/log and it's contents for the other user.
    Note that the widget may only let you look back a few days. If you need to look back farther, you'll need the Console app (in your Applications/Utilities folder) to look at your older system logs (named +*system.log.1.bz2, system.log.2.bz2,+* etc). Click +*Show Log List*+ in the toolbar, then navigate to the desired logs in the sidebar that opens up. You can select only the messages from TM backups by typing backupd in the Filter box in the toolbar.
    |
    _*A2. Time Tracker*_
    |
    Click here to download the TimeTracker app. It shows most of the files saved by TM for each backup (excluding some hidden/system files, etc.). This can help you figure out just what is (or is not) being backed-up.
    |
    _*A3. Tinker Tool*_
    |
    Click here to download the +*Tinker Tool*+ app. It allows you to change the Finder to show hidden files (among many other things). Select the first option under Finder, then click +Relaunch Finder+ at the bottom. Reverse this when done.
    Do not use any of the other options unless you know the possible consequences.
    |
    _*A4. Full Reset of Time Machine*_
    |
    a. Go to TM Preferences, turn TM Off, de-select the drive (select "none"), and click the Options button. Note any exclusions in the +Do Not Back Up+ box, and other option(s) on that panel. Then quit System Preferences.
    b. Eject, disconnect, and power-off the drive for a few moments, then reconnect it.
    c. Delete the file /Library/Preferences/com.apple.TimeMachine.plist (in your top-level Library folder, not your home folder).
    d. Go back to TM Preferences, re-select your drive, re-enter any exclusions and other options.
    e. Do a +*Back Up Now*+ or wait for the next scheduled backup.
    |
    _*A5. How to do a Repair or +Verify Disk+*_
    |
    This will Repair or Verify the +File System+ on a disk, partition, or sparse bundle (not the actual hardware). Use the +*Disk Utility+* app, in your Applications/Utilities folder. Do this when TM backups are turned-off, or at least not running.
    To Repair an *external disk attached to an Airport Extreme,* disconnect it from the Airport, connect it directly to your Mac and select it in the Disk Utility Sidebar.
    To Repair an external or *internal Time Machine* disk/partition, select it in the Disk Utility Sidebar.
    To Repair the *sparse bundle* on a Time Capsule, connect via an Ethernet cable if you can; it will be much faster. Then mount the sparse bundle by opening the TC in the Finder and double-clicking on the sparse bundle. Drag the sparse bundle into Disk Utility's sidebar and select it.
    With the desired partition or sparse bundle selected, click the +*Repair Disk+* (not permissions) button. This may take a while, especially on a Time Capsule. If errors are found, but not all of them were repaired, run the +*Repair Disk+* again, and again, until it either fixes all the errors or can't fix any more.
    To Verify your internal (boot) drive/partition (since you can't Repair the one you're running from), select it in Disk Utility's sidebar and click the +*Verify Disk+* (not permissions) button. If it shows errors, you'll need to fix them via this procedure:
    1. Insert your Leopard/Snow Leopard Install disc and restart while holding down the "C" key. This will take a few moments.
    2. Select your language when prompted.
    3. On the next screen, select Utilities in the Menubar, then +*Disk Utility.*+
    4. Do a +*Repair Disk*+ (not permissions) on your internal HD. If it doesn't fix all the errors, run it again (and again), until it either fixes them all, or can't fix any more.
    5. Reboot normally.
    |
    *Section B. _SET - UP PROBLEMS*_
    _*B1. I can't select my drive for use with Time Machine*_
    If the drive/partition you want to use for TM backups doesn't appear in the list when you select TM Preferences > Change Disk, it's probably not formatted correctly. See item #C1 for help determining whether it's right, and how to fix it.
    |
    _*B2. The +Change Disk+ button doesn't work*_
    If the +*Change Disk*+ button in TM Preferences doesn't do anything, try turning-off the +*Back To My Mac*+ application temporarily.
    |
    _*B3. No last or oldest backup date shown*_
    |
    If these dates don't appear when selecting the TM icon in your Menubar, or TM Preferences, try the following:
    1. Do a +*Back Up Now.*+ That will often recover the info.
    2. De-select your TM Drive via TM Preferences (select "none"), quit System Preferences, then re-select it and do a +*Back Up Now.*+
    3. A Log Out or Restart may fix it.
    4. If they're still not shown, try a Full Reset (see #A4).
    |
    _*B4. Wrong icon shown for TM drive/partition on desktop and/or Finder sidebar*_
    |
    Try de-selecting, then re-selecting the "Show" option in Finder > Preferences > General and/or Sidebar.
    Try a "Full Reset" as in item #A4.
    |
    *Section C. _BACKUP FAILURES*_
    _*C1. Initial Backup Failed*_
    The most common cause is the TM drive (but not a Time Capsule) not being formatted correctly (even, on occasion, if TM formatted it!). Use Disk Utility (in your Applications/Utilities folder) to verify the setup:
    First, select the second line for your internal HD (usually named "Macintosh HD"). Towards the bottom, the Format should be +Mac OS Extended (Journaled),+ although it might be +Mac OS Extended (Case-sensitive, Journaled).+
    Next, select the line for your TM partition (indented, with the name). Towards the bottom, the *Format must* be the same as your internal HD (above). If it isn't, you must erase the partition (not necessarily the whole drive) and reformat it with Disk Utility.
    Sometimes when TM formats a drive for you automatically, it sets it to +Mac OS Extended (Case-sensitive, Journaled).+ Do not use this unless your internal HD is also case-sensitive. All drives being backed-up, and your TM volume, should be the same. TM may do backups this way, but you could be in for major problems trying to restore to a mis-matched drive.
    Last, select the top line of the TM drive (with the make and size). Towards the bottom, the *Partition Map Scheme* must be either GUID (preferred) or +Apple Partition Map+ for an Intel Mac. It must be either +Apple Partition Map+ (preferred) or GUID for a PPC Mac. If this is wrong, you must completely erase the disk and reformat it. See item 5 of the Frequently Asked Questions *User Tip* at the top of this forum.
    Once you're sure your disk/partition is formatted correctly, if your backups still fail, continue to the next item:
    |
    _*C2. Other Backup Fails*_
    If this is your first backup, or the first one to a new external drive/partition, the most common cause is the drive not being formatted properly (even, on occasion, when Time Machine formatted it for you!). So if there's any question, see the previous item.
    If a backup fails, note any message it sends, and start with this Apple article: Troubleshooting Time Machine backup issues. It includes a wide range of problems, and has links to many other Apple technical articles.
    Those messages/problems are not repeated here, except for a couple that Apple doesn't cover completely.
    If that doesn't solve your problem, get the Time Machine Buddy messages (see #A1). Many of the common and normal messages are detailed in item 7 of the Frequently Asked Questions *User Tip* at the top of this forum. Only the ones that might indicate a problem are repeated here.
    *Messages that might indicate trouble:*
    Event store UUIDs don't match naming your internal HD (or any other drive/partition being backed-up). TM can't be sure the OSX internal log of file changes that it normally uses is correct. This is seen on your first backup of a disk, or after an improper shutdown, a full restore, certain hardware repairs, removal of certain exclusions, a large volume of changes (such as an OSX update), or many days without a successful backup. It may cause a lengthy backup, so if you see it frequently, without a good reason, you need to figure out why.
    Event store UUIDs don't match naming an external drive/partition. TM isn't sure that everything on it is what TM expects. This may be because the drive was disconnected improperly, or it doesn't appear to be the drive TM expects. Again, if you see this without a good reason, investigate.
    . . . node requires deep traversal. Instead of the log of file changes TM normally uses, it must examine every file and folder on the named drive/partition, and compare it to the last backup, to figure out what's changed and needs to be backed-up. Obviously, this is a lengthy procedure; and especially lengthy if you're doing wireless backups. As this is part of the "Preparing" (Leopard) or "Calculating changes" (Snow Leopard) phase, you may not see any more messages for quite a while. Try not to interrupt the backup, as this must be done again (and again) until a backup is completed successfully.
    Error: backup disk is full - all nn possible backups were removed, but space is still needed. This is pretty clear. TM deleted as many old backups as it could (and they're all listed in the first failed backup's messages). See item #C4.
    Bulk setting Spotlight attributes failed. or Waiting for index to be ready. There may be a problem with your TM drive, or difficulty communicating with it. See item #D2.
    Error: (-36) SrcErr:YES Copying {a file path} to {"null" or another file path}
    or Indexing a file failed. Returned -12 for: {a file path}, {another file path}
    These may indicate a problem with the first file referenced. See the next item.
    If you don't see any of these messages, or nothing here seems to help, copy and post all the messages from the failed backup in a new thread here, along with specifics of your set up.
    |
    _*C3. "An error occurred while copying files to the backup volume"* or *"Aborting backup because indexing a file failed"*_
    Occasionally, backups will fail with this message for no good reason, and the next one will complete normally. So either wait for the next scheduled backup, or do a +*Back Up Now*+ from the TM icon in your Menubar, or by right-clicking the TM icon in your dock. If that backup completes normally, there's no real problem.
    If the next one fails also, then there most likely is something wrong -- the question is, what?
    Get the Time Machine Buddy messages (see #A1). Look for the message(s) about a file that couldn't be copied, such as:
    |
    Error: (-36) SrcErr:YES Copying {a file path} to {"null" or another file path}
    or Indexing a file failed. Returned -12 for: {a file path}, {another file path}
    |
    If you're not familiar with file "paths," it can be a little difficult to read these messages. They look something like this:
    /Users/<Name>/iMovie Events.localized/clip-2008-04-02.mov to /Volumes/TM Backups/ . . . etc.
    The end of the file in question is usually indicated either by " to " or just a comma and space before the next one.
    If it's a file you're sure you don't need, you can delete it. If not, for now, don't touch it. Instead, exclude it from TM:
    Go to TM's Preferences and click Options.
    In the next panel, click the plus sign at the bottom.
    In the sidebar of the next panel, select your computer name, internal HD, or home folder as necessary; then navigate to the file listed, or, perhaps, it's enclosing folder.
    Select it, click Exclude, then Done.
    Then do a +*Back Up Now*+ from the TM icon in your Menubar, or by right-clicking the TM icon in your dock.
    If the backup runs ok, then you need to figure out what's wrong with that file.
    If it fails again, check it's messages. If it's the *exact same* file, you didn't exclude the right one, or you need to do a "full reset" (see item #A4).
    If you get the same message for a different file, you may need stronger stuff:
    a. Exclude your TM disk from any anti-virus scanning.
    b. Also exclude it from Spotlight indexing, via System Preferences > Spotlight > Privacy.
    c. Do a +*Repair Disk*+ on your TM drive/partition. See #A5 above.
    d. If the original file is on an external disk, do a +*Repair Disk*+ on it, too.
    e. If the original file is on your internal HD (your boot drive), do a +*Verify Disk*+ on it. See #A5 above.
    If all else fails, you may have a problem with the drive, or communicating with it. Try all the suggestions in #D2 below.
    |
    _*C4. "This backup is too large"*_
    |
    For one reason or another, TM is out of room on the backup disk/partition. When it's space gets near full, TM will normally delete as many old and expired backups as it can to make room for new ones.
    There are some backups that Time Machine *will not delete,* however. It won't delete the last remaining backup, or any backups from a different Mac. Sometimes TM will start a new "sequence" of backups, as if you had a different Mac, and it may not delete any from the prior sequence, either.
    Also note that, although it deletes a backup, it doesn't necessarily delete it's copies of all the items that were on that backup. It only deletes it's copies of items that no longer exist on any other backup. Thus you won't lose the backup of anything that's currently on your system.
    When this happens, you have a few options:
    1. De-select the +*Warn when old backups are deleted*+ option in TM Preferences > Options, and try again.
    2. Erase the TM disk/partition with Disk Utility (in Applications/Utilities) and let TM start over with a new full backup.
    3. Manually delete some old backups via the TM interface (do not use the Finder!). This is rather tedious, as it must be done one at a time, and there's no way to tell in advance which ones will be quick (and not gain much room) and which will take a long time and recover more space. See item #12 of the Frequently Asked Questions *User Tip* at the top of this forum for detailed instructions.
    4. Get a different disk/partition for your Time Machine backups. Then either:
    Give it a different name, and use the +Change Disk+ button in TM Preferences to select it. Let TM start fresh on the new drive/partition, with a full backup of your entire system. Keep the old drive/partition for a while (disconnected) until you're sure everything is working and you don't need the old backups anymore.
    Or, duplicate the current backups to it via the Restore tab of Disk Utility in your Applications/Utilities folder (in Snow Leopard only, you can copy the Backups.backupdb folder via the Finder). Note that you must duplicate an entire disk/partition to another entire disk/partition. See item #18 in the Frequently Asked Questions *User Tip* at the top of this forum for detailed instructions.
    |
    _*C5. "You do not have appropriate access privileges to save file “.<nnnnnnn>” in folder <name of TM Drive>"*_
    |
    Open the Terminal app (in your Applications/Utilities folder).
    Be extremely careful when using Terminal. It is a direct interface into UNIX, the underpinning of OSX. Unlike the Finder, there are few protections against making a mistake, which can cause untold damage.
    In Terminal, the prompt looks like this: user-xxxxxx:~ <your name>$
    (where <your name> is your short user name). It's followed by a non-blinking block cursor (unless it's been changed via Terminal > Preferences).
    At the prompt, type the following exactly as shown in the example, substituting the name of your TM drive exactly, including any spaces, between the quotes; and the string of numbers & letters from the message where the series of x's are (keep the dot):
    <pre> *sudo chmod 644 /volumes/"TM drive name"/.xxxxxxxxxxxx*</pre>
    example: *sudo chmod 644 /volumes/"TM Backups"/.0a1b2c3d4e5f*
    Press Return. You'll get some warnings and a request for your Administrator's password. Type it in (it won't be displayed) and press Return again.
    Then try a +*Back Up Now*+ from the TM icon in your Menubar, or by right-clicking the TM icon in your dock.
    |
    _*C6. The backup volume is read only*_
    First, follow the Apple article mentioned above: Troubleshooting Time Machine backup issues.
    If that doesn't correct it,
    If you only have a partial backup, or don't need the ones you've done, the simplest thing to do is just erase the disk/partition with Disk Utility (in your Applications/Utilities folder).
    If you don't want to erase it, here's a workaround:
    First, you need to find the name of the hidden file that's causing the problem. If the Time Machine Buddy (see #A1) shows a message like the one in item #C5, follow the instructions there.
    If not, use the TinkerTool app (see #A3) to show hidden files.
    In a Finder window, select your Time Machine drive/partition. The very first file shown should have a name consisting of a period (dot) followed by 12 numbers and/or letters. (This is your Mac's Ethernet Address). Copy or make a note of it.
    Then follow the rest of the instructions in item #C5.
    |
    _*C7. "Error (12): Link of previous volume failed."*_
    |
    This usually happens when you replaced a drive with a different one, but with the same name as the original.
    Because of the way Time Machine keeps track of drives, at one point it thinks they're the same, but later on realizes they aren't.
    Either rename the drive (append "_2" or something), or delete all previous backups of it, via the instructions in item 12 of the Frequently Asked Questions *User Tip* at the top of this forum.
    And note that TM will probably do a full backup of the drive. If there isn't much space on your TM drive/partition, see #C4. You may need to do item 2, 3, or 4 listed there.
    |
    _*C8. Backup fails after Logic Board replacement*_
    The logic board contains your Ethernet "Mac Address", which is a unique number that TM uses to be sure it knows which Mac is which. So, to TM, it is now a *different computer.*
    This is so it can keep each Mac's backups separate (you can back multiple Macs up to the same external disk or Time Capsule). It does this by putting a hidden file containing this address on the TM disk.
    There is a fairly elaborate way to attempt to persuade TM that the existing backups really are for your "new" Mac: http://www.macosxhints.com/article.php?story=20080128003716101
    It is very easy to make an error with Terminal, get no error message, and have it not work, or worse, so try it at your own risk.
    But there is an alternative: hold down the Option key while selecting the TM icon in your Menubar, or right-click the TM icon in your Dock. Then use the (badly named) +*Browse Other Time Machine Disks*+ option. It will take you into the normal TM interface where you can see and restore from the old set of backups.
    Even if you're successful with the Terminal work, your first backup with the new logic board may be a full one -- every file and folder on your system. If TM decides to do that, you cannot prevent it.
    So if your TM disk/partition isn't over twice the size of the data it's backing-up, your best bet may be to just erase it with Disk Utility (in your Applications/Utilities folder) and let TM start over.
    |
    _*C9. "The back-up disk image could not be created."*_
    |
    If you get this message when backing-up wirelessly, check your +*System Name*+ at the top of the System Preferences > Sharing panel.
    It must not be blank; it should not be more than 25 characters long; and you should avoid punctuation (except periods and underscores), and unusual characters.
    If that doesn't help, apply the same rules to the name of your Time Capsule.
    |
    _*C10. Error: (-50) Creating directory*_
    |
    This may indicate a problem with your TM drive. Do a +*Repair Disk*+ on it. See #A5 above.
    If no errors are found, or they're all found and fixed, but you still get the message, try a "full reset" as in item #A4.
    If Disk Utility can't fix them all, the disk may be failing. Copy the messages from the last run of Disk Utility and post them in a new thread in this forum for advice.
    |
    _*C11. Drive does not appear to be the correct backup volume for this computer(Cookies do not match)*_
    |
    If this happens after getting a new Logic Board, see item #C8.
    This also happens on occasion after switching a TM drive from one Mac to another, erasing your TM disk/partition, or attaching a new TM drive with the same name as an old one.
    You can usually fix this by simply re-selecting your TM drive in TM Preferences > Change Disk.
    If that doesn't help, try a full reset. See item #A4.
    |
    *Section D. _OTHER PROBLEMS RUNNING BACKUPS*_
    _*D1. Stuck in "Preparing" or "Calculating changes"*_
    |
    See this Apple Support document: Time Machine may display "Preparing" for a longer time
    Try not to interrupt the backup, as this procedure must be done again (and again) until a backup is completed successfully.
    Also see the next topic:
    |
    _*D2. Backup is slow or "hung"*_
    |
    If this is your first backup under Snow Leopard after updating from Leopard, try cancelling the backup, doing a Restart, and trying again.
    Otherwise, get the Time Machine Buddy messages (see #A1).
    If it shows Event store UUIDs don't match
    and/or . . . node requires deep traversal, it may not be "hung" at all. See item #C2.
    If it shows Waiting for index to be ready and/or Bulk setting Spotlight attributes failed messages, there may be a problem with your TM drive, or difficulty communicating with it. Unfortunately, any of a number of things may cause this. The list of things to try is:
    1. Exclude your TM disk/partition from any anti-virus scanning.
    2. Exclude it from Spotlight (System Preferences > Spotlight > Privacy).
    _*If backing up to a Time Capsule or External Disk connected to an Airport Extreme:*_
    3. Check your System Name via System Preferences > Sharing. It it's blank, that's likely the problem. If it's over 26 characters long, trim it. If it has any unusual characters, try removing them. Remove any punctuation and spaces. Do the same with the Time Capsule or Airport Extreme name.
    4. Try moving the TC or AEBS and Mac closer together.
    5. Look for interference with another wireless device. Turn anything else off, or move it farther away.
    6. Try repairing the TC's Sparse Bundle or AEBS drive's TM disk/partition. See #A5 above.
    _*If backing up to an External hard drive:*_
    7. Do a +*Repair Disk*+ on it. See #A5 above.
    8. At least temporarily, de-select +*Put the hard disk(s) to sleep ...+* in System Preferences > Energy Saver.
    9. Be sure it's connected directly to your Mac (no hubs, and not the USB port on the keyboard, as some are USB 1.0).
    10. Try different port(s), cable(s).
    11. See if your drive has an automatic sleep or "spin down" feature you can disable.
    12. Check the maker's web site (support or forum) for any driver or firmware updates.
    If nothing helps, your drive may be failing (they all do, sooner or later).
    |
    _*D3. TM is doing a full backup for no good reason*_
    If this is your first backup on Snow Leopard after upgrading from Leopard, try cancelling the backup, doing a Restart, and trying again.
    Time Machine may do a full backup after any of the following:
    Using a new disk or partition for backups (always).
    A full restore (probably).
    Some hardware repairs, especially a new internal hard drive (probably) or logic board (always, but see #C8).
    Changing your computer's name via System Preferences > Sharing (maybe).
    Renaming a disk/partition that's being backed-up (probably).
    Going several days without a backup (probably; also seems to depend on the volume of changes).
    Exactly why it doesn't always do full backups for the items marked "probably" is not clear, so to be safe, assume it will.
    |
    _*D4. My backups seem too large*_
    |
    Time Machine may be doing a full backup of your entire system. See #D3.
    Doing an OSX update can cause a large backup, as it may add or update several thousand files.
    Removing exclusions, such as your top-level System and/or Library folders, can be sizeable.
    Renaming a folder or disk drive, or moving a file or folder, will cause the entire item moved or renamed to be backed-up. This includes all files and sub-folders in a moved or renamed folder.
    There are some OSX features and 3rd-party applications that cause large Time Machine backups. Common ones are FileVault, vmWare Fusion, Parallels Desktop, Entourage, and Thunderbird. Any application that uses a single large file or database may do this. See item 9 of the Frequently Asked Questions post.
    You can use the +Time Tracker+ app (see item #A2) to see just what was copied on any particular backup. There may be ways to minimize the size of such backups; search and/or post in this forum for help.
    |
    *Section E. _PROBLEMS VIEWING, RESTORING, or DELETING BACKUPS*_
    _*E1. Backups were deleted unexpectedly*_
    |
    Time Machine manages it's space for you, automatically. When it's drive/partition gets near full, it will begin deleting your oldest backups to make room for new ones. See item #C4 for more info and your options.
    In addition, regardless of space, TM also routinely "thins" your backups. It keeps one per week for as long as there's room; one per day (the first) for a month; all others for 24 hours.
    Usually when old weekly backups are deleted unexpectedly, it's because TM has done a new full or large backup, which of course requires a lot of space. See #D3 or D4 for common reasons.
    If in doubt, get the +Time Machine Buddy+ widget messages (see #A1). They'll show how much it was trying to back up. See item #7 of the Frequently Asked Questions *User Tip* at the top of this forum for explanation of those messages.
    |
    _*E2. I can't see some backups*_
    |
    If you can't see the backups for a disk/partition that's no longer connected, see #E3 below.
    TM keeps the backups for each Mac separate, and normally only shows the ones for the Mac it's running on, even if there are other Macs' backups on its disk/partition.
    Also, sometimes TM will start a new "sequence" of backups, as if they were from a different Mac. See item #D3.
    To see these "other" backups, you need the (badly named) +*Browse Other Time Machine Disks*+ option. It's available by holding down the Option key while selecting the TM icon in your Menubar, or by right-clicking the TM icon in your Dock.
    You'll see a selection screen showing all the disks/partitions that have TM backups on them. Select the one you want, and you'll be taken to the normal TM "Star Wars" interface, where you should see all the backups on that disk/partition.
    Note that, unfortunately, you cannot merge or combine two different "sequences" of backups.
    Also note that you cannot use the normal Restore button at the bottom of the screen to restore items, since they're from a different Mac. Instead, select the desired item(s), then click the "Gear" icon in the Finder window's toolbar and select the +*Restore <item> to ...+* option. You'll then get a prompt to specify the destination.
    |
    _*E3. I can't see backups for a disk/partition that's no longer connected*_
    |
    Open a Finder window and press ShiftCmdC (or select your computer name in the Finder Sidebar).
    Then either +*Enter Time Machine*+ or +*Browse Other Time Machine Disks*+ (see #E2).
    On the first Finder window in the "cascade," labelled +*Today (Now),+* you'll see all the volumes currently attached to your Mac.
    Select the Finder window or TimeLine entry for any backup, and you'll see a folder for each drive/volume that was backed-up, including any that are no longer connected. Navigate from there to whatever you're looking for.
    Also note that you cannot use the normal Restore button at the bottom of the screen to restore selected items, since they're from a different disk/partition. Instead, select the desired item(s), then click the "Gear" icon in the Finder window's toolbar and select the +*Restore <item> to ...+* option. You'll then get a prompt to specify the destination.
    You can restore an entire disk/partition to a different one (erasing any previous contents) via the procedure in item #14 of the Frequently Asked Questions *User Tip* at the top of this forum.
    |
    _*E4. Time Machine Interface ("Star Wars") won't display properly, or crashes*_
    |
    This can be caused by any of a number of things. Try these fixes:
    If you're using a Finder replacement (such as Pathfinder), be sure the Finder is running.
    If you're using Spaces, turn it off temporarily.
    If you have a second monitor, or anything plugged-in to a video-out port, disconnect it temporarily.
    De-select your TM drive via TM Preferences > Change Disk (select "none"), then re-select the correct one.
    Do a "complete reset" of TM, as in item #A4.
    Do a +*Repair Disk+* on your TM drive. See #A5 above.
    Try or create another user (System Preferences > Accounts). If it works ok from that user, delete the file:
    +*<home folder of the user where it doesn't work>/Library/Preferences/com.Apple.Finder.plist+*

  • Time Machine not working with Verbatim USB2TB External HDD

    MacBook Pro
    15-inch, Mid 2010
    8GB Ram
    OS 10.8.2
    No updates available ATT.
    Problem with Time Machine using Verbatim USB2TB (Verbatim # 96865) external hard drive in regular and safe boot. According to the Verbatim website, this external drive is compatiable with MAC OS 10+ and can be formatted to the specific Mac filesystems.
    The following list of events below happen irregardless of running in regular or safe boot, so I noted my last attempt at a backup while in Safe Boot.
    Before this last attempt, I successfully zeroed out the data on the drive in regular boot.
    As you will see below, the drive works just fine until Time Machine gets it grimy digits on it and kills it like South Park kills Kenny.
    ---- Begin ----
    Started in Safe Boot
    Connected and powered on the external drive.
    Erased the drive and formatted it to Extended Journaled. Partition was successfully created.
    Verifying partition map for “SAMSUNG HD203WI Media”
    Checking prerequisites
    Checking the partition list
    Checking for an EFI system partition
    Checking the EFI system partition’s size
    Checking the EFI system partition’s file system
    Checking all HFS data partition loader spaces
    Checking Core Storage Physical Volume partitions
    The partition map appears to be OK
    Verifying volume “Big2TB”
    Checking file systemChecking 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 Big2TB appears to be OK.
    Successfully copied over 2.8 GB of random data. (Screenshot)
    Deleted the data and then emptied the Trash.
    Started Time Machine backup.
    Time Machine Created a backup folder on the external drive.
    Time Machine started to transfer data then hung at 452.1 MB of 257.66 GB.
    Backup failed.
    --- Console ---
    1/13/13 11:57:59.988 AM com.apple.backupd[1558]: Starting manual backup
    1/13/13 11:58:04.581 AM com.apple.backupd[1558]: User continued after being warned of changed destination volume identity
    1/13/13 11:58:04.623 AM com.apple.backupd[1558]: Backing up to: /Volumes/Big2TB/Backups.backupdb
    1/13/13 11:58:04.628 AM com.apple.backupd[1558]: Ownership is disabled on the backup destination volume.  Enabling.
    1/13/13 11:58:05.156 AM mds[34]: (Warning) Server: No stores registered for metascope "kMDQueryScopeComputer"
    1/13/13 11:58:06.336 AM com.apple.backupd[1558]: Forcing deep traversal on source: "MainMan" (mount: '/' fsUUID: 8A3A5598-7C8B-3753-ABA8-D980E60299A3 eventDBUUID: 23107488-4BC9-49FB-818D-226AE695DE06)
    1/13/13 11:58:23.346 AM com.apple.backupd[1558]: Backup content size: 246.45 GB excluded items size: 12.21 GB for volume MainMan
    1/13/13 11:58:23.368 AM com.apple.backupd[1558]: Found 910640 files (234.23 GB) needing backup
    1/13/13 11:58:23.370 AM com.apple.backupd[1558]: 281.08 GB required (including padding), 2 TB available
    1/13/13 11:58:23.388 AM com.apple.backupd[1558]: Waiting for index to be ready (100)
    1/13/13 11:59:23.443 AM com.apple.backupd[1558]: Waiting for index to be ready (100)
    1/13/13 12:00:02.530 PM WindowServer[114]: CGXGetWindowInfo: Invalid window 1045
    1/13/13 12:00:02.530 PM Dock[259]: CGSBindWindow: Unable to obtain window information
    1/13/13 12:00:02.531 PM Dock[259]: CGSGetWindowTags: Invalid window 0x415
    1/13/13 12:00:02.531 PM Dock[259]: find_shared_window: WID 1044
    1/13/13 12:00:02.531 PM Dock[259]: CGSGetWindowTags: Invalid window 0x414
    1/13/13 12:00:02.532 PM Dock[259]: find_shared_window: WID 1043
    1/13/13 12:00:02.532 PM Dock[259]: CGSGetWindowTags: Invalid window 0x413
    1/13/13 12:00:04.481 PM WindowServer[114]: CGXGetWindowType: Invalid window 1066
    1/13/13 12:00:04.481 PM Dock[259]: find_shared_window: Invalid depth WindowID 0x42a
    1/13/13 12:00:04.481 PM Dock[259]: CGSGetWindowTags: Invalid window 0x42a
    1/13/13 12:00:04.482 PM Dock[259]: find_shared_window: WID 1065
    1/13/13 12:00:04.482 PM Dock[259]: CGSGetWindowTags: Invalid window 0x429
    1/13/13 12:00:04.482 PM Dock[259]: find_shared_window: WID 1064
    1/13/13 12:00:04.482 PM Dock[259]: CGSGetWindowTags: Invalid window 0x428
    1/13/13 12:00:23.497 PM com.apple.backupd[1558]: Waiting for index to be ready (100)
    1/13/13 12:01:23.549 PM com.apple.backupd[1558]: Waiting for index to be ready (100)
    1/13/13 12:01:44.830 PM com.apple.launchd[1]: (com.apple.xpcd.F5010000-0000-0000-0000-000000000000[1541]) Exited: Killed: 9
    1/13/13 12:01:44.000 PM kernel[0]: memorystatus_thread: idle exiting pid 1541 [xpcd]
    1/13/13 12:01:49.000 PM kernel[0]: (default pager): [KERNEL]: ps_select_segment - send HI_WAT_ALERT
    1/13/13 12:01:49.000 PM kernel[0]: macx_swapon SUCCESS
    1/13/13 12:02:15.000 PM kernel[0]: USBF:          7419.448          AppleUSBEHCI[0xffffff8008e26000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 5, EP: 2)
    1/13/13 12:02:21.000 PM kernel[0]: USBF:          7425.451          AppleUSBEHCI[0xffffff8008e26000]::Found a transaction which hasn't moved in 5 seconds on bus 0xfd, timing out! (Addr: 5, EP: 0)
    1/13/13 12:02:27.000 PM kernel[0]: USBF:          7431.454          AppleUSBEHCI[0xffffff8008e26000]::Found a transaction which hasn't moved in 5 seconds on bus 0xfd, timing out! (Addr: 5, EP: 0)
    1/13/13 12:02:58.000 PM kernel[0]: USBF:          7462.473          AppleUSBEHCI[0xffffff8008e26000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 5, EP: 2)
    1/13/13 12:05:37.068 PM WindowServer[114]: CGXGetWindowInfo: Invalid window 1196
    1/13/13 12:05:37.068 PM Dock[259]: CGSBindWindow: Unable to obtain window information
    1/13/13 12:05:37.068 PM Dock[259]: CGSGetWindowTags: Invalid window 0x4ac
    1/13/13 12:05:37.069 PM Dock[259]: find_shared_window: WID 1195
    1/13/13 12:05:37.069 PM Dock[259]: CGSGetWindowTags: Invalid window 0x4ab
    1/13/13 12:05:37.070 PM Dock[259]: find_shared_window: WID 1194
    1/13/13 12:05:37.070 PM Dock[259]: CGSGetWindowTags: Invalid window 0x4aa
    1/13/13 12:06:34.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:06:39.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:06:44.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:06:50.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:06:55.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:07:01.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:07:11.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:07:17.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:07:22.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:07:27.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:07:27.000 PM kernel[0]: jnl: disk1s2: do_jnl_io: strategy err 0x5
    1/13/13 12:07:27.000 PM kernel[0]: jnl: disk1s2: end_transaction: only wrote 0 of 389120 bytes to the journal!
    1/13/13 12:07:54.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:08:21.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:08:21.820 PM com.apple.backupd[1558]: Error: (-36) SrcErr:NO Copying /Applications/Adobe/AdobePatchFiles/{CFA1AAD1-DC10-413D-875E-2F5B8A78CB3B}.zip to /Volumes/Big2TB/Backups.backupdb/numeroeins/2013-01-13-115805.inProgress/376C91 FB-29D6-47F1-A29B-67D94CBD01BA/MainMan/Applications/Adobe/AdobePatchFiles
    1/13/13 12:08:23.122 PM com.apple.backupd[1558]: Stopping backup.
    1/13/13 12:08:23.122 PM com.apple.backupd[1558]: Error: (-8062) SrcErr:NO Copying /Applications/Adobe/AdobePatchFiles/{CFA1AAD1-DC10-413D-875E-2F5B8A78CB3B}.zip to /Volumes/Big2TB/Backups.backupdb/numeroeins/2013-01-13-115805.inProgress/376C91 FB-29D6-47F1-A29B-67D94CBD01BA/MainMan/Applications/Adobe/AdobePatchFiles
    1/13/13 12:08:23.136 PM com.apple.backupd[1558]: Copied 817 files (572.1 MB) from volume MainMan.
    1/13/13 12:08:23.136 PM com.apple.backupd[1558]: Copy stage failed with error:11
    1/13/13 12:08:23.174 PM com.apple.backupd[1558]: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/Big2TB/Backups.backupdb/numeroeins size:37
    1/13/13 12:08:33.228 PM com.apple.backupd[1558]: Backup failed with error: 11
    1/13/13 12:08:48.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:09:15.000 PM kernel[0]: disk1s2: I/O error.
    ---- End console ---
    Attempted to copy over 2.8 GB of random data again. Failed. 
    Now the drive is completely useless until it is erased. Also will not eject properly anymore. Force eject took 3 minutes.
    --- Console ---
    1/13/13 12:19:00.248 PM mtmfs[1555]: filesystem unmount attempted from stopFS
    1/13/13 12:19:31.946 PM fseventsd[44]: disk logger: failed to open output file /Volumes/Big2TB/.fseventsd/0000000000048e11 (Invalid argument). mount point /Volumes/Big2TB/.fseventsd
    1/13/13 12:19:31.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:19:32.187 PM fseventsd[44]: disk logger: failed to open output file /Volumes/Big2TB/.fseventsd/0000000000048e11 (Invalid argument). mount point /Volumes/Big2TB/.fseventsd
    1/13/13 12:19:32.910 PM WindowServer[114]: CGXDisableUpdate: UI updates were forcibly disabled by application "Disk Utility" for over 1.00 seconds. Server has re-enabled them.
    1/13/13 12:19:35.129 PM WindowServer[114]: reenable_update_for_connection: UI updates were finally reenabled by application "Disk Utility" after 3.22 seconds (server forcibly re-enabled them after 1.00 seconds)
    1/13/13 12:20:05.375 PM fseventsd[44]: disk logger: failed to open output file /Volumes/Big2TB/.fseventsd/0000000000048e11 (Invalid argument). mount point /Volumes/Big2TB/.fseventsd
    1/13/13 12:20:05.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:20:05.390 PM fseventsd[44]: disk logger: failed to open output file /Volumes/Big2TB/.fseventsd/0000000000048e11 (Invalid argument). mount point /Volumes/Big2TB/.fseventsd
    1/13/13 12:20:37.153 PM fseventsd[44]: disk logger: failed to open output file /Volumes/Big2TB/.fseventsd/0000000000048e11 (Invalid argument). mount point /Volumes/Big2TB/.fseventsd
    1/13/13 12:20:37.153 PM fseventsd[44]: disk logger: failed to open output file /Volumes/Big2TB/.fseventsd/0000000000048e11 (Invalid argument). mount point /Volumes/Big2TB/.fseventsd
    1/13/13 12:20:37.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:20:48.102 PM diskarbitrationd[49]: mds [34]:20995 not responding.
    1/13/13 12:21:04.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:21:04.451 PM com.apple.kextd[11]: Can't create kext: invalid CFBundleVersion in identifier cache entry entry 339.
    1/13/13 12:21:14.854 PM com.apple.security.pboxd[1518]: CGSGetWindowTags: Invalid window 0x7b5
    1/13/13 12:21:14.854 PM com.apple.security.pboxd[1518]: kCGErrorFailure: CGSSetHideOnDeact: error getting window tags
    1/13/13 12:21:15.372 PM com.apple.security.pboxd[1518]: CGSCopyWindowColorSpace: Invalid window 0x7b5
    1/13/13 12:21:22.606 PM WindowServer[114]: CGXDisableUpdate: UI updates were forcibly disabled by application "com.apple.security.pboxd" for over 1.00 seconds. Server has re-enabled them.
    1/13/13 12:21:23.060 PM com.apple.quicklook.satellite[1657]: bootstrap_look_up2 failed with 0x44c
    1/13/13 12:21:23.081 PM mds[34]: (Warning) Server: No stores registered for metascope "kMDQueryScopeComputer"
    1/13/13 12:21:23.090 PM WindowServer[114]: reenable_update_for_connection: UI updates were finally reenabled by application "com.apple.security.pboxd" after 1.48 seconds (server forcibly re-enabled them after 1.00 seconds)
    1/13/13 12:21:23.000 PM kernel[0]: Sandbox: sandboxd(1658) deny mach-lookup com.apple.coresymbolicationd
    1/13/13 12:21:26.021 PM com.apple.security.pboxd[1518]: CGSReleaseWindow: Invalid window 1973
    1/13/13 12:21:26.021 PM com.apple.security.pboxd[1518]: _NXTermWindow: error releasing window (1000)
    1/13/13 12:21:27.775 PM sandboxd[1658]: ([1657]) QuickLookSatelli(1657) deny mach-lookup com.apple.PowerManagement.control
    1/13/13 12:21:52.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:21:57.967 PM fseventsd[44]: disk logger: failed to open output file /Volumes/Big2TB/.fseventsd/0000000000048e11 (Invalid argument). mount point /Volumes/Big2TB/.fseventsd
    1/13/13 12:21:57.967 PM fseventsd[44]: disk logger: failed to open output file /Volumes/Big2TB/.fseventsd/0000000000048e11 (Invalid argument). mount point /Volumes/Big2TB/.fseventsd
    1/13/13 12:21:57.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:21:58.229 PM com.apple.kextd[11]: Can't create kext: invalid CFBundleVersion in identifier cache entry entry 339.
    1/13/13 12:21:58.000 PM kernel[0]: jnl: disk1s2: close: journal 0xffffff800908acc0, is invalid.  aborting outstanding transactions
    --- End Console ---
    ---- That's all folks! ----
    Any help would be great!

    The external drive is malfunctioning, or the data cable is bad, or you have another malfunctioning device on the bus, or there's an internal hardware fault.

Maybe you are looking for