Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'A possible fix for invalid sibling links on a hard drive' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
A possible fix for invalid sibling links on a hard drive
Authored by: tritium147 on Feb 24, '09 04:02:52PM

I recently ran into this problem and have tried this hint along with everything in the comments and nothing seems to work.

I've tried running disk utility while booting off the disk as well as fsck -fy in single user mode. Both tries comes back with invalid sibling link while its "checking catalog file."

while in the terminal while booting in the disk if I run fsck_hfs -r /dev/disk0s2 like was mention in this hint and the following gets reported:

/dev/rdisk0s2
Checking Journaled HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Rebuilding catalog B-tree.
The volume HDD could not be repaired.

the same error occurs if I try the same thing in single user mode as well. It seems that any method i try to repair the problem or figure out whats going wrong it can't get past the Rebuilding catalog B-tree step and stops saying the drive can't be repaired.

Any help on what else to try or explaining what is going on (if I should give up and reformat or get a new drive competely) would be appreciated.



[ Reply to This | # ]
A possible fix for invalid sibling links on a hard drive
Authored by: Bobe52ME on Mar 16, '09 07:28:07AM

Unfortunately the reported fix hasn't worked for me and I am just restoring my hard drive from Time Machine for the second time in about 4 months.

I can connect to the drive using the Target mode and another computer, but every time I try to start the MacBook Pro 15" with the problem, it makes it through about a half boot up and then shuts down.

The only advice I have, until I find something else that works, is to use Time Machine hourly and then you can restore everything the way it was just before the Sibling Link problem.

I would be interested to know if anyone has experienced this problem after installing a new, larger HD in their MacBook Pro. I replaced my 120Gig drive with a 320Gig drive about a year ago but didn't start with this problem until about 5 months ago. I run a fairly full HD, too.



[ Reply to This | # ]