Intermittent Time Machine Error -1

I have a late 2008 MacBook Pro 2.8 GHz with 4 GB of RAM running Mac OS X 10.7.3. I have Time Machine backups performed through a Mac Mini running Mac OS X 10.7.3 Lion Server (clean install) to an external drive attached to the mini via Firewire 800. I have three machines backing up to the server and prior to Lion, had no issues. Since the migration to Lion, only one machine, the one listed above intermittently fails to backup with the error -1, unable to mount volume. I have downloaded all of the latest patches for all clients and the server. I tried installing the "Turbo" device driver from Western Digital for the drive since no other device drivers are available (WD site says they are provided by the OS). This made no difference and the other machines continue to backup without a problem. The client having issues will backup for as much as a day or two, then throw the error again. In addition to the above I have tried the following:
Run disk utilties to verify no disk errors - no issues found
I did a manual backup to another disk, reformatted the Time Machine Disk backed up all machines - same problem
WD Smartware updated to 1.3.3.8 - latest version released after Lion and states Lion compatible.
Verified through Workgroup Manager that MAC addresses and hardware UUID are correct for all machines (Software Update through the Server works fine).
Tried backup up connected by ethernet versus WiFi - problem still intermittent and is independent of network connection type.
What next? Anyone else seeing this?

See #C17 in Time Machine - Troubleshooting.

