Time Machine Error -1: WD Smartware is the culprit!

If you're having problems where your Time Machine will not connect (and it has before) the problem is most likely WD Smartware. This is Western Digital's bundled software on Western Digital external drives and it's a sneaky install, done often without you knowing it.
(See NOTE below if you want to confirm that your data is still on your backup, even though Time Machine is not working)
***SOLUTION: GET RID OF All WD SOFTWARE TO PROPERLY USE TIME MACHINE AGAIN***
DO THIS:
Applications > DELETE all WD Smartware applications
Go to "/Library/LaunchDaemons" (this is root of your HD, where you should see a Users folder) and DELETE these files:
com.wdc.WDDMservice.plist
com.wdc.WDSmartWareServer.plist
Restart your computer.
Try launching Time Machine again.
(It may take a few minutes to renegotiate with the prior backups. It won't show that it's picking back up in the history (meaning it won't show the last date and time, but you can tell it's working if the back up is smaller than a full backup of the entire hard-drive)
This should work! :-)  ... If not, contact Apple Support!
NOTE: If you want to confirm that your data is still on your backup drive (even though Time Machine is not working), do this:
Finder > On left side, under Shared, you should see "Data"
Open "Data". Should see a file named something like "YourComputerName.sparsebundle"
Open this file. (May take a few minutes)
Finder > On left side, "Time Machine Backups" should appear (or mount) under Devices
Select this device on left side.
Should see a folder on right side called Backups.backupdb
Open this Folder. Should see an enclosed Folder named after your computer.
Open this Folder. If your data is still there, you should see a bunch of folders named after each prior backup. These will be named with date and time, which should look something like "2012-06-29-212605" depending on the date and time of your last backup (the last digits represent the time in 24 hour-speak)
If you see this, there is hope. If you don't see this, sadly you've probably got other problems and should contact Apple Support.
Thanks to a few other users and Eric at Apple Support for solving this!!!

This is a Lion bug. compounded probably by the bugs in 7.6 and later firmware of the TC.
Rebooting the TC is disconnecting the users .. Lion is failing to unmount the TC after a backup. Reboot is forcing it to do so.
But if you download and install the non-toy version airport utility for lion.. which still has a disk page.
http://support.apple.com/kb/DL1482
Install and run that exclusively, on the disk page is a simple icon, disconnect all users.. wonder why they have that icon.. well now you know. So you don't need to reboot the TC. Just press the button (icon) so to speak.
The grand guru poobah of TM.. all knowing all seeing Pondini.. has written a KB to help poor struggling padawans.. commonly known as grasshopper.
http://pondini.org/TM/Troubleshooting.html
See C17.. there are a couple of other issues that cause it.. but just get your bug nets.. !!

