Previous 1 2 3 Next 33 Replies Latest reply: Oct 29, 2012 3:40 PM by joeblotnick Go to original post
  • Pondini Level 8 Level 8 (38,720 points)

    That's amazing!

     

    However, that sparse bundle is now associated with the same Mac as the one you copied those files from -- they contain the ID of the computer that was backed-up.

     

    If you have them both on the TC's internal HD that way, there's no telling what Time Machine will do with them -- which one it will back up to or display.

     

    It will have the Ethernet Mac address of the Mac in question  and/or the HostUUID, depending on what version of OSX you're on.   You should be able to find them via System Profiler (System Information on Lion).

  • gobes7 Level 1 Level 1 (0 points)

    Amazingly, and somewhat unortunatley - I'm having the exact same problem as you.
    Macbook Pro had to get a new harddrive installed, now I cannot reload y backup from a time capsule. However it will show a backup onthe same time capsule from my girlfriends mac.

     

    Would you mind explaining exactly how you managed to fix your sparsebundle? I have a windows 7 PC available to use, conncted via network to the time capsule.

     

    Many thanks!

  • EdinNorway Level 1 Level 1 (5 points)

    Health warning - I experiment a lot so this may not work for you!

     

    In summary, the problem was that I have a time capsule with 2Tb of space that seemed to work fine.  It had a number of flies and folders and two sparse bundles.  One of the bundles, refused to mount i.e. double click would not put the image on my desktop and open in finder.  I could right click and choose "show package contents" and see the "bands" directory, but it was useless in this form.  Because it wouldn't mount, no software data recovery programs would work because they didn't "see" the image.  The other bundle would mount and display all the backup folders.  Other people here helped in suggesting tips but most felt the drive was bad or that the file was too corrupted.  I tried all the things you probably have in trying to get the terminal command hdiutil to work, but it always failed with something like "Unrecognized filesystem".

     

    In desperation, I attached to the TC from a Win7 64bit system and found something curious.  You can see from the screen shots above that Windows showed each bundle as a folder with files in it.  OS X didn't seem to show these to me before.  I opened the files with notepad in Win7 to see what was inside and they seemed to describe the bundle in some way, i.e. included the bundle name and other info.  The bad bundle did not have these info or .plist files, showing only a zero byte file and LSOverride which I deduced was some means for telling OS X how to deal with this unknown file.  I copied these two band bundle files to another location leaving only the "bands" directory then copied the files from the good bundle over to the bad bundle, excluding the "bands" directory from the good bundle.  Basically, I copied the "helper" files from the good bundle to the bad bundle.  I don't know how one does this in OS X, so I had to use Win7 to do that.  after that, I went to my OS X machine and double clicked on the previously bad bundle only to find it worked just as well as the other bundle.  In fact, I found the file from 7 years ago that I was looking for and celebrated with a tall martini afterwards. 

     

    I don't know that this will help you, but good luck.

     

    ed

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

    EdinNorway wrote:

    . . .

    Other people here helped in suggesting tips but most felt . . . the file was too corrupted.  I tried all the things you probably have in trying to get the terminal command hdiutil to work, but it always failed with something like "Unrecognized filesystem".

    Yes, that's kinda the definition of corrupted. 

     

    In desperation, I attached to the TC from a Win7 64bit system and found something curious.  You can see from the screen shots above that Windows showed each bundle as a folder with files in it.  OS X didn't seem to show these to me before.

    It might have, if you'd right-clicked it in the Finder and selected Show Package Contents.

     

    Those files are separate from the data (the actual .dmg is spread across all those zillions of "bands"); I've never seen one where those control files just disappeared, and the rest of the sparse bundle was still (at least somewhat) intact.   (I suspect it's still somewhat corrupted.)

     

    But the first thing to try, gobes7, is to repair it, per #A5 in Time Machine - Troubleshooting.  That will usually fix whatever's wrong.

  • EdinNorway Level 1 Level 1 (5 points)

    Protect those points.....

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

    Excuse me?

  • gobes7 Level 1 Level 1 (0 points)

    Great thanks for the help guys.
    I haven't got any further than trying to migrate from the back up and not being able to find it.
    Not had time since then to do anything but make a copy of the file.

    I'll try that repair guide tonight and see how it goes!

     

    First time I've had to call upon a backup like this so bit lost as to what I need to do as soon as it didn't go smoothly....

  • gobes7 Level 1 Level 1 (0 points)

    Thanks i tried to repair as suggested in disk utility, but the sparsebundle simply won't mount so I can't verify or repair.

     

    When I open package contents i see these files:

    Screen Shot 2012-02-23 at 22.22.40.png


    I also have a working sparsebundle on the same time capsule with the same files available.

     

    Is it these files you replaced?

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

    Those are the correct file names.

     

    What happens when you drag the sparsebundle into Disk Utility's sidebar?  Do you get a message?

  • joeblotnick Level 1 Level 1 (0 points)

    I'm with grantdoug -- Time Capsule has been a disaster since purchase.

     

    2 of 3 macs are continually having sparsebundle / backup / restore failures of various kinds.  Repeated Apple updates haven't fixed the problem.

     

    When I look thru Apple Support, I find all of my problems are very common, with no reliable solution, usually no solution at all.

  • joeblotnick Level 1 Level 1 (0 points)

    Thanks Pondini, I've checked your great resource.

     

    The solution I find required AirPort Utility 5.6, which can't be loaded on Mountain Lion 8.2, which features AirPort Utility 6.1, which no longer supports the "Disconnect All Users" feature, which seems to be the fix for my current "Resource Temporarily Unavailable" problem.

  • joeblotnick Level 1 Level 1 (0 points)

    I see elsewhere that you can Use the Terminal to do a forced disk eject, but I'm afraid to use it, and not sure I'd get command right.

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

    joeblotnick wrote:

    . . .

    The solution I find required AirPort Utility 5.6, which can't be loaded on Mountain Lion 8.2, which features AirPort Utility 6.1, which no longer supports the "Disconnect All Users" feature, which seems to be the fix for my current "Resource Temporarily Unavailable" problem.

    Either use the Pacifist app to extract the app from the Airport 5.6 .dmg, or try shutting down all Macs on your network (or at least disconnecting them from the network), then power the Time Capsule off for a few moments, then back on.

     

    There are some reports that changing the Time Capsule's password will also work, but that probably also requires disconnecting everything.

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

    joeblotnick wrote:

     

    I see elsewhere that you can Use the Terminal to do a forced disk eject, but I'm afraid to use it, and not sure I'd get command right.

    And, if any files are left open, it may cause additional damage. 

     

    As noted in the MAN page:

     

    "Force will force-unmount the volumes (less kind to any open files .  .  ." (emphasis added).

     

    Powering-down each Mac (or disconnecting them from the network), then power-cycling the TC is less likely to cause damage.