Skip navigation
This discussion is archived

Error 109 With Time Machine

92769 Views 206 Replies Latest reply: Jun 14, 2010 8:57 AM by lolondonkb RSS
  • texadian Calculating status...
    Currently Being Moderated
    Mar 5, 2010 2:48 PM (in response to Merged Content 1)
    Ok if there is any doubt that the file name is involved here is the kicker. My macbook backs up to a disk named data 1, i have the error 109. My wife's IMAC goes to data3 works fine. Who said that consistency is the hobgoblin of feeble minds.
  • Vivek Khera Calculating status...
    Thanks rsva for the key to the solution. The only hitch I came across was that the fsck_hfs -rf kept complaining that the device was busy (no write). I decided to run it with debugging on and remove the -f flag since it was a known unclean file system so that was unnecessary anyhow. The fsck_hfs -dr took a good long time, and cleaned up quite well. Backups are moving along again just fine.

    Couple of notes: You don't need to "cd .." multiple times. Just "cd /Volumes" then find your volume. Also, it is not strictly necessary to reboot in between running fsck_hfs twice, nor is it really necessary to mount the USB drive directly. You can run the fsck_hfs on the sparse bundle on the network mounted drive. It is however, necessary to locally attach the USB drive to run disk repair on the whole drive.
    MBP 13", multiple iMac, minis., Mac OS X (10.6.2)
  • Roel13 Calculating status...
    Same here, tried everything. Only thing that worked is rvsa's solution (see page 10 of this topic). Thx !

    btw: The first part did the trick, no need for the second part for me. Probably minor damage.
    MacBook Pro 13" 4GB 2,53, Mac OS X (10.6.2)
  • Roel13 Level 1 Level 1 (0 points)
    Unfortunately, after 3 days the error-109 is back. Will try again and hope that Apple brings out 10.6.3 soon, including a fix for it.
    MacBook Pro 13" 4GB 2,53, Mac OS X (10.6.2)
  • jollyllama Calculating status...
    I see there are specific fixes for Time Machine over Airport in 10.6.3. Anyone know anything about whether these might be in regards to the issue discussed in this thread?
    Intel Core Duo iMac, Mac OS X (10.5.2)
  • Roel13 Level 1 Level 1 (0 points)
    Not sure. To be a bit more sure about my TM backup I started with a fresh backup after updating to 10.6.3. Let's hope this lasts without errors-109.
    MacBook Pro 13" 4GB 2,53, Mac OS X (10.6.3)
  • jollyllama Level 1 Level 1 (0 points)
    In case anyone stumbles on this thread in the future, I just thought I'd post that, after a long time of getting 109's every few weeks after performing the fixes on this thread, I haven't had any problems after updating to 10.6.3.
    Intel Core Duo iMac, Mac OS X (10.6.3)
  • Maverick110 Calculating status...
    Ok ... let me see if I can explain this. I have been getting error 109 every so often over the last year, I noticed that the problem might actually be caused by damage to the drives directory, so whenever I get an error 109 from Time Machine I unmount the drive from the Time Machine, plug it into my iMac, and run Disk Warrior from Alsoft software (, there are usually errors to the drive structure and errors to how the drive is reporting free space. Disk Warrior fixes the drive without a hassle, and I didn't get error 109 for about another month or so. It works so well that when I go to do my usual monthly maintenance on my computer I just include the backup drive. Now I do not get the errors at all.

    My system is an Apple iMac late 2009 edition (which replaced my Mac Pro tower that died last month), an Apple Time Capsule (non dual-band) with a 500 Gigabyte hard drive (which backs up all of the household MacBooks, and MacBook Pros), a 2 Terabyte LaCie Big Disk Dual connected to the Time Capsule via USB to back up my iMac. I also have an Apple AirPort Extreme Base Station (non dual-band) with a 500 Gigabyte Western Digital MyBook Essential used for files that I want access to from any computer in the house.

    I'm not sure whether 10.6.3 solved the problem, or whether my sparsebundle was damaged, but I do know that Disk Warrior keeps things running smoothly for me.

    Hopefully this will help some of you out.
    Apple iMac, Late 2009 21.5", 15" Apple MacBook Pro Unibody 2.4 GHz Intel Core 2 Duo, Mac OS X (10.6.3), MacBook Pro 17" 2.16 GhZ, 2GB; PowerMac G4 1.2 GhZ, 1.5 GB, 500GB
  • Michael Bennett2 Level 1 Level 1 (0 points)
    I also have some USB drives hanging off a Dual-Band AEBS. I've had this error for weeks. After installing Time Capsule Backup Update, it deleted my old backups, but now Time Machine works again.
    Mac Mini (C2D 9400M), Mac OS X (10.6.3)
  • -=X|0g4n=- Calculating status...
    Currently Being Moderated
    Apr 30, 2010 1:06 AM (in response to Merged Content 1)
    Looks like Apple released a Time Capsule Backup Update, Version 1.0. I got mine through software update on 4-28-10. I had to wipe my old Time Machine sparesbundle and rebuild, which lost all my old data. I backup with an AEBS and a USB HD. We'll see if it fixes my 109 errors..
    MacBoo3,1, Mac OS X (10.6.3)
  • RobH78 Calculating status...
    Found rsva's solution on page 10. Worked like a charm for me on my broken AEBS & USB sparsebundle. I highly suggest you give it a try before blowing away the drive and starting new.

    Thanks rsva. Made my day.
    MBP, MB, iPhone, AEBS Gb, AE, XServe, various x86 Lin/Sol/Win
  • lolondonkb Calculating status...
    Currently Being Moderated
    Jun 14, 2010 8:57 AM (in response to Merged Content 1)
    I think I've got the solution....
    I had the same problem and I deleted my sparsebundle and did the back up again and... IT WORKED
    MacBook Pro, Mac OS X (10.6.3)
1 ... 10 11 12 13 14 Previous Next


More Like This

  • Retrieving data ...

Bookmarked By (1)


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