Similar Messages

  • Time Machine error -6584 can't run the programme, using new time capsule. Help please!

    Bought a new time capsule and it appears to be OK, my Macbook has backed up nicely. Tried to get my imac 27" intel to do the same. Can seee the capsule and can save to the capsule but Time Machine won't run. I just get the error message -6584 .... any ideas anyone?

    The problem seems to be common. Time Machine won't start: i.e. "it"... or the "Stars Wars" thing...
    The following process eliminated the "error -6584"
    Brand new out of the box, 2TB Time Capsule 4th Gen, backed up my iMac 24/4GB/10.7.2 over ethernet with no problems or errors. Time Machine did several incementals over night while I slept. When I returned from work, ready to reimage the OS, I discovered TC hung on an hourly incremental. When I tried to re-establish connection, no dice (error -6584) .
    Several attempts to open the volume failed. I could manage all the preferences and configure the Time Capsule. I just couldn't open the back up or start Time Machine (app).
    I dropped the %HOSTNAME file from the archive folder in Finder into the Disk Utilities image window to verify and repair, but received "file in use".
    Restarting ("reset") the TC oddly resulted in renaming the volume label to "Unamed".  I open Airport Utilities and renamed the archive folder to "Data" as before...
    Now able to mount (login into) the volume... But it shows "--" in available volume space and no "Oldest" or "Latest" backups are displayed...  Not a good sign. Waiting for backup to start..... Looking for backup....
    Odd, instead of failing now, it started an incremental. Done!
    I am now able to open Time Machine (or that cool Star Wars thingy that takes you off somewhere) and review all the backups starting with the first one I created before I went to bed last night.
    The question seems to be what created the problem. I suspect my iMac went to sleep (shut down HDD) in the middle of an incremental. That may have set the "in use" flag on the archive and OS X didn't know how to handle that when I woke the machine up.
    I hope this helps, and corrects my problem permanently.

  • Hi - i got a problem with time capsule stating all of a sudden: time machine error (-1) could not access the image (Name) Macintosh.sparsebundle

    Hi - can anybody support me with a time capsule error message (-1) : could not access macintosh.sparesbundle? mny TXS

    This is a Lion bug. compounded probably by the bugs in 7.6 and later firmware of the TC.
    Rebooting the TC is disconnecting the users .. Lion is failing to unmount the TC after a backup. Reboot is forcing it to do so.
    But if you download and install the non-toy version airport utility for lion.. which still has a disk page.
    http://support.apple.com/kb/DL1482
    Install and run that exclusively, on the disk page is a simple icon, disconnect all users.. wonder why they have that icon.. well now you know. So you don't need to reboot the TC. Just press the button (icon) so to speak.
    The grand guru poobah of TM.. all knowing all seeing Pondini.. has written a KB to help poor struggling padawans.. commonly known as grasshopper.
    http://pondini.org/TM/Troubleshooting.html
    See C17.. there are a couple of other issues that cause it.. but just get your bug nets.. !!

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

    My son played the video game Spore on my iMac Saturday. An hour or two later I sat down at the computer and the Time Machine Error message box was in the middle of the screen:
    Unable to complete backup. An error occurred while copying files to the backup volume.
    I downloaded Time Machine Buddy and this is my error: Error (-36) No Copy/Users/iMac/Library/Application Support/Firefox Profiles

    norauc wrote:
    I am having the same issue, I got the latest security update and then Time Machine just gets stuck for hours and then says error, run Disk Utility, which I have and it says everything is fine. Run Time Machine again and same thing.
    As posted above, see #C3 in Time Machine - Troubleshooting (or use the link in *User Tips* at the top of this forum).

  • 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

  • MacPro backed up to Time Machine, added Mac Mini now get "The backup disk image "/Volumes/Data/Jerry Booher's MacBook Pro.sparsebundle" is already in use." error when Mac Pro tries to back up

    MacPro backed up to Time Machine, added Mac Mini now get "The backup disk image “/Volumes/Data/Jerry Booher’s MacBook Pro.sparsebundle” is already in use." error when Mac Pro tries to back up

    It is standard Mountain Lion error due to the networking ability which is comparable to wet string. (actually that was lion.. it dried out some with Mountain Lion.. higher in the hills perhaps!!)
    See C12 and C17
    http://pondini.org/TM/Troubleshooting.html
    But many people are suffering the same issue..
    And the above is even a little out of date.. you might need to do a reset to the TC.
    Welcome to Apple's beta program for everyone.

  • 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, 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 disk image "/Volumes/----/----MacBook Pro.sparsebundle" is already in use and resource unavailable?

    I have a MacBook Pro 13" 2010 model running Mountain Lion. I have always been able to use Time Machine with my Time Capsule. Just today I have been receiving the same error message whenever I would back up my computer:
    I removed my name before "MacBook Pro". It takes a long time "Looking for backup disk..." first. The disk I put with the time capsule is called Huge Backup, and in Huge Backup there is my sparsebundle file called "----- MacBook Pro." When I open Finder, open my time capsule, and then open my sparse folder, it should mount a drive where I can see my computer's backups. That doesn't work. Then I get this message:
    I once again removed my name before "MacBook Pro" but I can open my sister's sparsebundle who is running Mountain Lion on the same network and her backups work fine. I have researched this topic and have tried to repair the disk in Disk Utility, remount all the drives, remove the drive and restart the backups, and even restart my computer and the Time Capsule. Nothing worked. It just was working yesterday, but now I get this in the settings along with a caution symbol in my menubar:
    Is there anything I could do to fix this? Reconnecting it in AirPort Utility (5 or 6) didn't work. Also, for some reason, the error renamed Huge Backup to Huge Backup-1 as you can see above and below in the messages. I downloaded the Time Machine Buddy widget and this is the error report I got. I replaced my names or private info with [-----]. By the way, the network is called NDR Network, and the Time Capsule is alled NDR Time Capsule. Here's the error I keep getting:
    Starting manual backup
    Attempting to mount network destination URL: afp://[-----];AUTH=SRP@NDR%20Time%20Capsule._afpovertcp._tcp.local/Huge%20Backu p
    Mounted network destination at mount point: /Volumes/Huge Backup using URL: afp://[-----];AUTH=SRP@NDR%20Time%20Capsule._afpovertcp._tcp.local/Huge%20Backu p
    Disk image already attached: /Volumes/Huge Backup/[-----]'s MacBook Pro.sparsebundle, DIHLDiskImageAttach returned: 35
    Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7ff0a483e6c0 {MessageParameters=(
    Ejected Time Machine network volume.
    Waiting 60 seconds and trying again.
    Attempting to mount network destination URL: afp://[-----];AUTH=SRP@NDR%20Time%20Capsule._afpovertcp._tcp.local/Huge%20Backu p
    Mounted network destination at mount point: /Volumes/Huge Backup using URL: afp://Rohan;AUTH=SRP@NDR%20Time%20Capsule._afpovertcp._tcp.local/Huge%20Backup
    Disk image already attached: /Volumes/Huge Backup/Rohan's MacBook Pro.sparsebundle, DIHLDiskImageAttach returned: 35
    Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7ff0a343d430 {MessageParameters=(
    Ejected Time Machine network volume.
    Waiting 60 seconds and trying again.
    Attempting to mount network destination URL: afp://Rohan;AUTH=SRP@NDR%20Time%20Capsule._afpovertcp._tcp.local/Huge%20Backup
    Mounted network destination at mount point: /Volumes/Huge Backup-1 using URL: afp://Rohan;AUTH=SRP@NDR%20Time%20Capsule._afpovertcp._tcp.local/Huge%20Backup
    Disk image already attached: /Volumes/Huge Backup-1/Rohan's MacBook Pro.sparsebundle, DIHLDiskImageAttach returned: 35
    Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7ff0a34410c0 {MessageParameters=(
    Ejected Time Machine network volume.
    Giving up after 3 retries.
    Backup failed with error: 31
    [SnapshotUtilities mountPointForVolumeRef] FSGetVolumeInfo returned: -35
    Failed to eject volume (null) (FSVolumeRefNum: 0; status: -35; dissenting pid: -1)
    Failed to eject Time Machine disk image: /Volumes/Huge Backup-1/Rohan's MacBook Pro.sparsebundle
    Please help!

    I didn't remove all of my names, so just ignore that...

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

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

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

  • Time Machine Error: An error occurred while creating the backup directory

    Time Machine Error: Unable to complete backup. An error occured while creating the backup directory.
    I back up to wirelessly to a Time Capsule. I get these errors often. I'll go for a few days with everything working and then encounter these errors. I've even completely erased the Time Capsule drive and started over. It'll work fine for a few days and then start the errors over again. Interestingly, when the errors occur, the Time Capsule drive can not be unmounted even if clicking the eject button. I am on 10.5.8 but it happened in 10.5.7 as well. I have another Mac that doesn't seem to have any issues with the same Time Capsule.
    Here's a log - they all seem to fail with similar errors:
    Starting standard backup
    Backup destination alias resolved to path: /Volumes/AirPort Disk
    Disk image /Volumes/AirPort Disk/Brittney’s Computer_0019e33d4fde.sparsebundle mounted at: /Volumes/Backup of Brittney’s Computer
    Backing up to: /Volumes/Backup of Brittney’s Computer/Backups.backupdb
    2009-08-27 13:52:48.465 FindSystemFiles[2955:713] Querying receipt database for system packages
    2009-08-27 13:52:48.693 FindSystemFiles[2955:713] Using system path cache.
    Failed to create progress log file at path:/Volumes/Backup of Brittney’s Computer/Backups.backupdb/Brittney’s Computer/2009-08-26-212437.inProgress/.Backup.273091970.250248.log.
    Error: (-50) Creating directory 7CCE60DD-ADCC-4004-A0D9-3EC83D892372
    Failed to make snapshot.
    Backup failed with error: 2
    Failed to eject volume /Volumes/Backup of Brittney’s Computer (FSVolumeRefNum: -114; status: -47; dissenting pid: 0)

    Nancy H wrote:
    I used it as it came, supposedly formatted for a mac.
    It may or may not be right.
    I'd be inclined to start over, per #5 in the Frequently Asked Questions *User Tip* at the top of this forum.
    If that doesn't help, go on to #C10, etc., in the Troubleshooting Tip, as in the previous post.

  • Time Machine Error Prevention - Do Not Use "/" Symbols on the names on HD!

    This is a warning message:
    If your Time Machine Backup Fails with the Message:
    "The Backup Was Not Performed Because an Error Occurred while Copying Files To the Backup Disk. The problem May be temporary. Try again later to back up.etc.."
    *If you Use Symbols In Your Names DONT!*
    *Do Not Use this / slash Symbol on the names of your Hard Drives*! Also check your logs to see if the TM backup is hanging on a file name with : or / symbol.
    *Back Story*
    I had purchased a new 3TB Western Digital HD and needed to do a full backup. I never had issues with Time Machine before. But After trying 2 times and received the error message I new something was wrong.
    I did some research installed the Time Machine Widget and checked Console for the error codes.
    I was searching on the forums here and just read a post from Pandini regarding the use of characters in file names. I was having an issue with an error code #2 every time. I reformatted with a GUID Partition (Intel Only) and verified and repaired the disks and permissions on everything was good on all my HD's.
    After reading his short post about the characters possibly causing the issue I changed the naming on one of the external USB drives to be backed up.
    I had it labeled as "Audio/Video/Docs 1TB."
    I changed to: "Audio Video Docs 1TB" then tried the backup again it worked great.
    It's amazing how a / slash can hang then entire system. I wish Apple would provide some informational notes about these very very simple subtle issues.
    Thanks to Pandini for the post, it was the key clue. Save yourself some time and check your logs and hard drive naming to be sure there are no / Slashes.
    Thanks to everyone on the forum for their contributions.

    Problem solved. Issue resolved. Problem was due to the : or / symbol in the file or HD name.

  • Time machine error: The backup disk image could not be mounted

    Time Machine worked OK for several months. Now I get this error every 10 minutes or so.
    I unplugged Time Machine capsule and "Change Disk" in Time Machine options.
    Nothing helps, I continue to get this error.
    I cannot Enter Time Machine either. "Connecting to Server, Connecting to backup" does not work.
    Help please because I will probably have to archive and reinstall Leopard. I need the backups,
    Christine

    Christ1ne,
    Before you reformat the disk, consider these causes of this error.
    *_"The Backup Disk Image Could Not Be Mounted" (Console - “Failed to mount disk image”)_*
    First, it is important to distinguish this error message from another, similar Time Machine error that states “The backup volume could not be mounted”. This is important as the causes and cures for these two errors can be very different.
    Consider each topic below separately. When one option does not resolve your issue, then move on the next one.
    *Unmount the Backup Disk Image* (TC)
    If, for some reason, you have manually mounted the Time Machine backup disk image (sparsebundle), or Time Machine failed to eject it after the previous backup, subsequent backups may fail. (Console - “Failed to mount disk image”… “Backup failed with error: 21”)
    Eject the backup disk image (white drive icon) by either clicking the little Eject icon to the right of the disk image in the Finders’ Sidebar, or Ctrl-Click the drive icon on the desktop and select “Eject” from the contextual menu. Now try backing up again or launching Time Machine to view previous backups.
    *“Disconnect All Users…”:*
    If your Time Machine backup drive (“Backup of Users Computer”) is mounted on your desktop or in the Sidebar of the Finder window. then Time Machine may think the drive is already in use. Alternatively, if the Time Capsule hard disk has been recently accessed by a Windows machine, it may not have fully relinquished control. Do the following:
    Open Airport Utility and select the Time Capsule on the left.
    Click “Manual Setup”.
    Select “Disks” at top of window.
    Click “Disconnect All Users…” at bottom of window.
    Close the Airport Utility.
    Now try Backing up again.
    One poster reported: “I got it resolved. Apparently it had to do with one of the files being open on the disk from the drive. I had browsed the disk with one of my windows boxes here and it must have left one of the folders "open". Anyway, I rebooted the TC and we are good to go now.”
    *Proper Computer Name* #
    Make sure your computer has a proper name. Go to System Preferences --> Sharing. Time Machine needs to differentiate your computer from others on your network (i.e. "Bills MacBook" or "Office iMac"). If the "Computer Name" field is blank, create a name. Realize that if this step is necessary, you will likely have to start the Time Machine backup process over again and do another full initial backup.
    According to this article, [http://support.apple.com/kb/TS1760], Time Machine may experience problems if your computer name includes certain characters. Make sure the computer name only includes ASCII characters from the following set.
    (0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ)
    Once a change in the computer name occurs, you should stop and restart Sharing on the affected computer. Uncheck and then recheck Sharing in the Services list on the left.
    # Try removing the apostrophe from the disk images name (sparsebundle).
    *A Stalled .inProgress Files:* #
    It may be that the previous backup attempt was ungracefully interrupted leaving remains that Time Machine can’t deal with.
    Stop any current backup attempt. Choose “Stop Backing Up” from the Time Machine menu.
    Open the Time Machine Preferences and turn “OFF” Time Machine.
    Open your Time Machine drive.
    Open the folder labeled “Backups,backupdb”.
    Now open the folder containing backups of the computer in question.
    Are there any “.inProgress” files there. Delete them by dragging the file to the Trash. Or Ctrl-Click the file and select "Move to Trash" from the contextual menu. (Give this time as deleting a large file on an external disk can take a while.)
    Turn Time Machine back “ON”. Now try backing up again.
    NOTE: If the above procedure becomes impossible to perform, try accessing the disk image from another Mac. Some have discovered that attempting a repair from another computer succeeds where the original computer failed.
    Let us know if any of the suggestions above helped to resolve your issue.
    Cheers!

Maybe you are looking for