How to fix a Corrupted Time Machine Backup

The other day time machine decided to stop working for me and kept giving me errors about mounting the backup image. After firing up Console.app I found that the sparsebundle which time machine stores the backup data in was corrupted. This is a bad thing since if I couldn’t find a way to fix the image all my backups for the last 6 months would be lost :(.

My first step on the road to fixing the problem was to open the bundle with “Disk Utility” and see if repair disk would work. To do this you need to drag the back image (the .sparsebundle) and drop it on disk utility. Then you can select the image and press “Repair Disk”. Usually if if you have some disk corruption this would fix it, but not for me.

After working for a couple minutes Disk Util would fail at repairing the disk since it found an “Invalid Sibling Link”. It seems the disk was corrupted and the disk repair utility decided it wasn’t going to repair it. Worried that my backups were gone for good I did some Googling and found that this problem isn’t totally uncommon. It seems that Disk Utility is just fairly bad at repairing disks and that using the “real” disk repair utility fsck_hfs might actually fix the problem.

Of course there’s one problem fsck_hfs has to be used directly on a block device not a “sparsebundle” disk image. Not only that but the volume you run the util on cannot be mounted and OS X always tries to mount the image when you click on it. The solution? Use the command line tool hdiutil to “attach” but not “mount” the image. This makes OS X create a /dev/ device for the sparse bundle but doesn’t actually mount the filesystem.

So combining hdiutil and fsck_hfs we might have a way to fix the disk image. Note: Make sure you turn off Time Machine in the System Preferences panel. We don’t want Time Machine trying to mount our image and back up to it until we’re done making all the repairs.

First I ran hdiutil:

hdiutil attach -nomount -readwrite Bhaal_0011247e3338.sparsebundle

After a minute or two of thinking we had success:

/dev/disk1              Apple_partition_scheme
/dev/disk1s1            Apple_partition_map
/dev/disk1s2            Apple_HFSX

The next step was run fsck_hfs on the main volume.

fsck_hfs -rf /dev/disk1s2

-f is required to force a check since this is a journaled file system. I also used -r to have it rebuild the filesystem catalog for the “invalid sibling link” this is required (thanks Dan). At this point I went out for breakfast since I was running a disk repair utility over my wireless internet to my Linux SAMBA server. After coming back from breakfast we had success!

** /dev/rdisk1s2
** Checking Journaled HFS Plus volume.
** Detected a case-sensitive catalog.
** Checking Extents Overflow file.
** Checking Catalog file.
** Rebuilding Catalog B-tree.
** Rechecking volume.
** Checking Journaled HFS Plus volume.
** Detected a case-sensitive catalog.
** Checking Extents Overflow file.
** Checking Catalog file.
   Incorrect number of thread records
(4, 13716)
** Checking multi-linked files.
** Checking Catalog hierarchy.
   Invalid directory item count
   (It should be 0 instead of 1)
   Invalid directory item count
   (It should be 3 instead of 4)
   Incorrect folder count in a directory (id = 3795486)
   (It should be 0 instead of 1)
** Checking Extended Attributes file.
** Checking multi-linked directories.
** Checking volume bitmap.
** Checking volume information.
   Invalid volume free block count
   (It should be 37267681 instead of 37310834)
   Volume Header needs minor repair
(2, 0)
** Repairing volume.
** Rechecking volume.
** Checking Journaled HFS Plus volume.
** Detected a case-sensitive catalog.
** Checking Extents Overflow file.
** Checking Catalog file.
** Checking multi-linked files.
** Checking Catalog hierarchy.
** Checking Extended Attributes file.
** Checking multi-linked directories.
** Checking volume bitmap.
** Checking volume information.
** The volume Backup of Bhaal was repaired successfully.

111 thoughts on “How to fix a Corrupted Time Machine Backup

  1. Sorry, don’t know much about unix. Always get a

    hdiutil: attach failed – Nicht erkannt (translates to not recognized)

    when entering the command:

    “hdiutil attach -nomount -readwrite ” and the location of the sparsebundle which I added with drag and drop from the finder to the terminal window.

    The complete command then looks like this:

    hdiutil attach -nomount -readwrite /Volumes/FreeAgent\ Drive/Katrin\ Meiers\ MacBook_002332d73aaa.sparsebundle/

    I’m not sure if there is something wrong with the path. The sparsebundle is located on a HD/volume called “FreeAgent Drive” and the sparsebundle has the file name “Katrin Meiers MacBook_002332d73aaa.sparsebundle”.

    Any help appreciated.

  2. This is great. And thank you SO MUCH for posting it. I wish it would fix my problem, though.

    Anybody know what to do with a bad catalog b-tree?

    Executing fsck_hfs (version diskdev_cmds-491~1).
    ** Checking Journaled HFS Plus volume.
    ** Detected a case-sensitive volume.
    ** Checking extents overflow file.
    ** Checking catalog file.
    ** Rebuilding catalog B-tree.
    Invalid node structure
    (14, 50220)
    Invalid record count
    (14, 50220)
    ** The volume Time Machine Backups could not be repaired.

    Thanks!

  3. Hi, I’m glad that I came across this site, but I have a problem with my Time Capsule. How do I run the “hdiutil” when its not attached via USB to the iMac? I am using ethernet cable, but Disk Utility won’t repair it, nor would the Terminal console report any significant progress by copy/pasting your instructions. This is what i get:

    (BTW, disregard the “(MacMini)” part… seems ot be a legacy from when I upgraded and copied everything from the macmini to the new imac.)

    Would appreciate any and all help!!! Thanks

    —-

    Last login: Thu Mar 4 23:01:51 on ttys000
    michael-cheungs-imac-2:~ Michael (MacMini)$ hdiutil attach -nomount -readwrite iMac_002500d151f0.sparsebundle
    2010-03-04 23:09:28.649 hdiutil[975:903] Error loading /Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundle/Contents/MacOS/VirtualPCDiskImagePlugin: dlopen(/Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundle/Contents/MacOS/VirtualPCDiskImagePlugin, 262): no suitable image found. Did find:
    /Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundle/Contents/MacOS/VirtualPCDiskImagePlugin: mach-o, but wrong architecture
    2010-03-04 23:09:28.651 hdiutil[975:903] Cannot find function pointer MacDiskImagePluginFactory for factory 7F1FD83E-6684-11D8-968F-000A957703C0 in CFBundle/CFPlugIn 0x1004169a0 (bundle, not loaded)
    2010-03-04 23:09:28.782 diskimages-helper[977:2103] Error loading /Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundle/Contents/MacOS/VirtualPCDiskImagePlugin: dlopen(/Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundle/Contents/MacOS/VirtualPCDiskImagePlugin, 262): no suitable image found. Did find:
    /Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundle/Contents/MacOS/VirtualPCDiskImagePlugin: mach-o, but wrong architecture
    2010-03-04 23:09:28.784 diskimages-helper[977:2103] Cannot find function pointer MacDiskImagePluginFactory for factory 7F1FD83E-6684-11D8-968F-000A957703C0 in CFBundle/CFPlugIn 0x100125c30 (bundle, not loaded)
    hdiutil: attach failed – No such file or directory
    michael-cheungs-imac-2:~ Michael (MacMini)$

  4. I had thought I was finally onto a winner with these tips. My 999gb TM/TC backup sparsebundle had become unmountable but I’d managed to repair it with diskutility. A few days later, it went corrupt again (don’t recall doing anything to the drive or files) but diskutility had been unable to do anything this time.

    Got the backup drive attached with hdiutil but, regrettably, after a couple of hours, fsck_hfs reported itself unable to repair drive after 3 attempts – incorrect links seeming to be the problem. I ran it again a couple of times without any change.

    Looks like the format is imminent and 6 months’ backups down the pan. TM is great but if I can’t rely on it, it’s less than useful! Maybe I should just switch and run a SuperDuper backup to the disc…

  5. FWIW, I found that even with -noautofsck, snow leopard would auto-fsck, meaning I would get ‘resource busy’ or whatever. I have no idea why it is ignoring my no-auto-fsck request. Whatever.

    To allow the process to go, I ‘ps auxwww | grep fsck’ to find the PID, then ‘sudo kill (PID)’ to kill this fsck so I can run my own.

  6. Works. Nice explanation. Thanks much. BTW, if you did this while you went to breakfast, you eat very, very slowly. Or, I guess, my Macbook Air is very slow. . . .

  7. Another ass saved! My TM backups are generally killed by putting the system to sleep while backing up. So easy for Apple to fix, but I will instead use Time Machine Editor so it’s not churning through backups every hour.

  8. Thanks for the genius level support effort – but it isn’t working easily for me on a MacBook Pro which had been doing successful TimeMachine backups months after Snow Leopard 10.6.3 until last week..

    ** /dev/rdisk1s2
    Executing fsck_hfs (version diskdev_cmds-491.0.2~6).
    ** Checking non-journaled HFS Plus Volume.
    ** Detected a case-sensitive volume.
    Invalid node structure
    (8, 0)

    same response x 4 tries.

    any ideas?

    thanks in advance

  9. Went through all of the directions. Ran fsck_hfs, .sparsebundle was repaired “sucessfully” and ejected the disk. However, am still getting the “disk image unable to mount” error. Got any ideas or is my backup system beyond repair?

  10. Hi All I Tried:
    hdiutil attach -nomount -readwrite -noautofsck -noverify
    Get response:
    hdiutil: attach failed – not recognized

    So I Tried “control” click and Show Package Contents, then I Can see a folder “Bands” which takes forever to open and shows nothing useful when it does

    Any other ideas or help would be greatly appreciated

    Thanks

    Desperate Dave

  11. when I run:
    hdiutil attach -nomount -readwrite My-Mac-Mini_0016cbaf9b2f.sparsebundle
    I get an error
    hdiutil: attach failed – Operation not supported on socket
    Any ideas how to fix this …..

    ————–

    Same problem here.

  12. HELP!!!!
    i’ve run this on terminal :

    MacDee-Pro:~ dinarpermadi$ hdiutil attach -nomount -readwrite MacDee Pro.sparsebundle

    And appears like this :
    hdiutil: attach: extra image argument “Pro.sparsebundle” – “MacDee” already specified
    Usage: hdiutil attach [options]
    hdiutil attach -help

    any help???

  13. Hi a bit of information for all those who are experiencing the “Resource Busy” message after executing fsck_hfs – if you open the Activity Monitor utility application you will see that there is an existing fsck_hfs process running.

    I don’t recommend killing the process just to get yours running, but I do recommend waiting until it completes. Then you will find you can execute your rebuild as mentioned here.

    I impatiently killed the process which allowed me to run mine – but then realised what I’d probably done! It could have been rebuilding some important catalogue on the mac itself – and I just killed it! I’ve yet to find out of course…… wish me luck.

  14. Hi Dinar- your problem is the space in the name of your sparsebundle; put the entire disk image name in quotes:
    MacDee-Pro:~ dinarpermadi$ hdiutil attach -nomount -readwrite “MacDee Pro.sparsebundle”
    and it may work for you. And never, ever put a space in a filename again ;-))

  15. @Rob-
    It’ll be on the TimeCapsule volume TM’s been backing up to- so you’ll need to mount your TimeCapsule drive in the Finder (it should show up in “Shared” in the sidebar), and you should find your .sparsebundle at the top level of the drive- alongside that for any other machines backing up to that TC.

    HTH
    T

  16. @Rob-
    sorry, I was assuming you’re using a Time Capsule… If not, the .sparsebundle will be at the top level of whatever NAS/ SMB share/ other volume that Time Machine had been backing up to…
    T

  17. Excellent post, and the first actual fix for busted Time Machine sparsebundles that I’ve come across. Saved my backup, at least for now, anyway. As an aside, I’ve mirrored with SuperDuper onto an external drive for years, but Time Machine certainly has its place, and has helped me a bunch with some old information that otherwise would’ve been long gone or at best hard to retrieve. Years ago Retrospect was a great solution, but the ease of Time Machine both in backup and retrieval makes it a winner for me. Point: Time Machine good. Broken/unusable sparsebundles bad. This post, fixing same, for free, VERY good.

  18. Great bit of information.

    I’d just like to let people know that if you are using Time Machine with an external drive (not a Time Capsule) you can fix your corrupt backup volume by simply running “fsck_hfs /dev/disk1s2” (replace with your device ID). Disk Utility gives you an easy way to determine your device ID. Just right click the partition, click “Information,” and you’ll see the device ID.

  19. I’ve run into the same problem as several of you.

    I have an iMac (1 TB HD), which have been backed up througt Time Machine to a TimeCapsule (2 TB). The file TM have produced is called iMac.sparsebundle

    Theres several issues that i find really really annoying considering the normal ease of use that Apple got on both soft- and hardware.

    First the TC is impossible to get data/files to and from, its unstable and slow,
    so i had to mount a 2 TB harddrive to the TC and copy the sparsebundlefile to the external HD. The sparsebundle file is 1,12 TB in size, but the iMac HD was about 750 GB full, out of a 1 TB HD.

    Yesterday.. i don’t know what happened, but bottumline is, all 750 GB data is gone, bummer… and no matter how i try to acces the data in the “iMac.sparsebundle” file, its a no go.

    I tried Disc Repair, i tried DiskWarrior, Back-In-Time 2. Booting from the Snow Leopard DVD and using the Utility program that should restore your HD, doesnt recognize the TM/sparsebundle file and thus can’t be used.

    So basicly im F….., i’ve tried working the terminal with you commands, but im a complete newbie to using any of the Terminal tools in OSX.

    Can anyone give me a step-by-step, to the repair/fix, that this thread is about.

  20. Thanks for saving my sparsebundle! My account still can’t login, but I created a new one and copied everything over. Thanks so much for blogging a fix!!! Awesome 🙂

  21. Okay so I have had an issue with at least 2 backups. Both have gone corrupt. The first one had 3 months worth of data that was VERY IMPORTANT to me (if you know what I mean). The other I could give 2 sh!ts about. Your solution helped the most out of all the solutions I saw online. At least I can access my files and get what I need. The only bad thing is that it can’t be added back and used in TM anymore. I have to access the files from the finder window -folder by folder, file by file. When I tried to use it in TM, I got an error message that basically told me that my backup cannot be used. Other times it doesn’t see it at all. Anyways, best of luck to everyone else here. I’ll post a few other tips I found later but for now I have to get back to work!

  22. i have a seagate external hdd ..using as a time machine backup..beside of that ,i also make another folder to keep my stuff such as photo / music & etc …
    Problem: 1. the hdd is not shown on my macbookpro

    i have try the disk utility and go for first aid..its seem showing me “invalid sibling link”

  23. i have a seagate external hdd ..using as a time machine backup..beside of that ,i also make another folder to keep my stuff such as photo / music & etc …
    Problem: 1. the hdd is not shown on my macbookpro

    i have try the disk utility and go for first aid..its seem showing me “invalid sibling link”

    i have tried fsck_hfs /dev/disk1s2 …but it shown

    Billy-Ngs-MacBook-Pro:~ billyng$ fsck_hfs /dev/disk1s2
    ** /dev/rdisk1s2
    ** Checking Journaled HFS Plus volume.
    ** Detected a case-sensitive catalog.
    ** Checking Extents Overflow file.
    ** Checking Catalog file.
    Invalid sibling link
    (4, 16500)
    ** Rebuilding Catalog B-tree.
    ** The volume Time Machine Backups could not be repaired.
    Billy-Ngs-MacBook-Pro:~ billyng$

    please help!!!!

  24. i have also tried

    Billy-Ngs-MacBook-Pro:~ billyng$ fsck_hfs -f /dev/disk1s2
    ** /dev/rdisk1s2
    ** Checking Journaled HFS Plus volume.
    ** Detected a case-sensitive catalog.
    ** Checking Extents Overflow file.
    ** Checking Catalog file.
    Invalid sibling link
    (4, 16500)
    ** Rebuilding Catalog B-tree.
    ** The volume Time Machine Backups could not be repaired.
    Billy-Ngs-MacBook-Pro:~ billyng$

    i seem like not working either…

    HELP

  25. I have followed all of the steps given. But my terminal seems to be stuck on “** Rebuilding catalog B-tree”. I do not know if this step takes a long time or something is wrong.

  26. Thanks to this article and the comment’s
    i could repair my .sparsebundle.
    DiskWarrior 4.2 can only repair a TimeMachine Volume if stored on USB or Firewire drive and used localy
    Not if stored on a OS X 10.5 Server Network TimeMachine Volume (.sparsebundle)

    here some additional comments:

    – I used OS X 10.6.5
    – mount the disk locally on your mac (USB, Firewire no Network)
    – change name of .sparsebundle to the original Name without the timestamp
    (TimeMacine ad’s wile making backup the timestamp
    “Macxx_2011-04-11-103023.sparsebundle” > “Macxx.sparsebundle”)
    – move it to the highest possible level on the hard drive
    – switch to the Mac User Interface to english (System Preferences > Languages & Text)
    (to get the benefit of googling with the english error messages)
    – restart mac (to make shure Disk Utility has killed properly)
    – don’t start Disk Utility

    – start the Terminal
    – check the rights on the .sparsebundle
    (do you (admin) have read write rights? if not change it with:)
    computername:~ user$ chmod -v -v 755 /Volumes/Backup/Macxx.sparsebundle

    – mount Macxx.sparsebundle
    computername:~ user$ hdiutil attach -nomount -readwrite -noautofsck -noverify /Volumes/Backup/Macxx.sparsebundle

    – repair the Macxx.sparsebundle
    computername:~ user$ fsck_hfs -rf /dev/disk2s2
    maybe you have to use “computername:~ user$ sudo fsck_hfs -rf /dev/disk2s2”

    – if the “fsck_hfs” fails to repair try several times.
    (Example: “The volume Time Machine-Backups could not be repaired after 2 attempts.”
    after the third time: “The volume Time Machine-Backups was repaired successfully.”)

  27. So thanks for all the information, both on this page and in the comments.

    I was unable to move forward with just this information, I kept getting “Operation Not Permitted” when I attempted to attach using “-readwrite”. When I ran it without readwrite, or with “-readonly” it would work fine- but obviously the fsck would be limited by the dreaded “(NO WRITE)”. But it worked. I could also manually mount the file system (even though hdiutil and Disk Utility refused, citing “No Filesystems”).

    However I think I found one of the problems. I have it running right now- even though I specified “noautofsck” it’s running anyway- which is fine with me, it’s progress and I’m letting it run.

    So here is the key- I had to change directories into the sparsebundle directory, and inside was the “token”. This token had “uchg” flag set! Take a look like so:

    ls -lO /path/to/name.sparsebundle/token

    If you see the “uchg” flag, this could be your problem if you are getting “Operation Not Permitted” when running “hdiutil”.

    To correct it, I ran: “chflags nouchg token” while inside the sparsebundle directory.

    I was then getting “Resource Not Available”. A new confusing error message, but progress! I had to reboot, and now fsck is running!

    Thanks again everyone!

  28. Thank you SO MUCH for this. My fsck process has been running for ten hours; apparently there’s a lot that needed repairing! Very glad to be able to repair it rather than having to ditch all my backups.

  29. I was trying to run this and i get the error:

    **Checking Journaled HFS Plus volume.
    Invalid number of allocation blocks
    (4294967295, 0)
    **The volume could not be verified completely.

    Ive run it multiple times… any ideas?

  30. In addition to all the precious informations I’ve found on both the article and the comments I would like to add my two cents.
    If after fixing the backup your system stills ask for a new backup to be created (even though you repaired it and both DiskUtility and fsck_hfs will prompt that the disk image is fine after a verify) you have to change a couple of things inside the com.apple.TimeMachine.MachineID-plist that resides in the sparseboundle.
    Just cd to it via terminal as described in other comments and unset the uchg flag on file “token” as mentioned eariler in the comments.
    Then copy somewhere the file com.apple.TimeMachine.MachineID.plist in order to have a backup of that file (just in case), then edit it and if it is present the property “RecoveryBackupDeclinedDate” erase it, then modify the property “VerificationState” to value “1” if it was set to value “2”.
    After that save it and then ALT click on the menubar icon of Time Machine and choose “Verify Backup” from the top-down menu. The Backup sparseboundle disk image should now be paired again with your computer and the verify process should start. If hopefully this verify went fine you can keep using your backup disk image as before.

  31. By the way, if you’re getting a “resource not available” or “resource temporarily unavailable” error with hdiutil, try restarting the external drive. Don’t know why it works, but it does.

  32. Great advice! Worked like a champ when coupled with Rayced’s advice above (comment 83.) and Mike’s (comment 80.)

    Once you believe that you have fixed your backup, it’s not a bad idea to verify the backup. Option click the Time Machine icon on the menu bar and select “Verify Backups”.

    Thanks for posting this.

  33. @Spell: I’m glad my comment was helpful. Can you believe that after les than a month my backup failed again? And again it’s just the filesystem dirty!! I guess it’s time to get a better HD in my Time Capsule, not the one Apple ships and claims to be a server grade HD, while instead it’s just a desktop one.
    A caviar green could be a good choice: it’s not a server grade HD too, but it should be much better than the Hitachi “DeathStar” (that’s its nickname in honor of its well known reliability) that Apple used for the model I own.

  34. I’ve successfully changed the internal hard disk of my Time Capsule to a brand new 2TB Caviar Green Western Digital WD20EARS one.

    This tutorial was very helpful and the operation took about half an hour and was painless.
    Now I can barely hear the new drive spinning (amazing!) as well as resulting in a much cooler operative temperature of the device itself (awesome!).

    I’ve put the old drive inside an USB external case and I would like to move the old Time Machine backups back in the new Time Capsule’s internal hard drive.

    It seems that this copy operation has to go trough AppleShare, even though the hard disk is connected directly to the USB port of the Time Capsule.
    It’s painful.
    It will take about 100 hours or more for a total of 800MB data (I have two Macs backing up via Time Machine to the same Time Capsule plus some old backups of my old Leopard install not used anymore).
    Does anybody knows a better way to let this copy be faster (ie not having it going trough Apple Share)?

  35. Thanks SOOOO MUCH FOR THE GREAT FIX !!!

    It did take a little time, but it worked out very well .. I could see the sparsebundle, but I couldn’t get it to mount .. this did the trick !!

    HOpe I don’t have to use it again, but glad I know what to do now !!!

    LIFESAVER !!

  36. Hi guys! Nice to see this kind of blog + an active community around it. Hope God will be reading this…
    My GF unplugged my TC while doing a backup… and I my sparsebundle seems fked up…
    When I go

    fsck_hfs -rf /dev/disk1s2

    it says

    ** /dev/rdisk1s2
    Executing fsck_hfs (version diskdev_cmds-491.6~3).
    ** Checking Journaled HFS Plus volume.
    Invalid B-tree node size
    (3, 0)
    ** The volume could not be verified completely.

    This
    Invalid B-tree node size
    (3, 0)
    is a hell of a bad boy! Could somebody help me kill him? (and save an innocent sparsebundle)

    Love to my saver.

  37. Another ass saved! Thank you Jthon!!!!!

    I stupidly let Apple Store take out my hard drive. When I got home and found the Time Capsule corrupted I called the store but they had already erased the disk and sent it to be recycled. (what a horrible policy to not give customers the bad drive just in case!)

    I spent 5 days on phone with Apple people to no avail… 27 years of Mac files were gone. 4 more days of stress and depression.. Then found your site. Ran the fix 3x unsuccessfully. Went to bed and ran it one more time. Awoke to magic!

    r.i.p. SJ

  38. I can’t thank you enough for this post. After this incident, I am definitely going to rethink my backup configuration and add multiple layers. Thank you!

  39. Hi,

    if you have the problem with an IOMEGA cloud storage disk, the following might help you.
    1. Activate the root account in OSX and set the password to “sohoXXXX” where XXXX is the password you set for the administer account in the web interface of the IOMEGA cloud network storage.
    2. In the shell su with root. Make sure the TimeMachine disk is unmounted. Enter the directory of the sparse bundle, in my case /Volumes/TimeMachine.
    3. cd into the sparse bundle and use the following command: “chflags nouchg token”
    4. Now kill fsck if it is running: “ps auxwww |grep fsck”. If there is a progress use the PID and do: “kill PID”.
    5. Use hdiutil as mentioned above: “hdiutil attach -nomount -readwrite TimeMachine/BLABLABLA.sparsebundle”
    6. Finally use: “fsck_hfs -rf /dev/disk1s2 ” – the disk name might be different.

    7. DONE and good luck!

    By the way if you want to get ssh access to the NAS you can activate this feature via the web interface in the diagnostics page: https://mydiskname/diagnostics.html

  40. Help

    I get this erorr when i try your repair

    ** /dev/rdisk3s2
    Executing fsck_hfs (version diskdev_cmds-540.1~25).
    ** Checking Journaled HFS Plus volume.
    Catalog file entry not found for extent
    (4, 0)
    ** The volume could not be verified completely.
    is all hope lost or can some one help me ?

  41. Thanks so much for this! This fix has saved all my data. Though I think next time I would do it over a wired connection and not the wireless – i ttook around 30 hours!

    Thanks again!

  42. Have tried to run fsck multiple times on my time capsule… but am getting the same errors each time and finally it all aborts… see the msgs below… PLEASE HELP!!!

    ** /dev/rdisk1s2
    Executing fsck_hfs (version diskdev_cmds-540.1~34).
    ** Checking Journaled HFS Plus volume.
    ** Detected a case-sensitive volume.
    The volume name is Time Machine Backups
    ** Checking extents overflow file.
    ** Checking catalog file.
    ** Rebuilding catalog B-tree.
    Invalid node structure
    (4, 17)
    Invalid record count
    (4, 42)
    Invalid key length
    (4, 640)
    Invalid record count
    (4, 17024)
    Invalid node structure
    (4, 56329)
    ** The volume Time Machine Backups could not be repaired.

Leave a Reply

Your email address will not be published. Required fields are marked *