<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: How to fix the Invalid Sibling Link error</title>
	<atom:link href="http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/feed/" rel="self" type="application/rss+xml" />
	<link>http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/</link>
	<description>means "I love you"</description>
	<lastBuildDate>Thu, 17 Dec 2009 16:20:54 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Brian</title>
		<link>http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/comment-page-3/#comment-7933</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Thu, 17 Dec 2009 16:20:54 +0000</pubDate>
		<guid isPermaLink="false">http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/#comment-7933</guid>
		<description>I just found this page using Google. I&#039;m working on a friend&#039;s Powerbook that wouldn&#039;t boot. It had an invalid volume header and invalid sibling link. I was ready to give up repairing it since I tried everything I could find and nothing would fix it. Then I found this page and tried this fix and the Mac is back up. My friend&#039;s kids thank you.</description>
		<content:encoded><![CDATA[<p>I just found this page using Google. I&#8217;m working on a friend&#8217;s Powerbook that wouldn&#8217;t boot. It had an invalid volume header and invalid sibling link. I was ready to give up repairing it since I tried everything I could find and nothing would fix it. Then I found this page and tried this fix and the Mac is back up. My friend&#8217;s kids thank you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mika</title>
		<link>http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/comment-page-3/#comment-7932</link>
		<dc:creator>mika</dc:creator>
		<pubDate>Thu, 03 Dec 2009 20:08:42 +0000</pubDate>
		<guid isPermaLink="false">http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/#comment-7932</guid>
		<description>awesome!
it worked with my mb. thx a lot</description>
		<content:encoded><![CDATA[<p>awesome!<br />
it worked with my mb. thx a lot</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Abhinay Omkar</title>
		<link>http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/comment-page-3/#comment-7931</link>
		<dc:creator>Abhinay Omkar</dc:creator>
		<pubDate>Sun, 29 Nov 2009 07:42:56 +0000</pubDate>
		<guid isPermaLink="false">http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/#comment-7931</guid>
		<description>This didn&#039;t work for me...

I tried doing fsck in single user mode of Mac and also tried in Ubuntu with hfsprog utility, I got the same error - it says &#039;Macintosh HD&#039; couldn&#039;t be repaired. My Mac is not booting too.

(in Ubuntu)
abhinay@abhiomkar:~$ sudo fsck.hfsplus -r  /dev/sda2
** /dev/sda2
** Checking HFS Plus volume.
** Checking Extents Overflow file.
** Checking Catalog file.
** Rebuilding Catalog B-tree.
** The volume Macintosh HD could not be repaired.

abhinay@abhiomkar:~$ sudo fsck.hfsplus /dev/sda2
** /dev/sda2
** Checking HFS Plus volume.
** Checking Extents Overflow file.
** Checking Catalog file.
   Incorrect block count for file configd.pid
   (It should be 1 instead of 0)
   Incorrect block count for file DirectoryService.pid
   (It should be 1 instead of 0)
   Incorrect block count for file syslog.pid
   (It should be 1 instead of 0)
   Incorrect block count for file utmpx
   (It should be 1 instead of 0)
   Invalid sibling link
(4, 53631)
** Volume check failed.

I believe that, this is because, the Mac partition is not unmounted properly in Ubuntu Linux, my suggestion is - do not mount Mac partition with Write permissions as the hfsplus write is still an experimental.

PS:
I&#039;m still in the process of finding a solution to fix my partition...</description>
		<content:encoded><![CDATA[<p>This didn&#8217;t work for me&#8230;</p>
<p>I tried doing fsck in single user mode of Mac and also tried in Ubuntu with hfsprog utility, I got the same error &#8211; it says &#8216;Macintosh HD&#8217; couldn&#8217;t be repaired. My Mac is not booting too.</p>
<p>(in Ubuntu)<br />
abhinay@abhiomkar:~$ sudo fsck.hfsplus -r  /dev/sda2<br />
** /dev/sda2<br />
** Checking HFS Plus volume.<br />
** Checking Extents Overflow file.<br />
** Checking Catalog file.<br />
** Rebuilding Catalog B-tree.<br />
** The volume Macintosh HD could not be repaired.</p>
<p>abhinay@abhiomkar:~$ sudo fsck.hfsplus /dev/sda2<br />
** /dev/sda2<br />
** Checking HFS Plus volume.<br />
** Checking Extents Overflow file.<br />
** Checking Catalog file.<br />
   Incorrect block count for file configd.pid<br />
   (It should be 1 instead of 0)<br />
   Incorrect block count for file DirectoryService.pid<br />
   (It should be 1 instead of 0)<br />
   Incorrect block count for file syslog.pid<br />
   (It should be 1 instead of 0)<br />
   Incorrect block count for file utmpx<br />
   (It should be 1 instead of 0)<br />
   Invalid sibling link<br />
(4, 53631)<br />
** Volume check failed.</p>
<p>I believe that, this is because, the Mac partition is not unmounted properly in Ubuntu Linux, my suggestion is &#8211; do not mount Mac partition with Write permissions as the hfsplus write is still an experimental.</p>
<p>PS:<br />
I&#8217;m still in the process of finding a solution to fix my partition&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lisa</title>
		<link>http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/comment-page-3/#comment-7930</link>
		<dc:creator>Lisa</dc:creator>
		<pubDate>Thu, 26 Nov 2009 11:54:22 +0000</pubDate>
		<guid isPermaLink="false">http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/#comment-7930</guid>
		<description>OMG - If I could, I would kiss you!!

Thankyou so much. I had tried everything, to no avail, but this worked a treat for me.

Furiously doing major backup now though, just in case . . 

Thankyou!

Lisa</description>
		<content:encoded><![CDATA[<p>OMG &#8211; If I could, I would kiss you!!</p>
<p>Thankyou so much. I had tried everything, to no avail, but this worked a treat for me.</p>
<p>Furiously doing major backup now though, just in case . . </p>
<p>Thankyou!</p>
<p>Lisa</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc</title>
		<link>http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/comment-page-3/#comment-7929</link>
		<dc:creator>Marc</dc:creator>
		<pubDate>Sat, 21 Nov 2009 15:47:16 +0000</pubDate>
		<guid isPermaLink="false">http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/#comment-7929</guid>
		<description>Works GREAT !!! Thanks a lot, my PowerBook Pro die, and like Amy posted on 12.08.08 at 12:56 pm: &quot;...I thought everything on my computer was lost… &quot;
Once again THANK YOU !!! :)</description>
		<content:encoded><![CDATA[<p>Works GREAT !!! Thanks a lot, my PowerBook Pro die, and like Amy posted on 12.08.08 at 12:56 pm: &#8220;&#8230;I thought everything on my computer was lost… &#8221;<br />
Once again THANK YOU !!! :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Another Frank</title>
		<link>http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/comment-page-3/#comment-7927</link>
		<dc:creator>Another Frank</dc:creator>
		<pubDate>Fri, 06 Nov 2009 20:08:06 +0000</pubDate>
		<guid isPermaLink="false">http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/#comment-7927</guid>
		<description>Didn&#039;t work for me....

Still getting &quot;The volume Macintosh HD could not be repaired&quot; when I attempt fsck_hfs -r /dev/disk0s5

When I do the fsck -fy I&#039;m back to getting &quot;Invalid sibling link... Volume check failed&quot;

I think my next step may be DiskWarrior.</description>
		<content:encoded><![CDATA[<p>Didn&#8217;t work for me&#8230;.</p>
<p>Still getting &#8220;The volume Macintosh HD could not be repaired&#8221; when I attempt fsck_hfs -r /dev/disk0s5</p>
<p>When I do the fsck -fy I&#8217;m back to getting &#8220;Invalid sibling link&#8230; Volume check failed&#8221;</p>
<p>I think my next step may be DiskWarrior.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frank</title>
		<link>http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/comment-page-3/#comment-7920</link>
		<dc:creator>Frank</dc:creator>
		<pubDate>Sun, 25 Oct 2009 07:59:22 +0000</pubDate>
		<guid isPermaLink="false">http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/#comment-7920</guid>
		<description>Hi,

I have tried fsck_hfs -r /dev/disk0s2, and got the message,

the volum disk0s2 could not be repaired.

I also try to backup image and got message, input/output error.

Please help.

Thanks.

Frank</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I have tried fsck_hfs -r /dev/disk0s2, and got the message,</p>
<p>the volum disk0s2 could not be repaired.</p>
<p>I also try to backup image and got message, input/output error.</p>
<p>Please help.</p>
<p>Thanks.</p>
<p>Frank</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian</title>
		<link>http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/comment-page-3/#comment-7917</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Thu, 15 Oct 2009 22:48:59 +0000</pubDate>
		<guid isPermaLink="false">http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/#comment-7917</guid>
		<description>Finally worked after repeating the command 5 times. It seems that it slowly corrected things after each attempt and finally took on the last.

Dont give up if it doesn&#039;t work the first time.

The error I was getting was the same as the original disk utility error 
&quot;invalid sibling link&quot;</description>
		<content:encoded><![CDATA[<p>Finally worked after repeating the command 5 times. It seems that it slowly corrected things after each attempt and finally took on the last.</p>
<p>Dont give up if it doesn&#8217;t work the first time.</p>
<p>The error I was getting was the same as the original disk utility error<br />
&#8220;invalid sibling link&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott</title>
		<link>http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/comment-page-3/#comment-7915</link>
		<dc:creator>Scott</dc:creator>
		<pubDate>Tue, 13 Oct 2009 20:06:56 +0000</pubDate>
		<guid isPermaLink="false">http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/#comment-7915</guid>
		<description>After approx 3 minutes, the process returned the Failed After 3 Attempts; then ran standard fsck and repair went through. Rebooted. Live again. First order of business. Backup!

Thank you. If only all tech support were so happy.</description>
		<content:encoded><![CDATA[<p>After approx 3 minutes, the process returned the Failed After 3 Attempts; then ran standard fsck and repair went through. Rebooted. Live again. First order of business. Backup!</p>
<p>Thank you. If only all tech support were so happy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CP</title>
		<link>http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/comment-page-3/#comment-7904</link>
		<dc:creator>CP</dc:creator>
		<pubDate>Sat, 03 Oct 2009 07:27:48 +0000</pubDate>
		<guid isPermaLink="false">http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/#comment-7904</guid>
		<description>Worked fine, thank you!</description>
		<content:encoded><![CDATA[<p>Worked fine, thank you!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Leigh</title>
		<link>http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/comment-page-3/#comment-7876</link>
		<dc:creator>Leigh</dc:creator>
		<pubDate>Sun, 06 Sep 2009 10:50:40 +0000</pubDate>
		<guid isPermaLink="false">http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/#comment-7876</guid>
		<description>Hi there - a million thank you&#039;s for this lovely webpage which fixed my system and saved me from non-backup-near-heart-attack.

Best Wishes, and many thanks,

Leigh</description>
		<content:encoded><![CDATA[<p>Hi there &#8211; a million thank you&#8217;s for this lovely webpage which fixed my system and saved me from non-backup-near-heart-attack.</p>
<p>Best Wishes, and many thanks,</p>
<p>Leigh</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Laurie</title>
		<link>http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/comment-page-3/#comment-7875</link>
		<dc:creator>Laurie</dc:creator>
		<pubDate>Wed, 02 Sep 2009 21:16:46 +0000</pubDate>
		<guid isPermaLink="false">http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/#comment-7875</guid>
		<description>My external Maxtor hard drive was not able to read some  folders and Disk Utility reported a &quot;invalid sibling link&quot;. I read through all the troubleshooting options. I tried the fsck thing  a few times and it said the drive could not be repaired.

I downloaded a demo version of Data Rescue II software from https://prosoft1.securesites.net/ and it was able to see all my drive&#039;s folders. I bought the software and have recovered all my files! I just copied them onto another drive. It looks like I&#039;ll need to reformat the bad drive but the important thing is I saved my data. It was worth the $99.</description>
		<content:encoded><![CDATA[<p>My external Maxtor hard drive was not able to read some  folders and Disk Utility reported a &#8220;invalid sibling link&#8221;. I read through all the troubleshooting options. I tried the fsck thing  a few times and it said the drive could not be repaired.</p>
<p>I downloaded a demo version of Data Rescue II software from <a href="https://prosoft1.securesites.net/" rel="nofollow">https://prosoft1.securesites.net/</a> and it was able to see all my drive&#8217;s folders. I bought the software and have recovered all my files! I just copied them onto another drive. It looks like I&#8217;ll need to reformat the bad drive but the important thing is I saved my data. It was worth the $99.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Professor Minotaur</title>
		<link>http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/comment-page-3/#comment-7874</link>
		<dc:creator>Professor Minotaur</dc:creator>
		<pubDate>Sat, 29 Aug 2009 23:35:28 +0000</pubDate>
		<guid isPermaLink="false">http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/#comment-7874</guid>
		<description>As per external hard disks...
Try Disk Warrior

I tried all of the advice above and after trying Drive Genius (which also failed) I moved on to Disk Warrior. WOW! The disk was physically damaged and Disk Warrior created a temporary mount that allowed me to drag ALL of my files over to another drive. Unbelievable how effective this tool was.</description>
		<content:encoded><![CDATA[<p>As per external hard disks&#8230;<br />
Try Disk Warrior</p>
<p>I tried all of the advice above and after trying Drive Genius (which also failed) I moved on to Disk Warrior. WOW! The disk was physically damaged and Disk Warrior created a temporary mount that allowed me to drag ALL of my files over to another drive. Unbelievable how effective this tool was.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JF</title>
		<link>http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/comment-page-3/#comment-7856</link>
		<dc:creator>JF</dc:creator>
		<pubDate>Mon, 17 Aug 2009 15:30:03 +0000</pubDate>
		<guid isPermaLink="false">http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/#comment-7856</guid>
		<description>Worked for me. Thanks!</description>
		<content:encoded><![CDATA[<p>Worked for me. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin</title>
		<link>http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/comment-page-3/#comment-7767</link>
		<dc:creator>Martin</dc:creator>
		<pubDate>Tue, 14 Jul 2009 16:36:41 +0000</pubDate>
		<guid isPermaLink="false">http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/#comment-7767</guid>
		<description>Thank you, I was already scared my hard drive is broken. What a shame that even the Disk Utility after booting from DVD didn&#039;t do the job. Hurray to BSD.</description>
		<content:encoded><![CDATA[<p>Thank you, I was already scared my hard drive is broken. What a shame that even the Disk Utility after booting from DVD didn&#8217;t do the job. Hurray to BSD.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lonnie Ro</title>
		<link>http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/comment-page-3/#comment-7688</link>
		<dc:creator>Lonnie Ro</dc:creator>
		<pubDate>Wed, 01 Jul 2009 05:42:00 +0000</pubDate>
		<guid isPermaLink="false">http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/#comment-7688</guid>
		<description>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&#039;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&#039;t write to it). I found this website, ran the code twice (wasn&#039;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&#039;t work.

THANKS!!!!</description>
		<content:encoded><![CDATA[<p>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&#8217;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&#8217;t write to it). I found this website, ran the code twice (wasn&#8217;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&#8217;t work.</p>
<p>THANKS!!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scared Sh*tless</title>
		<link>http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/comment-page-3/#comment-7685</link>
		<dc:creator>Scared Sh*tless</dc:creator>
		<pubDate>Tue, 30 Jun 2009 20:25:48 +0000</pubDate>
		<guid isPermaLink="false">http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/#comment-7685</guid>
		<description>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</description>
		<content:encoded><![CDATA[<p>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?</p>
<p>Mac OSX 10.4.11<br />
Dual 1.8 GHz PowerPC G5 Processor<br />
3 GB DDR SDRAM Memory</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: NASHUN</title>
		<link>http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/comment-page-3/#comment-7616</link>
		<dc:creator>NASHUN</dc:creator>
		<pubDate>Tue, 16 Jun 2009 08:08:36 +0000</pubDate>
		<guid isPermaLink="false">http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/#comment-7616</guid>
		<description>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..</description>
		<content:encoded><![CDATA[<p>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..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben</title>
		<link>http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/comment-page-3/#comment-7577</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Tue, 09 Jun 2009 03:56:10 +0000</pubDate>
		<guid isPermaLink="false">http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/#comment-7577</guid>
		<description>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 &quot;lost&quot; data. Very friendly guy, but I&#039;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&#039;s what I did exactly:
- Shut down imac
- Power down lacie
- Flip lacie power switch &quot;on&quot;
- Turn on mac (in normal mode)
- (lacie icon still didn&#039;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 &quot;on&quot;
- watch the icon appear on desktop
- open iphoto and itunes (like regular)</description>
		<content:encoded><![CDATA[<p>This method worked for my external Lacie USB hard drive (mac os x 10.4.11). </p>
<p>By the way, the consultant at Drive Savers gave me a quote of $2700 to retrieve my &#8220;lost&#8221; data. Very friendly guy, but I&#8217;m very pleased that someone took the time to post this article. Thank you very much. </p>
<p>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 &#8211; 41. </p>
<p>Here&#8217;s what I did exactly:<br />
- Shut down imac<br />
- Power down lacie<br />
- Flip lacie power switch &#8220;on&#8221;<br />
- Turn on mac (in normal mode)<br />
- (lacie icon still didn&#8217;t mount/was not visible on desktop)<br />
- open disk utility<br />
- get the disk identifier for lacie (disk1s6 for me)<br />
- ejected the lacie drive<br />
- open a terminal window<br />
- type this: fsck_hfs -r /dev/disk1s6<br />
- observed this at the terminal window&#8230;</p>
<p>** /dev/rdisk1s6<br />
** Checking HFS Plus volume.<br />
** Checking Extents Overflow file.<br />
** Checking Catalog file.<br />
** Rebuilding Catalog B-tree.<br />
** Rechecking volume.<br />
** Checking HFS Plus volume.<br />
** Checking Extents Overflow file.<br />
** Checking Catalog file.<br />
   Incorrect number of thread records<br />
(4, 195)<br />
** Checking Catalog hierarchy.<br />
** Checking Extended Attributes file.<br />
** Checking volume bitmap.<br />
** Checking volume information.<br />
   Invalid volume file count<br />
   (It should be 210285 instead of 200053)<br />
   Invalid volume directory count<br />
   (It should be 58041 instead of 57787)<br />
   Invalid volume free block count<br />
   (It should be 89818897 instead of 116252881)<br />
   Volume Header needs minor repair<br />
(2, 0)<br />
** Repairing volume.<br />
** Rechecking volume.<br />
** Checking HFS Plus volume.<br />
** Checking Extents Overflow file.<br />
** Checking Catalog file.<br />
** Checking Catalog hierarchy.<br />
** Checking Extended Attributes file.<br />
** Checking volume bitmap.<br />
** Checking volume information.<br />
** The volume LaCie was repaired successfully.</p>
<p>- opened disk utility to confirm lacie still not mounted<br />
- power down lacie<br />
- flip lacie power switch &#8220;on&#8221;<br />
- watch the icon appear on desktop<br />
- open iphoto and itunes (like regular)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kap</title>
		<link>http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/comment-page-3/#comment-7542</link>
		<dc:creator>kap</dc:creator>
		<pubDate>Wed, 03 Jun 2009 00:20:10 +0000</pubDate>
		<guid isPermaLink="false">http://mahalkita.nanogeex.com/2007/09/28/how-to-fix-the-invalid-sibling-link-error/#comment-7542</guid>
		<description>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?!</description>
		<content:encoded><![CDATA[<p>hi<br />
i tried the fsck_hfs on my external drive. it immediately brings up the terminal prompt with no message<br />
fsck -fy then gives me the following message:<br />
BAD SUPER BLOCK: MAGIC NUMBER WRONG<br />
how do i fix it? and how can i recover the data?!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic page generated in 0.267 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2009-12-24 03:03:19 -->
<!-- Compression = gzip -->