How to fix the Invalid Sibling Link error

I got this error after a software update that turns on journaling on the Mac OS X filesystem.

The update instructs the user to reboot using the Install Disk and running a Repair operation using the Disk Utility. That was when I discovered the error. Apparently, even the Repair operation could not fix the error.

The solution

Here is the solution, adapted from macosxhints.com:

  1. Reboot into Single User mode (restart, and press and hold Command-S). You will see a black screen with a command prompt.
  2. Type fsck_hfs -r /dev/disk0s2 and press Enter. This will repair the error, and will take a while (~10 minutes). Wait for the operation to complete i.e. until the command prompt appears again.
  3. Type fsck -fy and press Enter. This will check the filesystem again, and confirm that it is now OK. Again, wait for the operation to complete i.e. until the command prompt appears again.
  4. Type reboot and press Enter. This will restart the system to normal.

Good luck!

Why this works

Actually, this is more of why I think this works. (UPDATE 11/01/09: Karl has given a more accurate explanation in comment #102. Thanks, Karl!)

Booting into Single User mode allows you run administrative tools (in our case, fsck, a disk repair tool) without mounting any hard disk partitions or starting any system services. This allows fsck to repair parts of your hard disk (in particular, the /usr directory) which are not usually possible to repair using Disk Utility from within Mac OS X that is loaded from the hard disk itself.

So, alternatively, I think you could in fact use the Disk Utility that is loaded from the Mac Installation DVD to achieve the same success. However, this method eliminates the need for the disk, and thus is useful for those who no longer have the Installation DVD or are just too lazy to find it. Plus, if this is your first time booting into Single User mode or typing such cryptic commands as the above, you’ll find it way cooler ;-)

Why this might not work

As explained above, this method will work only if you have an error in the part of your hard disk that is not normally accessible when you are running Mac OS X. If the problem you face is actually from an external hard disk, I believe that Disk Utility should suffice to correct the error, if the error is repairable (i.e. the error is not because of a hardware defect).

However, if you read some of the comments below, this method has worked for some to correct some errors on external hard disks which Disk Utility cannot; so it’s still worth a try. But there are also some who report that this method does not work, and I suspect that it is because their hard disk is physically defective, in which case, the only solution is to get a new hard disk.

Signs of success

From external web sites

From the comments

A cool thing that they’re all odd-numbered.

Donors

  • Christian Riera of Transition-Area — my first-ever donation!
  • Dave Frey
  • Albert Mapache

Thank you!

P.S.:

  • If this worked for you, please do let me know here :)
    It may serve as a confirmation so that other people would be willing try this method too.
  • This page has had 3500+ visits so far (as of June 2008).
    If you found this useful, please consider donating to my PayPal account :)