Similar Messages

  • Intermittent Time Machine Error

    I am wondering if anyone else ha experienced this. I have Time Machine backing everything up on my Mac to a hard drive, but I keep on getting an error message. It says that "the back up volume is read only" and prompts me to change it....when I eject the drive, unplug it, and then plug it in again, it appears in the disks window of the Time Machine preferences, and I select it and its fine for about 24-hours. Then the same fault occurs when TM attempts to back up. It happened once before, but eventually stopped....any suggestions? It is driving me crazy as I have to go through the same procedure every day now.......Thanks!

    Hi Barry,
    Definitely not in there....in fact there is no time machine preferences document at all! I meant to add in my initial blurb that my husband has exactly the same Mac, operating system and back up disk for Time Machine and he doesn't get any problems.
    Anything else you can suggest?
    Thanks so much.....JO

  • Odd Intermittent Time Machine error - volume in use

    Occasionally when backing up to a shared time machine volume from a system running 10.7 server it gives an error message that the volume is in use.  /Backups adds a number next to itself such as /Backups-1 or /Backups-15.  The backups seem to automatically occur the next hour or so, however on occasion it will pop up the error throughout the day.
    Specifics about my system:
    10.7 MBAir 11" 2010 1.6GHz C2Duo -- Filevault2 encryption turned on, fresh time machine backup started after the filevault was enabled.
    Shared volume:
    iMac running 10.7 server, sharing a Drobo as a Time Machine backup location.
    All other systems on the network seem to backup fine to it however no others are operating with filevault enabled. Also none of the other systems are named the same Computer Name, and each computer's backup appears as a separate sparseimage on the shared backup volume.
    Anyhow, it looks and sounds like a bug, but just wondering if anyone else was seeing the same issue.  I was unable to find anything on the internet or the discussion boards about this issue.

    Of course as soon as I post this I finally find the troubleshooting procedures in the FAQ... That seems to have worked.

  • I'm having trouble backing up my second macbook to a new time capsule.   continue to get an error message -- "Time  Machine Error.  The backup disk image could not be created."   Is there something I need to change in my time capsule or time machine?

    I just set up a new time capsule.  it worked fine on my first macbook.  But now I cannot backup my second macbook.   Getting "Time Machine Error"  "The backup disk image could not be created."  Do I need to change settings on my time capsule to allow the second computer, or do I need to change something on the computer to allow time machine to work right?

    Try #C9 in Pondini's Time Machine Troublshooting
    http://pondini.org/TM/Troubleshooting.html

  • I have not been able to back up for2 days.  Time machine error message: /Volumes/Data/David's MacBook Air.sparsebundle" is already in use.

    I have not been able to back up for2 days.  Time machine error message: /Volumes/Data/David’s MacBook Air.sparsebundle” is already in use.
    What now?
    Macbook Air.
    Was working fine for the past year until now.

    See more like this on the right.. this is the most common error reported here since mountain lion came out..
    Or read C12.. http://pondini.org/TM/Troubleshooting.html
    Or just restart the whole network.. in right order from off.. modem.. router / TC.. clients 2min gap.

  • HT3275 Time Machine Error: The backup disk image "Volumes/Data/My Macbook Pro.sparsebundle" is already in use. (How do I correct this issue?)

    Time Machine did not back up:
    Time Machine Error; ("The backup disk image "/Volumes/Data/My MacBook Pro.sparsebundle" is already in use.")
    How do I correct this issue?
    Thanks!

    You need to be careful Bob.. people might take this literally.
    Bob Timmons wrote:
    How do I correct this issue?
    Call the exterminator to get rid of the bugs in Lion and Mountain Lion.
    https://discussions.apple.com/thread/5222487?tstart=0

  • Time Machine Error Unable to complete backup. An error occurred while ...

    Hi,
    I've looked all around the forums for the answer to this one and I'm still unable to get it. So I'm getting this error "Time Machine Error Unable to complete backup. An error occurred while linking files on the backup volume". This started happening after I turned off and on FileVault. I was having a problem with it and turning it on an off got rid of that problem, but created this one. I've noticed that when I shut down the computer and filevault accesses the TM hard drive, it can back up.....but then when I'm logged on, or I want it to back up I get the error. I've tried fixing the drive, removing the in progress file and resetting the PRAM (i think that's what it was called). I'm starting to run out of options and have no other drive to back all this info on to reformat it.
    I really don't want to loose all my stuff.
    Please help!
    Daria

    nautical_stars wrote:
    Hi,
    I've looked all around the forums for the answer to this one and I'm still unable to get it. So I'm getting this error "Time Machine Error Unable to complete backup. An error occurred while linking files on the backup volume". This started happening after I turned off and on FileVault.
    Usually this message happens when you replace an external disk that was being backed-up by Time Machine with another one of the same name.
    Since File Vault works by making a sparse image of your home folder, and it's treated as a volume just as a HD is, that's probably what's happening here: the new sparse image has the same name as the old one, but isn't the old one.
    First, consider whether you really need File Vault. It doesn't work well with Time Machine: you can't see or restore individual items in your home folder, and it only gets backed-up when you log out.
    If you have a lot of other things, say photos, videos, and/or music that don't need to be encrypted, perhaps there's an easier way to secure our sensitive data. You can create an encrypted disk image via Disk Utility (in your Applications/Utilities folder), then copy the sensitive documents into it. Then the rest of your home folder is backed-up normally, and individual items can be viewed and restored in the usual fashion.
    But if you do continue using FileVault, you may have to use TM to delete all backups of it, via the instructions in item #12 of the Frequently Asked Questions *User Tip* at the top of this forum. That should then allow the new version of your encrypted home folder to be backed-up by TM.

  • Time Machine Error "Unable to complete backup"

    I have not backed up my hard drive for about 30 days. When I plug my external hard drive in, Time Machine "prepares backup" for a while, then gives me the following message:
    *Time Machine Error*
    Unable to complete backup. An error occurred while copying files to the backup volume.
    I tried unplugging and re-plugging, rebooting my computer, trashing the ".inprogress" backup file and restarting. It did not help. While it time machine is preparing the backup, my computer runs crazy slow, with the rainbow pinwheel spinning for about 5-10 seconds just about every time I click the mouse, in any program.
    Per someone's suggestion, I put "sudo grep backupd /var/log/system.log" into terminal, and this is what came up:
    "No pre-backup thinning needed: 4.98 GB requested (including padding), 70.16 GB available
    Waiting for index to be ready (906 > 0)
    Unable to rebuild path cache for source item. Partial source path:
    Indexing a file failed. Returned -12 for: /Applications/iChat.app, /Volumes/Time Machine Backups 1/Backups.backupdb/My Computer (2)/2011-01-13-113417.inProgress/CB0D491E-EF04-48A0-9AE9-32AE43E9209C/Macintosh HD/Applications/iChat.app
    Aborting backup because indexing a file failed.
    Stopping backup."
    This time, it was apparently iChat, but in each of the three times I've tried to backup and gotten this error message, a different file has been the culprit for the indexing error.
    Any suggestions?

    orchestr wrote:
    Indexing a file failed. Returned -12
    see [this_|http://web.me.com/pondini/TimeMachine/C3.html] user tip by Pondini.
    JGG

  • "Time machine error, The disk image cannot be mounted" What can I do??

    I ran the time machine. Then, "preparing backup" showed up for a long time. After that, a window pop out: "Time machine error, The disk image cannot be mounted" What is disk image? What can I do (I can't back up anything)
    P.S. I use time capsule for backup. there were no problem on connection

    I'm having the same issue. I do not have TC as my base station. It says right in the book that if you choose, you do not have to have it run as your router, just as a part of your existing wireless network. All software is up to date and I have already shortened the name of both my TC and TC disc to 6 characters and no spaces! I've already spoken with someone today about this. He really didn't know. Have tried backing up both wirelessly and directly connecting with an Ethernet cord. I had to finally call because when I attempted to register the product to get online support, apple.com didn't recognize the serial number!!! The gentleman on the phone got it registered for me. I bought the TC from an official apple store and for whatever reason when he put in the serial number his computer said that this TC was so "old" I guess that there was technically "no support." That basically means that even though my parents just purchased this for me a week before Christmas, that it was made a year ago and the warranty is not good?? I need to do more research on that. Right now I am very unhappy about this. I am a firm apple user and have been for years, but this is frustrating.
    I had read somewhere else (not sure I've been searching apple for what seems like forever now) to make sure that the TC was showing up in "devices" of the Finder. Mine doesn't show up there, but rather in the "Network" window. Is this an issue? If it is, can anyone tell me how to fix that. I have Time Machine backing up to my TC, so I do not see why it would be.
    UPDATE: I just opened up my TC on the "Shared" section of the Finder window and deleted the old "sparsebundle" (I had no clue that anything had backed up way back at 3:30pm on Dec 29) and now I get a slightly new message: Time Machine Error: The backup disc image could not be created." So now the word "mounted" is replaced with "created." This error showed up a lot sooner than the original one. Ok, no clue. I am going to try to Change the Disc again, and try again. I will post another update.
    Message was edited by: kryzma

  • Time Machine Error: The backup was not performed because an error occurred

    G'day (from Queensland, Australia)
    Not for the first time Time Machine has broken down - originally in September 08 (I just can't recall how I fixed it!!).
    Now it has failed after 14 months of faultless performance.
    There seems to be little help available, but searching for solutions finds plenty of problems.
    I get the message "The backup was not performed because an error occurred while copying to the backup disk.
    The problem may be temporary. Try again later to back up. If the problem persists, use Disk Utility to repair you backup disk."
    (I have a Time Capsule as my backup disk)
    Disk Utility runs and finds-
    Verifying volume “Backup of xxxxxx’s iMac”
    2010-01-25 12:16:09 +1000: Starting verification tool:
    2010-01-25 12:49:21 +1000: The volume Backup of xxxxxx’s iMac appears to be OK.
    2010-01-25 12:49:21 +1000: Repair tool completed:
    So I search and find "Fix for broken Time Machine backups under Snow Leopard"
    (http://www.andrewgrant.org/2009/09/22/fix-for-broken-time-machine-backups-under- snow-leopard.html) - downgrading to 7.4.1 of the Airport Extreme / Time Capsule firmware.
    But still have the same Time Machine error!
    On to http://forums.macosxhints.com/showthread.php?t=103919&highlight=TimeMachineError
    and try-
    "... suggesting would be something like renaming the existing TimeMachine file on your backup disk - e.g. add a date to the end of it.
    And then go onto Time Machine preferences and set it up as if it were the first time you used it. (Renaming the file on the backup disk should make Time Machine think that you are starting fresh.)"
    So, using Finder, I opened my Time Capsule and renamed "xxxxxx’s iMac_00224135e6fb.sparsebundle" as "091222xxxxxx’s iMac_00224135e6fb.sparsebundle091222"
    And finally, this worked - I have my backups to 22 December and a complete backup as at today and hopefully for at least another 14 months!

    pjh42 wrote:
    G'day (from Queensland, Australia)
    Not for the first time Time Machine has broken down - originally in September 08 (I just can't recall how I fixed it!!).
    Now it has failed after 14 months of faultless performance.
    There seems to be little help available, but searching for solutions finds plenty of problems.
    On the contrary. At the top of this forum are four *User Contributed Tips,* including one on Troubleshooting that would have saved you a great deal of time.

  • Time Machine Error. Unable to complete backup. An error occurred while copy

    I purchased my iMac 24" in February.
    After I had set up the machine I configured an IceCube Firewire 300 GB (Seagate) Hard Drive as a backup volume and flicked the switch in Time Machine. All went as expected. I even restored my whole hard drive from the Time Machine volume about a month ago after I repartitioned the boot volume to set up Boot Camp. No problems.
    About a week ago I purchased a 500GB WD HDD and set it up inside the IceCube enclosure (I remembered to make it the "Master" disk too!!). I partitioned it with Disk Utility with a GUID Mac OS X (Journaled) partition for my Leopard boot partition, and as MS-DOS FAT32 for my Boot Camp external partition. I used Carbon Copy Cloner to copy all the Windows files across from Boot Camp to the new FAT32 partition and set up Time Machine to make a backup of the Leopard boot partition.
    After several hours Time Machine stopped with the error message above. ("Time Machine Error. Unable to complete backup. An error occurred while copying files to the backup").
    I have spent days formatting the new WD drive, repairing permissions on the boot drive, excluding large files and cache files from the backup in Time Machine to no avail. Every time I get the same message. I even set up another 200GB firewire drive to see if it was anything to do with the enclosure of WD HDD. Same result!!
    I have searched these forums for any ideas, and have done wide searches with Google but nothing has worked.
    I can not understand why my Mac worked perfectly with Time Machine before I installed the new Western Digital Hard Drive.
    What have I missed?

    I keep getting the Time Machine backup error too, like many others. Was fine until just the other day, now, nothing. Although my husband's backs up just fine. I assume it's the 10.5.3 bug everyone else has. I've tried reselecting the drive, running the disk utility, shutting everything on and off... help!
    Here's the console log- anyone know what this means?
    Jun 10 08:37:27 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Starting standard backup
    Jun 10 08:37:27 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Network mountpoint /Volumes/Library not owned by backupd... remounting
    Jun 10 08:37:27 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Network volume mounted at: /Volumes/Library-1
    Jun 10 08:37:43 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Disk image /Volumes/Library-1/Tiffany Danko’s Computer (2)_001b63baf698.sparsebundle mounted at: /Volumes/Backup of Tiffany Danko’s Computer (2)
    Jun 10 08:37:43 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Backing up to: /Volumes/Backup of Tiffany Danko’s Computer (2)/Backups.backupdb
    Jun 10 08:37:48 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Failed to create progress log file at path:/Volumes/Backup of Tiffany Danko’s Computer (2)/Backups.backupdb/Tiffany Danko's computer (2)/2008-06-09-065427.inProgress/.Backup.234797868.792920.log.
    Jun 10 08:37:48 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Event store UUIDs don't match for volume: Macintosh HD
    Jun 10 08:37:48 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Error: (-36) Creating directory 77B4FA27-3E65-4B81-897C-610DEE7BB187
    Jun 10 08:37:48 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Failed to make snapshot.
    Jun 10 08:37:53 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Backup failed with error: 2
    Jun 10 08:37:58 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Ejected Time Machine disk image.
    Jun 10 08:37:59 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Ejected Time Machine network volume.

  • I am running 10.7.5 and getting Time Machine error The backup disk image "/Volumes/Data/Kathy P's MacBook.sparsebundle" is already in use. what do i do now?

    i am running 10.7.5 on an older MacBook and getting Time Machine error The backup disk image “/Volumes/Data/Kathy P’s MacBook.sparsebundle” is already in use. what do i do now?

    See Pondini's TM FAQs, for starters.

  • Question on Time Machine error log

    I have a program (Time Machine Error Log) that keeps track of the message log entries that occurr after you do a Time Machine backup.
    I am getting two messages each time Time Machine completes a backup.
    Here are the two message from the last log:
    Jan 13 17:39:29 xxxxxx-iMac.local com.apple.backupd[36854]: Error: Error Domain=NSOSStatusErrorDomain Code=-36 "The operation couldn’t be completed. (OSStatus error -36.)" (ioErr: I/O error (bummers)) deleting backup: /Volumes/Time Machine Backups/Back
    Last Successful Backup Message:
    Jan 13 17:39:37 xxxxxx-iMac.local com.apple.backupd[36854]: Backup completed successfully.
    How can there be an error reported stating "deleting backup", then a message stating "Backup completed successfully"?
    If I didn't check the log, I wouldn't know that there was a problem, because the Time Machine preferences pane tells me the last backup time, and the next backup time, indicating all went well.
    I just need some verification that my backups are completing successfully.
    Thank
    Len

    There is a lot of rubbish messages that TM produces.. if the final message is that all is good, then I would say all is good.. it is pretty quick to decide when something isn't good.
    But I would say.. there is only one way to know a backup is good. Restore it.
    You don't need to test restore over current drive.. plug in an external drive and restore.
    You can do a verify.. hold the option key whilst clicking the TM icon in the top menu area.. and the option verify will appear.. click that. It really doesn't test more than files are readable though, AFAIK.
    Do a disk image occasionally.. Disk Utility can create an image.. but superduper even free download version can do a full disk image. Makes me feel safer knowing that I have a backup TM doesn't actually have anything to do with.

  • Is there a solution for Time Machine error?

    I got an error in Time Machine saying backup had failed, a couple of days ago. Spent the next day or two trawling the web and found thousands of postings from people with the same error, but no solution.
    (At least, some people had a solution - they were using PC-formatted hard drives.)
    I've been using Time Machine for a few weeks, and it has only now taken a dislike to my external hard drive, which is connected by FireWire.
    Is there a solution to this problem, or should I revert to using SuperDuper, which I was using successfully before?
    I haven't put in lots of information about the apps I'm running, because this is a general query rather than a specific one. If there's a solution, I'll use it; otherwise I'll wipe the drive and go back to using SuperDuper.

    OisinOg wrote:
    Pondini - Thank you for your slightly hostile reply.
    On the contrary. The statement was: +"found thousands of postings from people with the same error, but no solution."+ I don't know where you found thousands of posts -- there are many here, but certainly not thousands. If you're talking about, say, a Google search, if you actually look at them, many are duplicates, unrelated to your problem, or unrelated to Macs at all -- and there are a number of solutions that seem to have fixed many of the real ones.
    The error message was the standard one: "Time Machine Error - Unable to complete backup. An error occurred while creating the backup directory."
    There's most likely another, better message in your logs. Thus the suggestion about Time Machine Buddy. You can also use the Console app (in your Applications/Utilities folder). Click on Show Log List, then navigate in the sidebar to your system.log (or system.log.0.bz2, etc. for previous ones). You can filter for backupd to get the same TM messages as the widget, but I prefer to view the full log at the date/time in question, as messages from other concurrent processes may have a clue.
    I've gone through the suggestions in some of the helpful replies to those thousands of postings, by wiping my drive, erasing it and reformatting it, first in two partitions using the GUID method in Disk Utility, then in a single partition. But Time Machine still doesn't want to back up to it.
    Sounds a bit like a problem communicating with the drive. The logs may clarify that.
    The hard drive of my computer is 250GB; the external drive is 300GB. Both are SATA drives; the external is connected by FireWire.
    How full are they?
    Thanks for your suggestion of downloading the Time Machine Buddy widget; I'll give it a last try tonight.
    What is the difference between a SuperDuper clone and a Time Machine backup?
    The initial backup of both copies almost everything on your HD, excluding only some caches, temp files, etc., although you can exclude other things. This takes quite a while, of course. Thereafter, only the items that changed are backed-up.
    SuperDuper (and CarbonCopyCloner, which I use, and other, similar apps) are most often used to make bootable "clones" identical copies of your HD -- if your HD fails, you can boot and run from them immediately. With TM, once your HD is repaired/replaced, you restore your system to it from your TM backup.
    Score one for the clones, but TM has it's advantages, too (which is why many of us run both).
    First is, CCC and SD look at every file and folder on your HD to see what changed. This is quite time-consuming and CPU-intensive, so most of us run it once a day (or less often), usually automatically at, say, 3 am. TM, however, runs hourly, but uses an internal File System Event Log of changes, so it is far quicker and less intrusive. There are exceptions, but most users rarely even notice the backups unless they see the icon revolving. On my small system, for example, TM rarely runs over 30 seconds; CCC is at least 15 minutes.
    Second, not only does TM keep previous versions of changed files, but it manages the space and backups for you. It keeps those hourly backups for 24 hours; except the first of the day becomes a daily backup which is kept for a month; one per week becomes a weekly backup that is kept for as long as there's space (it will fill the drive/partition). But it's smart enough, as it deletes the old weeklies, that it won't delete it's copy of anything that still exists on your HD.
    There isn't room to have two 250GB sections on a 300GB drive. I suppose I could get another 250GB drive - I have an IDE enclosure somewhere - but I don't fancy the expense right now.
    Your CCC or SD partition only needs to be as large as your HD, although in a pinch it only needs to be somewhat larger than what's actually used on your HD. If you don't have room for both on the one drive, an even better solution might be to get a pair of smaller portable HDs for CCC/SD. Use one daily for, say, a week, then take it to your safe deposit box, workplace, relative's house, etc. and start with the other. Now you're also protected against fire, flood, theft, direct lightning strike on your power lines, etc.

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

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

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

Maybe you are looking for