Skip navigation
This discussion is archived

Error 109 With Time Machine

92794 Views 206 Replies Latest reply: Jun 14, 2010 8:57 AM by lolondonkb RSS
1 2 3 ... 14 Previous Next
Level 6 Level 6 (11,035 points)
Currently Being Moderated
Sep 3, 2009 5:53 PM
So I have a FantomDrives 1TB Hard Drive plugged into my airport extreme router through the USB port and me and my family have been using it for backing up our software, with mine going on one partition and my father and mother on the other. This has been working fine for us for a while now but as soon as we updated to Snow Leopard all of our backups stopped being accessible, ie, none of the .sparsebundles could be mounted. Ironically, we only installed Snow Leopard on two of the computers, but the third computer, an older PowerPC, cannot access its backup for the same reason. Any ideas?
Macbook, Mac OS X (10.4.10), 2 Ghz, 1g of RAM
  • alan73 Calculating status...
    Currently Being Moderated
    Sep 5, 2009 11:20 AM (in response to Merged Content 1)
    I have the same setup with a WD 1TB MyBook and have gotten the same error 109 ever since upgrading to Snow Leopard. I thought I simply had a corrupt mount point so I deleted my backup file and started from scratch. The initial backup went just fine but all subsequent backups failed. Hope something comes of this...
    MacBook Pro, Mac OS X (10.6), Airport Extreme Router, WD 1TB MyBook USB
  • ajfuchs Calculating status...
    Currently Being Moderated
    Sep 6, 2009 11:23 AM (in response to alan73)
    Same problems. WD 1TB plugged into airport extreme.
    MBP09, Mac OS X (10.4.7)
  • Sandman Level 4 Level 4 (3,270 points)
    Currently Being Moderated
    Sep 6, 2009 2:31 PM (in response to Merged Content 1)
    Same here.
    1Ghz 12 inch PowerBook + 10 gig ipod/512 shuffle + 14inch iBook, Mac OS X (10.4.1), 8g iPod touch
  • Pondini Level 8 Level 8 (38,710 points)
    Currently Being Moderated
    Sep 6, 2009 2:45 PM (in response to alan73)
    alan73 wrote:
    I have the same setup with a WD 1TB MyBook and have gotten the same error 109 ever since upgrading to Snow Leopard. I thought I simply had a corrupt mount point so I deleted my backup file and started from scratch. The initial backup went just fine but all subsequent backups failed.


    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. There should be a clue; if in doubt, copy and post the messages from that failed backup here.

    A few folks have had trouble with the Buddy on Snow; if you do, and are familiar with Console, use it and filter for the backupd process; if not, post back for instructions.
    24" iMac 2.66 GHz Intel; 4gb; 640 gb, Mac OS X (10.6), AEBS
  • Neil Stone Calculating status...
    Currently Being Moderated
    Sep 7, 2009 5:39 PM (in response to Pondini)
    I am having a similar problem. Here is the info from the Time Machine Buddy widget. Just upgraded to Snow Leopard. Using an Iomega hard drive connected to the USB port of our Airport Extreme.

    Starting standard backup
    Attempting to mount network destination using URL: (hidden)
    Mounted network destination using URL: (hidden)
    Failed to mount disk image /Volumes/(hidden).sparsebundle (DIHLDiskImageAttach returned: 109)
    Waiting 60 seconds and trying again.
    Ejected Time Machine network volume.

    then it goes thru this series a couple more times before giving up.
    many, Mac OS X (10.6)
  • Sandman Level 4 Level 4 (3,270 points)
    Currently Being Moderated
    Sep 7, 2009 6:10 PM (in response to Merged Content 1)
    I gave up... discarded months of backed up data.. and reformatted my backup disk. I will no longer use TM as it's obviously too picky... I'll be using Carbon Copy Cloner from now on. TM seemed like it was the best thing since sliced bread.. but that's obviously not true
    1Ghz 12 inch PowerBook + 10 gig ipod/512 shuffle + 14inch iBook, Mac OS X (10.4.1), 8g iPod touch
  • sccrzeus Calculating status...
    Currently Being Moderated
    Sep 12, 2009 8:18 PM (in response to Merged Content 1)
    I just encountered this issue after upgrading to 10.6.1. Has anyone come up with a solution?
    Mac OS X (10.6)
  • piglephant Calculating status...
    Currently Being Moderated
    Sep 13, 2009 3:08 PM (in response to sccrzeus)
    I have the same problem. I have two macs (MBP and iMac) and I just installed Snow Leopard on both. Both are using Time Machine through Airport extreme USB to separate partitions on a WD 1Tb mybook.
    Interestingly, the error is only occuring in the MBP, the iMac is still backing up without issue.

    Anybody have a fix?
    MBP Unibody, Mac OS X (10.6)
  • crismoon55 Calculating status...
    Currently Being Moderated
    Sep 14, 2009 12:11 PM (in response to piglephant)
    I have the same problem and the same set up (MPB & iMac) Snow Leopard since the day it was out. Only began to have the error 3 days ago, and only on the iMac.
    What gives? The disk has been rebooted, but still no change. We need a fix not more postulating.
    imac 24, Mac OS X (10.6)
  • deh2k Level 4 Level 4 (1,765 points)
    Currently Being Moderated
    Sep 14, 2009 12:38 PM (in response to Merged Content 1)
    Have you tried to mount your network drive and then reselecting the disk in Time Machine Preferences?

    BTW, the fact that your PPC Mac has trouble too indicates that it's not a Snow Leopard problem. Did you make any changes to your Airport base station? Have you tried rebooting it?
    MacBook Pro, Mac OS X (10.6), My other computer is a Prius
  • Chale Boy Calculating status...
    Currently Being Moderated
    Sep 14, 2009 8:20 PM (in response to Merged Content 1)
    I have the same error after updating to snow leopard. The sparsebundle is unable to mount. It worked fine in 10.5.8
    Mac OS X (10.6.1)
  • deh2k Level 4 Level 4 (1,765 points)
    Currently Being Moderated
    Sep 14, 2009 8:34 PM (in response to Chale Boy)
    Can you open up the NAS disk, find the sparse bundle, and double-click to mount it? If so, what happens if you then select backup now in Time Machine?
    MacBook Pro, Mac OS X (10.6), My other computer is a Prius
  • Danire Calculating status...
    Currently Being Moderated
    Sep 15, 2009 7:18 AM (in response to Merged Content 1)
    I have the same error after updating to Snow Leopard. Using Time Machine on a MacBook connecting through AEBS to a WD 1TB MyBook. The sparsebundle is unable to mount. Worked fine for a year under Leopard.
    iMac, Mac OS X (10.5.1)
  • Chale Boy Level 1 Level 1 (40 points)
    Currently Being Moderated
    Sep 15, 2009 9:12 AM (in response to Merged Content 1)
    If I double click on the sparsebundle, I get a message the disk image couldn't be opened because there was no mountable file systems. Again I was able to backup fine in 10.5.8 with time machine
1 2 3 ... 14 Previous Next

Actions

More Like This

  • Retrieving data ...

Bookmarked By (1)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.