130 Comments

  1. bigb

    Worked Great for me ,, thanks

    Posted by bigb on 30 Oct 2007 at 4:14 pm | Permalink
  2. Thanks for the feedback :)

    Posted by introspectif on 31 Oct 2007 at 10:03 am | Permalink
  3. Parthiban David

    It worked like magic. After following your steps I rechecked using disk utility “verify disk” and was happy to see the message “Volume passed verification”

    Posted by Parthiban David on 5 Nov 2007 at 11:35 pm | Permalink
  4. Thanks for the feedback, David :)

    Your name’s very familiar; I think we’ve met before in some military establishment, hah.

    Posted by introspectif on 5 Nov 2007 at 11:37 pm | Permalink
  5. Richard

    This worked perfectly! My machine froze or shutdown thru a power failure, then always took hours to boot-up, but all data & files were OK once booted and otherwise eventually acted normally. Backed all my stuff to an external and tried all the tricks and hints… eventually buying TechTool Pro. All that did was tell me of a problem I already knew of! (invalid sibling link) Running your trick did the job – everything is good again and Disk Utility & TechTool have OK’d everything. This trick worked, whereas the macosxhints you derived this from did NOT work.

    The only thing I had to do differently was change the end of the command to disk0s3 (instead of disk0s2).

    I suggest anyone with a sibling link problem should try this before resorting to buying a utility program, but after running Disk Utility AND backing up their stuff. TechToll, etc. are still always useful to have, but they might not fix this kind of problem…

    Lesson learned, but I did learn a lot about the inner workings of OS X in the process – and Knowing is Half the Battle :-D

    Thanks!

    Posted by Richard on 16 Nov 2007 at 8:52 pm | Permalink
  6. That’s wonderful news, Richard :) Thanks for the feedback.

    Just to clarify to everyone else, /dev/disk0s2 refers to the partition of the affected hard drive, so depending on your computer, it might be /dev/disk0s3 instead. I think installing things like BootCamp might trigger such a difference—I’m just guessing, since I’ve not installed BootCamp myself.

    Posted by introspectif on 16 Nov 2007 at 10:38 pm | Permalink
  7. How is the process differentif it is an external hard drive that gets the unreparable
    “Invalid Sibling Link” error from Disc Utility.
    My internal hard drive with the ox os is ok.

    The disc has 220g Of my illustrations on it! I am using leapord also.

    Posted by Andy H on 19 Nov 2007 at 3:13 am | Permalink
  8. For an external disk, I think it should be fine if you just click the “Repair Disk” button. Have you tried that?

    Posted by introspectif on 19 Nov 2007 at 1:15 pm | Permalink
  9. Jim S

    It worked like a charm! We have had invalid sibling links before, and DiskWarrior always was able to fix it. However, this time DW was unable to fix the problem. I got worried because this MacBook already had one HD fail. So relieved I found this page in my search.

    Thanks again! I have bookmarked this page for future reference.

    Posted by Jim S on 30 Nov 2007 at 3:00 am | Permalink
  10. Glad to hear that, Jim :) Thanks for the feedback.

    Posted by introspectif on 30 Nov 2007 at 10:23 am | Permalink
  11. Jake

    Tried it, did not work for me. This happened:

    **Root file system
    **Checking HFS Plus voume.
    **Checking Extents Overflow file.
    **Checking Catalog file.
    **Rebuilding Catalog B-tree
    **The volume iMac24″ could not be repaired.
    localhost:/ root#

    —————-

    Any ideas? I am somewhat desparate as i cannot start from Tiger Disk, another CD is in the drive and won’t come out.
    Thanks; Jake

    Posted by Jake on 8 Jan 2008 at 6:25 am | Permalink
  12. Hi Jake, thanks for visiting this site.

    I suspect the problem is one of these:

    1. Bad disk. Get it replaced by Apple.
    2. Corrupt installation. Reinstall Tiger, but you have to eject that CD first.
    3. The system is booting from the CD each time. Try manually ejecting the CD.

    Hope it helps :)

    Posted by introspectif on 8 Jan 2008 at 10:41 am | Permalink
  13. Jack

    Hi,
    I’m having this sibling link error with a LaCie triple interface 120GB hard drive. This is what I’m getting when I try this fix:

    jack-bayles-powerbook-g4-17:~ jackbayles$ fsck_hfs -r /dev/disk1s6
    ** /dev/rdisk1s6
    ** Checking HFS Plus volume.
    ** Checking Extents Overflow file.
    ** Checking Catalog file.
    ** Rebuilding Catalog B-tree.
    Invalid node structure
    (4, 3470)
    ** The volume Jack’s Photo Drive could not be repaired.

    Any help would be GREATLY appreciated.

    Posted by Jack on 13 Jan 2008 at 3:20 pm | Permalink
  14. I’m sorry I cannot help you, Jack. However, I could suggest that you backup everything from the drive and reformat it.

    Posted by introspectif on 13 Jan 2008 at 7:10 pm | Permalink
  15. Dustin

    worked perfectly! The guy at Apple basically told me my harddrive was failing and all was lost. Thank god for Google and you guys!

    Posted by Dustin on 16 Jan 2008 at 10:55 am | Permalink
  16. Good for you, Dustin! :)

    Posted by introspectif on 16 Jan 2008 at 2:17 pm | Permalink
  17. booloo

    I’ll add my thanks to the list. Had been fumbling around trying to resuscitate my system without luck (and lamenting the fact that it hadn’t been backed up in a long time). Your recommendations worked beautifully.

    thanks for taking the time to post,
    mark

    Posted by booloo on 16 Mar 2008 at 2:06 am | Permalink
  18. You’re welcome, Mark :)

    Posted by introspectif on 16 Mar 2008 at 3:27 am | Permalink
  19. michael

    thank you!
    all of a sudden my macbook pro wouldn’t startup.
    os x 10.4.9 just rolled on for some time then simmply shut down.
    I have a firewire startup disk and tried disk utility which gave the sibling error and couldn’t repair.
    I was totally stuck, with all my work in the laptop.
    it works! slow, smooth, fast! :)
    thank you again

    Posted by michael on 19 Mar 2008 at 5:49 am | Permalink
  20. You’re welcome, Michael :) Good for you!

    Posted by introspectif on 19 Mar 2008 at 6:26 am | Permalink
  21. concetta mahall ha..

    my maiden name is mahall….my father’s nickname was “taj” just a little note….
    i have just come across your tip after searching ‘invalid sibling link’ i downloaded updates on the 6th and after reboot, i cannot access mail safari itunes quicktime….. i just found this error and i would like to try your solution. will i lose any of my mail messages, etc. i am new to mac operating system so this will be a new learning experience. appreciate your help. i did download pacifist, but have not been able to open it. probably a good thing as i might do more harm than good! thanks, c. mahall. h. ;)

    Posted by concetta mahall ha.. on 9 Apr 2008 at 11:05 pm | Permalink
  22. For me, this error didn’t affect my ability to launch any of the applications; it showed only when I run “Verify Disk” using Disk Utility. I suspect that you are facing a different problem, so perhaps the solution is something else.

    Posted by introspectif on 9 Apr 2008 at 11:58 pm | Permalink
  23. Eunice

    I’m trying this on my MacBook right now while booted from the leopard DVD. About how long should rebuilding catalog b tree take? The first time I ran it, it kept giving ‘invalid node structure’ messages or similar so I quit out and tried it again. Now it’s been at rebuilding for 20 minutes. Am I a hopeless case? Will this only work in single user mode? I don’t know if I can get there as my hard drive seems to hate me and the mac is pretending it doesn’t exist. Thanks so much anyhow.

    Posted by Eunice on 17 Apr 2008 at 11:12 pm | Permalink
  24. It did take quite a while for me, I think about 10 – 15 minutes. I guess if your disk is really bad, it would take longer. Hope it helped.

    Posted by introspectif on 18 Apr 2008 at 12:32 am | Permalink
  25. Any idea how this would work on a Time Capsule drive? I tried it and it gave a permissions error. I tried repairing it through Disk Utility and it gave errors.

    Posted by Simon on 20 Apr 2008 at 9:58 am | Permalink
  26. I’m sorry, Simon, I don’t have a Time Capsule to try it out.
    Have you tried ‘Repair Permissions’ from Disk Utility?

    Posted by introspectif on 20 Apr 2008 at 12:06 pm | Permalink
  27. SeeS

    Thank you.
    It worked great. You rock, man

    Posted by SeeS on 24 Apr 2008 at 9:32 am | Permalink
  28. Glad to hear that.
    You’re welcome.

    Posted by introspectif on 24 Apr 2008 at 4:12 pm | Permalink
  29. Tiron

    :-(( Didn’t work for me …
    the volume could not be repaired.

    What next?

    T.

    Posted by Tiron on 1 May 2008 at 9:02 pm | Permalink
  30. I’m sorry, I can’t help you further.

    Posted by introspectif on 2 May 2008 at 11:20 pm | Permalink
  31. Shell

    I got this message – missing thread record; missing directory record; invalid index key…. still waiting for final verdict. Taking ages. by the way is it zero or Os2?

    Posted by Shell on 20 May 2008 at 1:01 pm | Permalink
  32. It’s a zero.

    Posted by introspectif on 20 May 2008 at 1:56 pm | Permalink
  33. Shell

    just told me there is no 0s2, so i tried 0s3 and that is spewing out lots of messages about missing threads, directories, etc… seems like it will never give me a prompt so i can wrap it up.

    Posted by Shell on 20 May 2008 at 3:02 pm | Permalink
  34. Seems like you’ve got quite a bad disk over there; that’s why it’s taking a long time. Another possible reason why it’s taking forever is that there’s a physical defect with the disk—which *might* not be repairable using this method. If all fails, it’s best to save the files that you can still retrieve and get a new hard disk.

    Explanation about disk0s2: disk0 refers to the first physical disk, whereas s2 refers to (I believe) the third partition of the disk. In my MacBook, disk0s2 is refers to the Mac OS X partition, whereas disk0s3 refers to my Windows XP partition (Boot Camp). So chances are, you’ll only need to fix disk0s2, your Mac partition.

    Hope this helps.

    Posted by introspectif on 20 May 2008 at 4:00 pm | Permalink
  35. Rebecca

    Sorry to be a pain – I can usually fumble around technically but as this is my boyfriends mac mini I want to make sure I get it spot on!

    We have a 1TB Lacie drive with all of itunes & iphotos, apps etc stored on it. We have had the lacie drive almost 2 years and all of a sudden it would not be recognised and the icon disappeared from the desk top. on going into utilities and verifying I am getting the ‘invalid sibling lilnks’ ‘hfs plus volume’ etc

    I cannot repair at all. I have been on google and have read horror stories on what can & can’t be retrieved from the drive,

    Please can you go through the instructions of what to do for a non techie person, who has the logic to do it.

    thanks

    Posted by Rebecca on 22 May 2008 at 11:07 pm | Permalink
  36. What does it say when you try to repair it using Disk Utility? I think the Disk Utility should suffice if you’re using an external drive.

    Posted by introspectif on 22 May 2008 at 11:10 pm | Permalink
  37. Rebecca

    Hi There!

    I am in disk utilities and I have clicked onto the lacie on the left have nav bar.

    I got the following:
    Verifying volume “lacie Disk”
    Checking journaled HFS Plus volume
    Checking Extents Overflow file.
    Invalid sibling link
    Volume check failed.
    Error: Filesystem verify or repair failed

    The popup:
    First Aid Failed
    Disk utility stopped verifying “LaCie Disk” because
    The following error was encountered:
    Filesystem verify or repair failed.

    (only option is to click OK)

    I have checked power supply to the lacie and I have tried switching from USB to Firewire 400 (lacie supports 400 & 800, but mac mini is only USB & firewire 400)

    Same thing time and time again.

    Posted by Rebecca on 22 May 2008 at 11:20 pm | Permalink
  38. Inside Disk Utility, select Disk Info, and take note of the ‘Disk Identifier’ value. Then click Unmount.

    Now open Terminal (under Applications, Utilities) and try the following:

    fsck_hfs -r /dev/<the disk identifier value which you noted>

    Posted by introspectif on 22 May 2008 at 11:29 pm | Permalink
  39. Rebecca

    Strange one but I have 2 sets of info – is this normal ? If so I will follow your instructions, but on which one – I only have 1 lacie disk

    Name : LaCie Group SA
    Type : Disk

    Partition Map Scheme : Apple Partition Map
    Disk Identifier : disk1
    Media Name : LaCie BigDisk Extreme Media
    Media Type : Generic
    Connection Bus : FireWire
    Connection ID : 58629683847496998
    Device Tree : fw/node@d04b6307060526/sbp-2@c000/@0:0
    Writable : Yes
    Ejectable : Yes
    Mac OS 9 Drivers Installed : Yes
    Location : External
    Total Capacity : 931.5 GB (1,000,215,699,456 Bytes)
    S.M.A.R.T. Status : Not Supported
    Disk Number : 1
    Partition Number : 0

    Name : LaCie Disk
    Type : Volume

    Disk Identifier : disk1s6
    Mount Point : Not mounted
    File System : Mac OS Extended (Journaled)
    Connection Bus : FireWire
    Device Tree : fw/node@d04b6307060526/sbp-2@c000/@0:6
    Writable : Yes
    Universal Unique Identifier : BA1B5739-098D-33AB-BDEA-9722E26D97CB
    Capacity : 931.5 GB (1,000,215,040,000 Bytes)
    Owners Enabled : No
    Can Turn Owners Off : Yes
    Can Be Formatted : Yes
    Bootable : Yes
    Supports Journaling : Yes
    Journaled : No
    Disk Number : 1
    Partition Number : 6

    Posted by Rebecca on 22 May 2008 at 11:36 pm | Permalink
  40. Rebecca

    sorry by ‘unmount’ do you mean eject?

    Posted by Rebecca on 22 May 2008 at 11:38 pm | Permalink
  41. Yes, it is normal. Use disk1s6. So that’s

    fsck_hfs -r /dev/disk1s6

    followed by <Enter>

    Posted by introspectif on 22 May 2008 at 11:40 pm | Permalink
  42. I meant Unmount. If the Unmount button is disabled, then skip the step.
    Proceed to running the command in the Terminal.

    Posted by introspectif on 22 May 2008 at 11:41 pm | Permalink
  43. Rebecca

    got the following

    fsck_hfs -r /dev/disk1s6
    ** /dev/rdisk1s6
    ** Checking Journaled HFS Plus volume.
    ** Checking Extents Overflow file.
    Invalid sibling link
    (3, 56)
    ** Volume check failed.

    Posted by Rebecca on 22 May 2008 at 11:45 pm | Permalink
  44. I’m sorry I can only help you this far. Perhaps you could try to Google for another method to fix it, or contact Lacie for help. If all fails, I guess you’ll just need to get a new disk.

    Posted by introspectif on 22 May 2008 at 11:50 pm | Permalink
  45. Rebecca

    ok – well thanks very much for your help – I do appreciate you taking the time

    Posted by Rebecca on 22 May 2008 at 11:52 pm | Permalink
  46. Andrew

    Hi, i want to try to backup my information on my corrupted disk, i’ve tried many things, and now i’m down to terminal. i’ve tried using the fsck_hfs -r /dev/disk0s2 method and it sometimes works. i’ve tried mounting my laptop to another computer to recover the files, but i accidentally stopped it mid-transfer and now the laptop isn’t recognized on another computer. any software ideas to recover my data?

    Posted by Andrew on 27 May 2008 at 7:46 am | Permalink
  47. 1. Run Disk Utility from the Mac OS X Install disc and try to repair the disk again.

    2. Boot a Linux Live CD (any distribution should do), mount your hard disk, mount a USB drive, and copy files from your hard disk onto your USB drive. Here is one guide on how to mount your OS X hard disk: http://jclark.org/weblog/2005/05/24/ubuntumount/

    Hope that helps :)

    Posted by introspectif on 27 May 2008 at 8:19 am | Permalink
  48. Texcor

    Hey,
    I am working through this right now and I don’t know iff this would fix the problem but my questions is…how can i save all the data on the hdd before I format it?
    Is there and free way to get the data of the disk?

    appreciate ur helo

    Posted by Texcor on 6 Jun 2008 at 10:19 am | Permalink
  49. You could use a Linux Live CD to mount the hard disk so that you can copy files from it into, say, a USB drive.

    Posted by introspectif on 6 Jun 2008 at 7:16 pm | Permalink
  50. worked like a charm, only took me 4 rounds of repairing attempts and some sweat. i guess you know what im going to do next. backing up everything! Thanks!

    Posted by dick on 13 Jun 2008 at 6:46 am | Permalink
  51. Dave

    Invalid Sibling Link on External Hard Drive:
    I experienced the error on a Freeagent external drive that I was using storage for all of my music files and photographs on my Macbook. I tried calling the company (Seagate) for a fix and they told me to (a) send them my drive and they’d recover the data for $700, or (b) Google the fix (yes, they honestly told me to Google the fix).

    So, I found this site, ran the fsck commands (having not used this kind of interface since playing video games DOS in the 1980’s, this was quite scary for me), but the issue did not get fixed. I called Seagate back and finally got a competent rep on the phone. The fix they provided was quite simple:

    1. Have both your computer and the external hard drive connected by the USB cord and powered up
    2. Go to Applications>Utilities>Disk Utilities
    3. Verify that your external hard drive is visible in the drive listing on the left side of the window
    4. Select your external hard drive from the list
    5. Click on the RAID tab. Ensure that the “Volume Format” is set to Mac OS Extended (Journaled)

    If you made it through steps 3-5, the drive is apparently okay and the issue is with mounting it to your computer.

    6. Unplug the USB connection on the external hard drive end (not from the computer) so you just have the USB cord connected to your computer
    7. Unplug the external hard drive from its power source
    8. Shut down your computer (not a Restart)
    9. Wait a minute or so and Restart your computer. Let it start up all the way before proceeding
    10. Plug the external hard drive back into the power source
    11. Plug the USB cord (which should be plugged only into your computer at this point) into the external hard drive

    The external hard drive should show up on your desktop in a moment or so. This worked for us, and I really hope it works for you all.

    Posted by Dave on 25 Jun 2008 at 6:37 am | Permalink
  52. Thanks for sharing, Dave.

    Posted by introspectif on 25 Jun 2008 at 8:52 pm | Permalink
  53. I tried it for an external drive that Finder wasn’t seeing when connected via USB, but Drive Genius was (and was able to erase) via FireWire. I got the disk#s# from Drive Genius, but couldn’t boot from the Leopard DVD, so I tried this method, and it just said the disk in question couldn’t be found. It seems the external drive, without any assigned name, changes its disk name with every reboot. Any idea on what I can do?

    Posted by Azurite on 4 Jul 2008 at 4:57 pm | Permalink
  54. Try comment #51:
    http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/#comment-4284

    Posted by introspectif on 4 Jul 2008 at 5:25 pm | Permalink
  55. Davy W

    This worked for me too, many thanks I thought it was a lost cause.

    Posted by Davy W on 8 Jul 2008 at 6:39 am | Permalink
  56. Henrik Christiansen

    I had the same problem, but when I ran the first command it had three attempts, then it gave up.
    It says that some directories are missing, and then “The volume Macintosh HD could not be repaired after 3 attempts.

    FILE SYSTEM WAS MODIFIED”

    Any tips are greatly appreciated!

    Posted by Henrik Christiansen on 11 Jul 2008 at 8:35 am | Permalink
  57. Henrik Christiansen

    Wait, nevermind. I ran fsck -fy, and it managed to repair it.
    Thank you so much for this guide!

    Posted by Henrik Christiansen on 11 Jul 2008 at 8:36 am | Permalink
  58. You’re welcome :)

    Posted by introspectif on 11 Jul 2008 at 2:29 pm | Permalink
  59. SanMichele

    Deo Gratias! It worked on my Black MacBook the very first time!!! Thanks so much all of you! SanMichele+

    Posted by SanMichele on 15 Jul 2008 at 11:04 am | Permalink
  60. istara

    OK I am trying the Terminal command now, so far I have:

    ** /dev/rdisk1s12
    ** Checking Journaled HFS Plus volume.
    ** Checking Extents Overflow file.
    ** Checking Catalog file.
    ** Rebuilding Catalog B-tree.

    How long should I wait? eg how long should the rebuilding take and how will I know if/when it has happened or not?

    Posted by istara on 15 Jul 2008 at 7:56 pm | Permalink
  61. istara

    It has worked! I had to run the terminal command twice: the first time seemed to repair some things, but then had a Bus Error.

    However the second time it repaired successfully, and now mounts and can be accessed again.

    introspectif: thank you SO much, you have saved my sanity (and my data!)

    Posted by istara on 15 Jul 2008 at 8:19 pm | Permalink
  62. You’re welcome, SanMichele and istara :)

    Posted by introspectif on 15 Jul 2008 at 8:34 pm | Permalink
  63. Adam Walczak

    Thank you so much!

    My computer had this error while I am out of the country – so I couldn’t get to an Apple Store.

    It worked perfectly – saved me from having to go service tech and pay a lot of money.

    Thanks again!

    Posted by Adam Walczak on 28 Jul 2008 at 2:42 am | Permalink
  64. You’re welcome, Adam :)

    Posted by introspectif on 28 Jul 2008 at 6:53 am | Permalink
  65. I Ran Disk Utility, Repair Disk, and it told me ‘Invalid Sibling Link’. I then rebooted and held down command S, and booted into single mode.
    I ran the commad you suggested, and it found a problem with the amount of file numbers, and corrected the problem -and said repair successful. Then, I ran the verification to check again, and it was all good. When I rebooted, still the drive did not mount. When I ran the procedure again, it again found files didnt match and corrected the problem. But on reboot, still the drive wont mount. I guess I have a dodgy drive?

    Posted by Peter de Beer on 1 Aug 2008 at 4:34 am | Permalink
  66. Something makes me think I am repairing the wrong drive?
    **checking Volume Information.
    Invalid volume file count
    (it should be 781324 instead of 781323)
    invalid volume free block count
    (it should be 13568147 instead of 13568170)
    Volume Header needs minor repair (2, 0)
    .
    .
    .
    **The volume Macintosh HD was repaired successfully.

    ***** FILE SYSTEM WAS MODIFIED*****

    I know what I was doing wrong. I was repairing the internal HD, which is fine. Using Disk Utility, it says my external HD is disk 2 partition 0 ,

    I tried that

    fsck_hfs -r /dev/disk2s0

    and it says:

    cant stat /dev/disk2s0
    cant stat /dev/disk2s0: No such file or directory

    Posted by Peter de Beer on 1 Aug 2008 at 5:08 am | Permalink
  67. (replied Peter via email)

    Posted by introspectif on 2 Aug 2008 at 7:01 am | Permalink
  68. Anton

    Thanks a lot from Amsterdam! You just saved me a lot of time!

    Posted by Anton on 4 Aug 2008 at 5:43 pm | Permalink
  69. Clarissa

    Thank you SO much. Your instructions were easy to run, but my HD seemed way too messed up. After 15 min and loads of checking and repairing, it finally said UNABLE TO REPAIR.
    Thanks to Henrik Christiansen’s comment saying he tried fsck -fy after repair failled, this was what did it for me! So thanks to everyone you has taken the time to post as well. Will definetly keep you bookmarked mahalkita.

    Posted by Clarissa on 6 Aug 2008 at 3:19 am | Permalink
  70. You’re welcome, Anton and Clarissa :)

    Posted by introspectif on 6 Aug 2008 at 10:48 am | Permalink
  71. David

    I tried your original suggestion and nothing happened. I then ran fsck -fy and saw that the disk was 05. I then re-ran fsck_hfs -r /dev/disk0s5 and now get the message “The volume Macintosh HD could not be repaired.” What do you suggest? Is any data retrievable? thanks much!
    Dave

    Posted by David on 10 Aug 2008 at 4:59 pm | Permalink
  72. Dave Frey

    You just saved me a lot of data (3 weeks and 10000 km from my TM backup). Thanks for your clear, careful post. I shot you a paypal donation.

    FWIW, I did lose a few iPhoto “events,” photos and all; I’m guessing fsck_hfs does a best effort repair and couldn’t get everything back.

    Now I’ve been duly prodded into researching a proper on-the-road backup strategy…

    Posted by Dave Frey on 17 Aug 2008 at 4:58 am | Permalink
  73. Ivan

    Thank you so much for saving my data!

    Posted by Ivan on 22 Aug 2008 at 6:22 pm | Permalink
  74. SAMUEL

    It works!!! thanks!! I almost gave up and thanks God I found your website! Thank you!!

    Posted by SAMUEL on 25 Aug 2008 at 10:52 pm | Permalink
  75. Melissa

    THANK YOU!!! I had tried everything and this worked for me! Thank you!!!!

    Posted by Melissa on 30 Aug 2008 at 3:10 am | Permalink
  76. You’re welcome, all of you :)

    Posted by introspectif on 4 Sep 2008 at 12:25 pm | Permalink
  77. Ozgur

    Thanks, its work for me..
    Same problem, error after a software update too…

    Posted by Ozgur on 8 Sep 2008 at 5:32 am | Permalink
  78. Isaac Boehman

    I LOVE YOU!!!! <333333333333333

    http://discussions.apple.com/thread.jspa?messageID=8048158&#8048158

    Posted by Isaac Boehman on 10 Sep 2008 at 7:35 am | Permalink
  79. Eh? :)

    Posted by introspectif on 10 Sep 2008 at 7:38 am | Permalink
  80. michael

    Thanks for this! It really helped! My answer was actually in the comments!

    Posted by michael on 10 Sep 2008 at 10:11 pm | Permalink
  81. Ryan

    As many others I’m having this same problem. It started when someone kicked the power cord out of my external drive, mac hasn’t liked it since. In disk utility I can see the 500g maxtor, select it, i can select the raid tab and see Mac OS Extended (Journaled) but when running Verify Disk I get the Invalid Sibling Link. Volume check failed.

    I attempted comment 51 (could it be that easy?) and no, it wasn’t that easy.
    I attempted comment 38 and when I hit enter after typing in the terminal command I get
    ** /dev/rdisk2
    Then it returns to my command line and nothing else happens. Same with fsck_hfs -fy /dev/disk2.
    Also, attempted to restart holding C down and entering terminal there, and restarting holding down S. The commands seem to have the same effect no matter where they are run from.

    All roads lead to a Invalid Sibling link. Any other suggestions or something I’m doing wrong? THanks in advance.

    Posted by Ryan on 11 Sep 2008 at 1:45 pm | Permalink
  82. Ryan

    **Updated – Somehow managed to get it to run under Command S startup thanks to someones partition comment. Now when running fsck_hfs -r /dev/disk1s3 it bombs out and can’t repair after three times, tried several more. Verify disk gives me Incorrect number of thread Records. Repair disk bombs after 3. fsck -fy /dev/disk1s3 gives me

    BAD SUPER BLOCK: MAGIC NUMBER WRONG
    LOOK FOR ALTERNATE SUPERBLOCKS? yes
    SEARCH FOR ALTERNATE SUPER-BLOCK FAILED. YOU MUST USE THE -b OPTION TO FSCK TO SPEIFY THE LOCATION OF AN ALTERNATE SUPER-BLOCK TO SUPPLY NEEDED INFORMATION; SEE fsck(8).

    I like the 3 different variations of super block mac has. Any ideas?

    Posted by Ryan on 11 Sep 2008 at 2:20 pm | Permalink
  83. xkont

    i run applejack and got the problem (not sure if applejack did it)

    it DID work
    thank god your post is top-google and got it right away.

    thanks alot

    Posted by xkont on 12 Sep 2008 at 3:28 am | Permalink
  84. Francois

    Worked very fine for me too. Your help was greatly appreciated.

    Posted by Francois on 15 Sep 2008 at 6:38 pm | Permalink
  85. Ryan

    **Update – As a last resort I installed and tried DiskWarrior. It actually worked like a charm. Surprised me considering all the comments I’ve heard about it, but whatever works right?

    Posted by Ryan on 17 Sep 2008 at 9:47 pm | Permalink
  86. joanna

    No.38 worked for me – an external LaCie/Seagate HD that had suddenly gone to limited functionality. Very grateful thanks to Andy M (who passed on your info to me) and the comments and info. on your fixing sibling error site. This is why I love the net – the generous sharing! Thank you.

    Posted by joanna on 5 Oct 2008 at 9:30 pm | Permalink
  87. bo pedersen

    Thanks it worked ;) you saved my day (and my files)

    Posted by bo pedersen on 17 Oct 2008 at 10:47 am | Permalink
  88. #51 Worked! Big exhale! Very Happy! ;^D

    Posted by Will Pool on 2 Nov 2008 at 3:08 am | Permalink
  89. LEO BORGOGNO

    THANKS!!!, THANKS!!!, THANK YOU VERY MUCHHH!!!!! it work great for me. It hapens just when i was using the migration asist to do a backup in another macbook!! Now i dont want to turn off the mac jaja! Dont you know other way to do the migration (iam using a firewire) to copy all the aplication and my files in my new mac????

    Posted by LEO BORGOGNO on 2 Nov 2008 at 2:43 pm | Permalink
  90. Mike

    I tried running this command once and it failed. The second time, it started working, fixing first the sibling link error, then going through and fixing all kinds of errors (incorrect number of thread records, invalid directory item count, etc).
    It took awhile, and then gave an error that it couldn’t repair the volume after 3 attempts. I then ran the standard /sbin/fsck -fy and it reported that it repaired the catalog file. I then ran fsck again to be sure it could run without reporting any errors.

    This problem had gotten severe enough that the only way I could boot the machine was to boot into single user mode, mount with the /sbin/mount -uw / command and then exit. Otherwise it would start to boot normally, and then just shut off suddenly.

    Thanks!

    Posted by Mike on 8 Nov 2008 at 3:28 am | Permalink
  91. Thanks to all who gave feedback :)

    Posted by introspectif on 11 Nov 2008 at 3:15 pm | Permalink
  92. Glenn

    I had the “invalid sibling link” error on a 1TB Lacie RAID setup (two 500GB drives spanned to form a 1TB drive, mirrored to another 1TB drive). I unplugged the 1TB drive so I was only working on one half of the mirror, leaving me a back-up if things went poorly.

    Disk Utility, fsck_hfs, and fsck all failed to make any progress, but, Disk Warrior fixed it on the first try. Best $100 I ever spent. I’ve now copied all my data off onto another set of disks, just to be sure, but at this point everything seems fine.

    Posted by Glenn on 21 Nov 2008 at 3:32 am | Permalink
  93. Nicole

    Hi, the info posted by introspectif in comment #38 about how to repair the external drives was a life saver. Thanks so much!

    Posted by Nicole on 23 Nov 2008 at 9:17 pm | Permalink
  94. After my new Apple Time Capsule crashed, see: http://discussions.apple.com/thread.jspa?threadID=1550759&tstart=0
    AND
    http://discussions.apple.com/thread.jspa?threadID=1799465&tstart=0

    and after 45 min. in the Apple store ending with a “gift” of two disaster recovery store business cards, I decided to try my own disaster recovery. After opening the hood of the Time Capsule (Thank U, YOUTube) I connected the 1TB-TC hard-drive to a SATA/USB (http://www.sataadapter.com/SATA-IDE-ATA-66-ATA-100-ATA-133-COMBO-ADAPTER/sata-ide-adapter-usb-hard-drive-sata-drive.html)

    After opening the Apple Disk Utility I was able to view the drive but received “Invalid node structure” so nothing could be viewed, verified, or backed up.
    So, after opening a terminal window and trying a few of these commands; finally the
    “fsck_hfs -r /dev/disk2s3″ (where disk2s3 was the Time Capsule over USB) WORKED!!
    and after repairing the volume; including incorrect number of thread records, invalid directory item count, incorrect number of access control lists, invalid volume free block count, etc. I received “The volume on ___ Time Capsule was repaired successfully. In other words your command allowed me to recover 350+ GIG of what I thought was irretrievable data. YOU ROCK!! Yo’ da’ bomb!! Thank You Thank you.
    After backing all of my data up to a GForce 1TB/USB-SATA, I’m dancing cartwheels over to the Apple Store and returning this brick for a new Time Capsule – at least the 802.11n will be good!! Thanks Again!

    Posted by Barry Haines on 25 Nov 2008 at 3:45 am | Permalink
  95. Amy

    I want to thank you SO MUCH for this tip. I thought everything on my computer was lost… I took my macbook to the genius bar after receiving the error that the disk could not be repaired. My computer wouldn’t even start up (except by a CD) and the drive wasn’t spinning. The drive wouldn’t mount on other computers from firewire mode and I had no access to my data. Well, when I got to the apple store they informed me that the disk could not be saved and that all my information was lost. They offered to replace the hard drive for free (even though my warranty is out) but said no data recovery could be done… well I decided I would shop around for a data recovery service before allowing them to replace the drive. I looked up the errors myself on google, found this post and tried the fix. I have never used terminal or any sort of coding of any kind but I gave it a shot. After running the fix I was still receiving all sorts of errors and getting messages that the drive could not be repaired but it did appear to be doing SOMETHING… so I ran the code thing twice and then typed reboot and I couldn’t believe my eyes when my computer booted back as normal… after 4 days of nothing. AMAZING!! I feel smarter than an Apple “Genius” for sure. THANK YOU SO MUCH!!! Now I can finally back up my files and have apple replace this messed up drive for good. I AM SO HAPPY.

    Posted by Amy on 8 Dec 2008 at 12:56 pm | Permalink
  96. Melina

    WOW. Thank you!!! I was able to fix a macbook air with this.

    Posted by Melina on 10 Dec 2008 at 1:25 am | Permalink
  97. Toks Salako

    Worked like a charm after sudden failure. Thanks a lot. However, now my MB takes at least ten mins to boot! Any ideas?

    Posted by Toks Salako on 12 Dec 2008 at 7:38 am | Permalink
  98. carter

    This works for FreeAgent drives on Macs running Leopard (OS 10.5). It deeply hidden at seagate.com:

    Ensure that any/all installers (DMG) files are dismounted before trying to prepare an external drive. Simply drag these files to the Trash to proceed.

    • Open Finder > Applications > Utilities > Disk Utility
    • Click on the Partition tab
    • Click on the Current Volume Scheme drop-down menu and select One (1) partition.
    • Click Options. From the Partition Schemes provided:
    • Click on the GUID Partition Table radio button
    -OR-
    Click on the Apple Partition Map radio button
    • Click OK. Select other options as desired (e.g., Volume Name, Format, etc.).
    • Click Apply. The Partition Disk screen opens.
    • Click Partition. At this point, the volume dismounts from the desktop and the drive is partitioned and formatted.

    Posted by carter on 26 Dec 2008 at 9:13 am | Permalink
  99. Philip Wharam

    Thank you so much for this. You are a star! Will def come back to you the next time I manage to f*** things up…

    Posted by Philip Wharam on 31 Dec 2008 at 10:30 pm | Permalink
  100. Liam

    G’day,
    I encountered the same problem, found the same solution, and tried the macosxhints site before this one, then used this to solve my problem…
    Eventually after a few attempts it worked, but out of curiosity, is everything from my user supposed to be wiped?
    or filed through to lost + found folders?
    This has become a big worry to me as its got all my work, school, music, video, and gaming files scattered or disappeared completely..

    Thanks for the help in actually getting my mac back online though :)

    Posted by Liam on 2 Jan 2009 at 1:33 pm | Permalink
  101. Liam

    Also, Happy new years!! :D

    Posted by Liam on 2 Jan 2009 at 1:34 pm | Permalink
  102. Karl

    Hi! My name’s Karl, I just wanted to fill you in a little bit on the why’s, since you seem very interested.

    In single user mode, the system thinks you’re logged in as root (why the common rm /db/.AppleSetupDone thing works, but not when logged in).

    Part of the restrictions to try and make sure this isn’t abused is that Diskutil, the commandline utility that Disk Utility is the frontend for, is not loaded.

    Yes, Diskutil isn’t even loaded in single user mode.

    FSCK_HFS is, in fact, a completely unrelated utility. It can, however, operate at a level that permits higher success rate due to the DiskUtil and fsck_hfs not being in conflict.

    So, if that was confusing, let me rephrase:

    1. Disk Utility and fsck_hfs are separate utilities.
    2. They conflict.
    3. When running Finder, the Diskutil frameworks are loaded, and take precendence.

    This explains why people have been having success on external drives; the live drive Mac Os X is booted off of is the drive that Diskutil lives on, thus Diskutil will take precedence.

    The commands listed should (take that should with a HUMONGOUS grain of salt) work under Finder by prepending “sudo -s” to them.

    EX:

    sudo -s fsck_hfs -r /dev/disk0s2

    Also, BSD, what Mac OS X is based off of, numbers from 0 (first element in an array) up. So Disk 0 is, in fact, the first disk.

    Also, NEVER repair disk0s0. This is the efi partitioning partition (I know, it’s confusing; Google EFI for a better understanding). If this partition becomes corrupted, you need to reformat or place in target disk mode and salvage your data.

    Those of you freaking out about losing data when receiving the errors should know Leopard can mount disks with this sort of error for backup. And for someone like Mike above who’s computer shuts down suddenly, you can place the computer in what’s known as “target disk mode” and still get to the files. If you have a Macbook without firewire (the late 2008 aluminum models) you can purchase a cheap external hard drive and plug it in, install Mac OS X from the DVD, boot off the drive and have access.

    I have 2 macs, so I just pulled the hard drive from my Macbook and attached it (in an external enclosure) to my iMac.

    Karl

    Posted by Karl on 11 Jan 2009 at 8:55 am | Permalink
  103. Nizam

    Thank you, topic help me!

    Posted by Nizam on 16 Jan 2009 at 6:18 pm | Permalink
  104. Frank

    I tried it for my “Invalid sibling link” on my external OWC Mercury Elite Pro but fsck_hfs said right away that it could not rebuild the catalog.

    I suspect there isn’t enough space for a new catalog…I will try removing some files…I do still have access to the files.

    Posted by Frank on 17 Jan 2009 at 2:37 am | Permalink
  105. guy goodwin

    Many thanks – perfect fix, so you saved me a lot of time (and money) and it is much appreciated.

    Posted by guy goodwin on 25 Jan 2009 at 7:47 pm | Permalink
  106. I can not express enough gratitude to this helpful site.

    You saved my life… and my job.

    I was told by apple that I needed to do a swap out of hard drives and they wouldn’t give me my old one. I thought my 7 years of professional photography were gone because just yesterday my backup drive crashed.

    Thank You, Thank You, Thank YOU!

    Posted by Steve on 28 Jan 2009 at 10:55 am | Permalink
  107. Due to the enormous ignorance of my older brother, who purposely shut off my iMac, my internal HD was damaged. Although I had to run the fsck_hfs step 2 times, it was able to repair my disc successfully.

    A big thank you from the Netherlands!

    Posted by Ton Somers on 30 Jan 2009 at 9:47 pm | Permalink
  108. Steve

    Thank you, worked fine on an external usb

    Posted by Steve on 17 Feb 2009 at 12:03 pm | Permalink
  109. Albert Mapache

    MIL GRACIAS…!! (THANK YOU)
    It worked perfect for me, at the first try. Saved my life…

    How can I donate?

    ALBERTO. Mexico City.

    Posted by Albert Mapache on 18 Feb 2009 at 12:13 pm | Permalink
  110. Albert Mapache

    OOPS! I found the DONATE button… And I made a donation.

    MUCHAS GRACIAS, AGAIN!

    ALBERTO. Mexico City.

    Posted by Albert Mapache on 18 Feb 2009 at 12:34 pm | Permalink
  111. TARA

    Thank God! This worked when nothing else would! I couldn’t even get into safe mode! Thank you!!

    Posted by TARA on 20 Feb 2009 at 9:37 am | Permalink
  112. Chris

    Worked like a charm for my external drive. Thanks! (You might want to include info about external/secondary drives and what to type in Terminal, ie “fsck_hfs -r /dev/disk1s1″ etc.

    Posted by Chris on 4 Mar 2009 at 4:43 am | Permalink
  113. Whitty

    Thanks for this. I have managed to get my boss’s mac mini working again. I owe you some brownie points!

    Posted by Whitty on 12 Mar 2009 at 9:19 pm | Permalink
  114. flowers

    thank you, you are a genius my macbook was flat dead for 3 weeks until i came across this web page. at first attempt to boot

    1st boot= failed

    second time, while making a cup of coffee and playing the xbox,it worked.

    coffee + xbox = worked

    Posted by flowers on 25 Mar 2009 at 8:37 am | Permalink
  115. George Noshy

    God bless you for this tips really it works like a smashing miracle but there is some things i need to ask about:

    *The screen of the single user mode after writing the commands and waiting while checking it told me that HD250 which is the one i want to repair can not be repaired after 3 attempts but after rebooting the OS opens normally but after a long time as mentioned above by richard so instead of taking 10 sec. to boot it takes about 40 sec. So please inform me why it takes long time.

    Posted by George Noshy on 6 Apr 2009 at 3:29 am | Permalink
  116. lbh

    this fix just saved my dissertation. you’re my hero of the day.

    Posted by lbh on 9 Apr 2009 at 3:40 am | Permalink
  117. bigfei

    It just worked like a charm. My 500G external disk is back now..
    Thanks..

    Posted by bigfei on 25 Apr 2009 at 5:06 pm | Permalink
  118. DaveMc

    Worked like a charm for me! Thanks so much, this saved me from a bizarre error.

    Posted by DaveMc on 7 May 2009 at 10:46 pm | Permalink
  119. DavidALLEN

    Many thanks to introspectiv : I have a LaCie terabite monster and that was V full and probably due to incorrect unmounting (don’t accidentally unplug your drive guys!!)…I have persevered with your Terminal black screen stuff and first (unwitingly really) repaired the actual computer volume (another fully working OK desktop computer)…and then the Lacie and it came up with that nice message – about sucessfully repairing the LaCie! oooh was that good or what! I’m now feeling like a computer programmer….(not). It didn’t work first time, but the second time, after the actual computer was ‘repaired’, then the LaCie disk name was recognised and it worked. But hey, this is brilliant and touch wood, all seems OK. Just need to get the laptop working…

    Posted by DavidALLEN on 11 May 2009 at 3:50 am | Permalink
  120. Guru

    I tried to update leopard to 10.5.7 but it failed saying the update files were corrupt and asked me to reboot. I rebooted and now I am stuck because I am getting an invalid sibling error!

    The fsck_hfs command does not help. It quits saying “The volume HDD could not be repaired”.

    Any tips? Can I atleast copy the data off of my disk to an external drive?

    Posted by Guru on 15 May 2009 at 2:35 am | Permalink
  121. Sean M

    Mahal kita!!

    You saved my life providing this information!

    I dj off my macbook and im booked to work tomorrow night – NOW I CAN!

    Posted by Sean M on 15 May 2009 at 6:08 am | Permalink
  122. dima

    didn’t work here:

    the volume could not be repaired

    Posted by dima on 16 May 2009 at 4:19 am | Permalink
  123. Elizabeth

    Thank you, Thank you, Thank you! It took quite a while to get through everything (30 mins or more) but worked… After hours of trying everything to get my poor macbook back up and running this finally did the trick. Mahalo ;-)

    Posted by Elizabeth on 21 May 2009 at 1:37 pm | Permalink
  124. Neil

    How will you do it on external drive?

    Is invalid sibling link same as invalid index link? Sorry, newbie here :) Using Leopard 10.5.7

    Posted by Neil on 24 May 2009 at 7:48 pm | Permalink
  125. Neil

    Comment #38 didn’t work for me, tried it few times. On one of the comments you said back up the files. How can I back up if it’s not mounting in the Finder.

    OT: Are you a Filipino?

    Posted by Neil on 25 May 2009 at 3:38 am | Permalink
  126. kap

    hi
    i tried the fsck_hfs on my external drive. it immediately brings up the terminal prompt with no message
    fsck -fy then gives me the following message:
    BAD SUPER BLOCK: MAGIC NUMBER WRONG
    how do i fix it? and how can i recover the data?!

    Posted by kap on 3 Jun 2009 at 8:20 am | Permalink
  127. Ben

    This method worked for my external Lacie USB hard drive (mac os x 10.4.11).

    By the way, the consultant at Drive Savers gave me a quote of $2700 to retrieve my “lost” data. Very friendly guy, but I’m very pleased that someone took the time to post this article. Thank you very much.

    I followed the instructions (a bit too literally at first), with no result, but nailed it the second time around when I noticed comments 37 – 41.

    Here’s what I did exactly:
    - Shut down imac
    - Power down lacie
    - Flip lacie power switch “on”
    - Turn on mac (in normal mode)
    - (lacie icon still didn’t mount/was not visible on desktop)
    - open disk utility
    - get the disk identifier for lacie (disk1s6 for me)
    - ejected the lacie drive
    - open a terminal window
    - type this: fsck_hfs -r /dev/disk1s6
    - observed this at the terminal window…

    ** /dev/rdisk1s6
    ** Checking HFS Plus volume.
    ** Checking Extents Overflow file.
    ** Checking Catalog file.
    ** Rebuilding Catalog B-tree.
    ** Rechecking volume.
    ** Checking HFS Plus volume.
    ** Checking Extents Overflow file.
    ** Checking Catalog file.
    Incorrect number of thread records
    (4, 195)
    ** Checking Catalog hierarchy.
    ** Checking Extended Attributes file.
    ** Checking volume bitmap.
    ** Checking volume information.
    Invalid volume file count
    (It should be 210285 instead of 200053)
    Invalid volume directory count
    (It should be 58041 instead of 57787)
    Invalid volume free block count
    (It should be 89818897 instead of 116252881)
    Volume Header needs minor repair
    (2, 0)
    ** Repairing volume.
    ** Rechecking volume.
    ** Checking HFS Plus volume.
    ** Checking Extents Overflow file.
    ** Checking Catalog file.
    ** Checking Catalog hierarchy.
    ** Checking Extended Attributes file.
    ** Checking volume bitmap.
    ** Checking volume information.
    ** The volume LaCie was repaired successfully.

    - opened disk utility to confirm lacie still not mounted
    - power down lacie
    - flip lacie power switch “on”
    - watch the icon appear on desktop
    - open iphoto and itunes (like regular)

    Posted by Ben on 9 Jun 2009 at 11:56 am | Permalink
  128. NASHUN

    I was letting my macbook just sit for about 6 months, not knowing what to do and dreading a repair bill, wish i found your site sooner, at first it told me that my hd could not be repaired but i just continued with the recheck again and it was repaired..

    Posted by NASHUN on 16 Jun 2009 at 4:08 pm | Permalink
  129. Scared Sh*tless

    I was attempting to do this at a computer at my work and now after doing the reboot part of the process the computer seems to work really hard when booting but nothing ever happens. It has stopped responding. I did Command+s to get back to the command prompt but nothing. Does this make sense? Have I done something terrible?

    Mac OSX 10.4.11
    Dual 1.8 GHz PowerPC G5 Processor
    3 GB DDR SDRAM Memory

    Posted by Scared Sh*tless on 1 Jul 2009 at 4:25 am | Permalink
  130. I never post comments, but i felt the need to since this actually did solve my problem. I tried to upgrade to 10.5.7. when i first started having problems. I couldn’t boot up after the install. I kept getting a kernel panic message right at start up. I was able to boot with the install disc that came with my MBP but i eventually did something wrong that turned off the permissions on my hard drive (i couldn’t write to it). I found this website, ran the code twice (wasn’t able to repair the first time) in single user mode, worked just like it said it would. I then booted from the installation disc, and ran repair disk and it went fine. Only trouble I had after that was when I tried to reinstall the OS, i had to do an Archive and Install, the upgrade option didn’t work.

    THANKS!!!!

    Posted by Lonnie Ro on 1 Jul 2009 at 1:42 pm | Permalink

One Trackback

  1. [...] How to fix the Invalid Sibling Link error: Congratulations to those for whom the methods I described worked. Please pass on the information to those who might value it. I will continue to try to help those who are still facing problems on a case-by-case basis. [...]

Post a Comment

Your email is never published nor shared. Required fields are marked *

*
*