Previous 1 2 Next 16 Replies Latest reply: Mar 2, 2013 10:04 AM by Thomas Schaller
Thomas Schaller Level 1 Level 1 (105 points)

Hi,

I'm having this issue for a coiuple of years now. Recently updated from Snow Leopard to Mountain Lion and thought to give it another try. Same outcome.

Back then I even brought it to the Genius guys and the time machine worked fine.

I created everything from scratch. Set up File sharing in Airport Utility with new name, etc.

 

When I select the new backup disk (my Time Capsule with different name - no facny characters, etc.), Time Machine spends some time first "preparing backup", then I see a volume created (disk image), called Time Machine Backups, and then Time Machine displays: Looking for disk (or similar).

That goes on for a while and then I get the error message:

 

"Time Machine couldn’t complete the backup to “Time Capsule”

The backup disk image “/Volumes/TomsTimeCapsule/Intel Mac mini.sparsebundle” could not be accessed (error -1)."

 

And the Time Machine Backups disk image is still sitting on my desktop, doesn't unmount.

 

In the meantime I do see a sparsebundle file has been created and it is with every try exactly 872.5MB large.

 

here is the log:

Starting manual backup

Attempting to mount network destination URL: afp://xxxxxx@Time-Capsule.local/TomsTimeCapsule

Mounted network destination at mount point: /Volumes/TomsTimeCapsule using URL: afp://xxxxxx@Time-Capsule.local/TomsTimeCapsule

Creating disk image /Volumes/TomsTimeCapsule/Intel Mac mini.sparsebundle

