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: PoinT on Jun 10, '08 06:41:44PM

my maxtor one touch got fried when PC i had it hooked blue screened ...when i hooked it back to the mac no go... wouldnt let me write to it .. maxtor tools wanted to reformat it.... disk utility said invalid sib links... and thats how i found this thread....

anyway after reading all this heres what i tried......>>>>>>>>>>>>>>>

used disk utility > info to get drive id disk1 and disk1s3
opened terminal... (had to find it first never used it before)
Try one...

Last login: Tue Jun 10 17:10:53 on console
Macintosh-2:~ MyMacUserName$ fsck_hfs -r /dev/disk1s3
** /dev/rdisk1s3
** Checking Non-journaled HFS Plus volume.
** Checking Extents Overflow file.
** Checking Catalog file.
** Rebuilding Catalog B-tree.
** Rechecking volume.
** Checking Non-journaled HFS Plus volume.
** Checking Extents Overflow file.
** Checking Catalog file.
Incorrect number of thread records
(4, 31565)
Incorrect number of thread records
(4, 31565)
** Checking multi-linked files.
** Checking Catalog hierarchy.
Missing thread record (id = 760145)
Missing thread record (id = 760146)
Invalid directory item count
(It should be 237 instead of 234)
Invalid directory item count
(It should be 19 instead of 18)
Invalid volume file count
(It should be 606823 instead of 606824)
** Checking Extended Attributes file.
** Checking volume bitmap.
Volume Bit Map needs minor repair
** Checking volume information.
Invalid volume free block count
(It should be 78732544 instead of 78770764)
Volume Header needs minor repair
(2, 0)
** Repairing volume.
** Rechecking volume.
** Checking Non-journaled HFS Plus volume.
** Checking Extents Overflow file.
** Checking Catalog file.
Missing thread record (id = 760040)
Incorrect number of thread records
(4, 31565)
** Checking multi-linked files.
** Checking Catalog hierarchy.
Invalid volume file count
(It should be 606823 instead of 606824)
** Checking Extended Attributes file.
** Checking volume bitmap.
** Checking volume information.
** Repairing volume.
Missing directory record (id = 760040)
** Look for missing items in lost+found directory.
** Rechecking volume.
** Checking Non-journaled HFS Plus volume.
** Checking Extents Overflow file.
** Checking Catalog file.
** Checking multi-linked files.
** Checking Catalog hierarchy.
** Checking Extended Attributes file.
** Checking volume bitmap.
** Checking volume information.
Invalid volume file count
(It should be 606824 instead of 606823)
** The volume OneTouch 4 could not be repaired after 3 attempts.
Macintosh-2:~ MyMacUserName$

>>>>>>>>>>>>> after try one things degraded it wouldn't mount now.... before it least it mounted just couldnt write to it or alter anything... so tried again...


Last login: Tue Jun 10 18:05:08 on ttys000
Macintosh-2:~ mymacusername$ fsck_hfs -r /dev/disk1s3
** /dev/rdisk1s3
** Checking Non-journaled HFS Plus volume.
** Checking Extents Overflow file.
** Checking Catalog file.
** Rebuilding Catalog B-tree.
** Rechecking volume.
** Checking Non-journaled HFS Plus volume.
** Checking Extents Overflow file.
** Checking Catalog file.
** Checking multi-linked files.
** Checking Catalog hierarchy.
** Checking Extended Attributes file.
** Checking volume bitmap.
Volume Bit Map needs minor repair
** Checking volume information.
Volume Header needs minor repair
(2, 0)
** Repairing volume.
** Rechecking volume.
** Checking Non-journaled HFS Plus volume.
** Checking Extents Overflow file.
** Checking Catalog file.
** Checking multi-linked files.
** Checking Catalog hierarchy.
** Checking Extended Attributes file.
** Checking volume bitmap.
** Checking volume information.
** The volume OneTouch 4 was repaired successfully.
Macintosh-2:~ mymacusername$


>>>>> Now it seems to work good as new.... moral of the story don't hook the hd to a buggy pc...

:)
thanks for the tips...



[ Reply to This | # ]