Failed to hide extension on /Volumes/TomsTimeCapsule/Intel Mac mini.sparsebundle, error: Error Domain=NSCocoaErrorDomain Code=4 "The file “Intel Mac mini.sparsebundle” doesn’t exist." UserInfo=0x7ff0cd04b8e0 {NSURL=file://localhost/Volumes/TomsTimeCapsule/Intel%20Mac%20mini.sparsebundle /, NSFilePath=/Volumes/TomsTimeCapsule/Intel Mac mini.sparsebundle, NSUnderlyingError=0x7ff0cd03fa00 "The operation couldn’t be completed. No such file or directory"}.

Failed to eject volume /Volumes/TomsTimeCapsule (FSVolumeRefNum: -122; status: -47; dissenting pid: 0)

Waiting 60 seconds and trying again.

Network destination already mounted at: /Volumes/TomsTimeCapsule

Failed to eject volume /Volumes/TomsTimeCapsule (FSVolumeRefNum: -122; status: -47; dissenting pid: 0)

Waiting 60 seconds and trying again.

Network destination already mounted at: /Volumes/TomsTimeCapsule

Failed to eject volume /Volumes/TomsTimeCapsule (FSVolumeRefNum: -122; status: -47; dissenting pid: 0)

Giving up after 3 retries.

Backup failed with error: 21

[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/TomsTimeCapsule/Intel Mac mini.sparsebundle

 

 

 

Thank you!


Mac mini (Mid 2010), OS X Mountain Lion (10.8.2)
  • LaPastenague Level 8 Level 8 (41,745 points)

    If the issue is long standing and started during Snow Leopard this may point to actual hardware fault.

     

    What model is the TC?? The actual number from the rubber base.. A1xxx will help.

     

    I can only suggest trying it a few different way. That will help narrow down the fault. Whether it is fixable is another question.

     

    1. Does TM complete the backup if you use an external USB drive?

    That will tell us if the issue is network/TC or actually you have internal fault in the mini..

     

    2. Are you using wireless or ethernet? Please try the other.. ie if you use wireless.. turn it off and use ethernet .. you can do it to TC freestanding.. ie no network connections.. just as a test. Using a short patch cable that is known good. If you have tried that, then test with wireless.. it won't be the first TC I have seen where wireless works but the ethernet was faulty.

     

    3. Test by using superduper.. free download will do a disk image.. do image to the TC by network. What happens.. if it fails the issue is pointedly TM. IMHO upgrade install of the OS is to be avoided.. if another backup utiity works.. well either pay for it and forget TM.. or do a clean install of the OS onto a fully reformatted dirve.

  • Thomas Schaller Level 1 Level 1 (105 points)

    OK, did some more testing:

     

    Time Capsule is 2TB 4th generation, A1409.

     

    1: I did a backup to a Firewire HD - only did 50GB, because of limited space on that drive - but Time Machine worked just fine.

    Tried the same limited backup to the Time Capsule - no go.

     

    2: tried Ethernet and wireless - no go.

     

     

    Also: I used the Time Capsule 2TB for the past year as a backup device using backup software and it worked fine - now under Mountain Lion that software isn't compatible anymore. I know there are other options out there, but I really liked the Time Machine when it worked.

     

    And: my daughter cannot do her backup to the same Time Capsule as well from an iMac connected to the home network.

  • LaPastenague Level 8 Level 8 (41,745 points)

    I am also at a bit of a loss..

     

    A full factory reset of the TC and use new names for everything.. short, no spaces, pure alphanumeric.

     

    Erase the TC so you start with a clean slate.

     

    Do a reset of TM A4 http://pondini.org/TM/Troubleshooting.html

     

    Have a look through the C section of pondini and see if some of those other issues could also be yours.

     

    Sorry in a rush now.. post again and I will have another go.

  • Thomas Schaller Level 1 Level 1 (105 points)

    OK, did a hard factory default reset

    wiped the TC clean beforehand

    deleted the com.apple.timemachine plist file beforehand.

     

    And everything still behaves the same way.

    I even tried to log in via my guest account on my computer and tried Time Machine from there.

    Same outcome.

     

    bizarre - seems to me from the log where things go wrong:

     

    Failed to hide extension on /Volumes/TomsTimeCapsule/Intel Mac mini.sparsebundle, error: Error Domain=NSCocoaErrorDomain Code=4 "The file “Intel Mac mini.sparsebundle” doesn’t exist."

     

    then the backup process halts, it tries to eject TomsTimeCapsule, but cannot.

    Next time when I run Time Machine, it creates a new volume: TomsTimeCapsule-1

     

    But even when I manually eject TomsTimeCapsule and try a fresh start, the error from the above log occurs again.

  • LaPastenague Level 8 Level 8 (41,745 points)

    Tell me the whole network layout.

     

    Modem model.. type of broadband.

     

    Is the TC router or bridge mode?

     

    Is the mini using wireless or ethernet?

     

    Can you try again with a completely isolated setup.. This is just a test.. it is to determine if the issue is network fault.

     

    Plug the TC Lan port to the mini with a short ethernet patch cord. No other connections on the mini.. so turn off wireless.. nothing else plugged into the TC. Totally isolated.

     

    Start again with factory reset. That will put the TC back into router mode.. you can then pick up an IP address and the airport utility should connect ok. Ignore all the problems.. except a disk problem.. tell me if AU shows disk issue..  do as little setup as possible.. you are not worrying about network as it is totally isolated.. it is simply to get the TM to work.. start TM. If the TM fails.. I would say the TC is faulty.. if you still have applecare or any warranty left take it back to apple for a checkup/replacement.

  • Thomas Schaller Level 1 Level 1 (105 points)

    I have a Comcast cable modem: Arris Model#: TM702G/CT.

    TC functions as a router

    Mini uses Ethernet, but I tried with wireless as well.

     

    Will try the isolated setup next.

    in the meantime I found somewhere somebody erased all contents of his Library/System Configuration folder as well as the Library/Cache folder. Also deleted the com.apple.TimeMachine.plist file.

     

    Then rebooted and tried again - this time I got the following error log:

    (IntelMacMini is my file sharing name)

    Macintosh is the hard drive name

     

     

    Starting manual backup

    Attempting to mount network destination URL: afp://Thomas%20Schaller@TimeCapsule.local/TimeCapsuleBackup

    Mounted network destination at mount point: /Volumes/TimeCapsuleBackup using URL: afp://Thomas%20Schaller@TimeCapsule.local/TimeCapsuleBackup

    Renaming /Volumes/TimeCapsuleBackup/Macintosh.sparsebundle to /Volumes/TimeCapsuleBackup/IntelMacMini.sparsebundle

    detach: could not open /dev/disk2

    Failed to eject volume /Volumes/TimeCapsuleBackup (FSVolumeRefNum: -106; status: -47; dissenting pid: 0)

    Waiting 60 seconds and trying again.

    Network destination already mounted at: /Volumes/TimeCapsuleBackup

    Failed to eject volume /Volumes/TimeCapsuleBackup (FSVolumeRefNum: -106; status: -47; dissenting pid: 0)

    Waiting 60 seconds and trying again.

    Network destination already mounted at: /Volumes/TimeCapsuleBackup

    Failed to eject volume /Volumes/TimeCapsuleBackup (FSVolumeRefNum: -106; status: -47; dissenting pid: 0)

    Giving up after 3 retries.

    Backup failed with error: 21

    [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/TimeCapsuleBackup/IntelMacMini.sparsebundle

  • Thomas Schaller Level 1 Level 1 (105 points)

    OK, did the isolated setup. Only MacMini was plugged into 1 Ethernet port.

    Did a hard factory reset again.

    Ran AU and only set up necessary stuff.

    Got the same errors.

     

    Then I moved the TC to another computer I have - older MacMini running Snow Leopard.

    Did the same thing - only plugged in Ethernet port to that Mini.

    Hard reset.

    Sparing setup.

    Ran TM.

    And it worked.

     

    Don't think it has anything to do with Snow Leopard vs Mountain Lion, as my problematic Mini also ran Snow Leopard when it didn't work.

     

    I guess next you will tell me to install OS from scratch.

    But how does one do that?

    How do I get a clean slate of OS on my hard drive?

  • Thomas Schaller Level 1 Level 1 (105 points)

    and another test and this one might be even more revealing?

     

    After moving my Time Capsule back to its original location and plugged everything back in (Internet, other Ethernet ports), I went ahead and ran Time Machine from my Snow Loepard Mini wirelessly.

    And it works - backing up as I write this.

     

    So there is some setting on my computer that prevents it from working...

  • LaPastenague Level 8 Level 8 (41,745 points)

    Sounds like it..

     

    Do a verify of the mini's disk.

     

    See A5 in pondini.

     

    But clean install of the OS is a great idea. At least that will prove something about the issue.

     

    Just look up clean install.. there are plenty of posts with instructions and youtube videos etc all showing howto clean install.

  • Thomas Schaller Level 1 Level 1 (105 points)

    no errors found by Disk Utility.

    I guess I have to take the big plunge....

     

    unless somebody knows something else to try?...

  • Pondini Level 8 Level 8 (38,720 points)

    It sounds a bit like the sparse bundle is already mounted, either by another process on your Mac or by the other Mac.

     

    Be sure to eject it, from both Macs, before starting a backup.  Actually, just to be sure, I'd recommend powering both Macs down, then powering-up only the one you want to back up, and starting the backup.  When the "Time Machine Backups" disk image appears on your desktop, don't attempt to mount it or look inside it.

     

     

    I'm not sure your problem is with OSX, but a "clean install" is probably overkill -- if you want a fresh copy of OSX, just install one, via the Recovery HD.  Unless you specifically erase the internal HD, that will just install a new copy of OSX, without disturbing anything else.  See the Reinstalling OSX section in the blue box of  Installing the ''combo'' update and/or Reinstalling OSX.

  • Thomas Schaller Level 1 Level 1 (105 points)

    In my many tries I often have erased the TC disk and then started from scratch - it was definitely not mounted yet.

    I think I'll do the clean install and will report back...

    Thanks

  • munepuppie Level 1 Level 1 (0 points)

    Hello Thomas,

     

    I've been experiencing exactly the same problem you have been and I can attest to the fact that it is totally infuriating.

     

    In my case, I have a 2009 Intel Core Duo MacBook Pro that came with Snow Leopard (if I remember correctly) and a 1TB Time Capsule that provided both my home WiFi and MBP backups. Then all of a sudden, I was constantly experiencing the "sparsebundle -1" errors. After many TC factory resets/erases I thought I had tracked down the problem to the TC itself and went out and bought a new 2TB one (as well as a new HD to install in the previous TC) and then discovered that it I was still having the same problem! And like you I also discovered that my Intel Mac Mini (a secondary computer) was able to utilize the TCs just fine and I am also able to use Time Machine on the MBP with a USB Western Digital drive to make backups. I had reinstalled Snow Leopard (not clean) to no avail. And last night I finally did an update install of Mountain Lion on the MBP thinking that it would probably fix the problem once and for all and it still comes up with the same sparsebundle error. I've even tried using Disk Utility to try to make the sparsebundle file Read/Write (initially it displays as being "Read Only") but that hasn't worked either. And I have been reading about Unix fixes in Terminal on the web to repair a Read Only sparsebundle to the proper Read/Write state but:

     

    a) it's really complicated

    b) I don't care about "recovering" the stupid file

    c) you shouldn't have to do all this jumping through hoops in order to make it "just work" in Apple's own phrasing!

     

    Actually I think a clean install is probable the only option. In my case, I think I'm going to do a clean install of Mountain Lion on a new hybrid (SSD/HDD) 750GB drive and install that in my MBP.

  • Thomas Schaller Level 1 Level 1 (105 points)

    munepuppie,

    I hear your pain!

    Did you see anything about Western Digital causing problems with the TC? I thought I saw somewhere that some people fixed the problem by deleting some WD driver file that came with their external disks. If you haven't, worth googling...

Previous 1 2 Next