[artlewis]

My apologies up front for throwing out this post. It's a plea for help and probably not worth reading further unless you're well versed in Mac surgery.

While attempting to set up a Belkin router with my cable provider (Comcast), I somehow managed to do major damage to the partition that had my e/m and docs, etc.
That partition won't mount and DiskWarrior 3 freezes on step 5(locating directory info...). When I re-boot from another 10.2.6 partition, a 9.2.2 partition, Disk Warrior CD (3 and 2.1), I can make no progress in repairing the damaged partition.
TechToolPro 3 offers to fix the damaged partition, but the data verification (the last step before approving repair) page shows wildly different values for catalog b-tree: a) 368,728 original leaf record count and TTP tells me there will be 7,695 after any repair; used nodes are 7,286 now and 125 after any repair; and free nodes of 1,162 now with 8,323 after any repair. Similarly volume information regarding total files has 599 original and projects 2,472 after any repair.
I hesitate to let TTP go to work.
Curiously, I can see the icon for the hosed partition and the files on it when I boot from the 9.2.2 partition, but when I attempt a manual copy to an external firewire drive, I get error messages if I'm trying to move applications, system, and what seems like the larger folders.
I have a week old backup made from CarbonCopyCloner but would like to save the hosed partition because I'm a relative newcomer to OS 10. I miss the drag & drop option for backup.
Thanks for any help you can offer.

[reader50]

Originally posted by artlewis:
...
While attempting to set up a Belkin router with my cable provider (Comcast), I somehow managed to do major damage to the partition that had my e/m and docs, etc.
That partition won't mount and DiskWarrior 3 freezes on step 5(locating directory info...). When I re-boot from another 10.2.6 partition, a 9.2.2 partition, Disk Warrior CD (3 and 2.1), I can make no progress in repairing the damaged partition.
TechToolPro 3 offers to fix the damaged partition, but the data verification (the last step before approving repair) page shows wildly different values for catalog b-tree: a) 368,728 original leaf record count and TTP tells me there will be 7,695 after any repair; used nodes are 7,286 now and 125 after any repair; and free nodes of 1,162 now with 8,323 after any repair. Similarly volume information regarding total files has 599 original and projects 2,472 after any repair.
I hesitate to let TTP go to work.
Curiously, I can see the icon for the hosed partition and the files on it when I boot from the 9.2.2 partition, but when I attempt a manual copy to an external firewire drive, I get error messages if I'm trying to move applications, system, and what seems like the larger folders.
I have a week old backup made from CarbonCopyCloner but would like to save the hosed partition because I'm a relative newcomer to OS 10. I miss the drag & drop option for backup.
Thanks for any help you can offer.

No apologies needed, this is a good place to ask for help.

Is this a bootable partition? I don't know what an "e/m and docs" partition is. An OSX bootable partition normally has upwards of 250,000 files on it, a stripped OS9 bootable partition should have at least 1,000 files for just the system.

If this is a data file partition, does TTP3's count of 599 files sound about right? If so, let it do the repair. The 2,472 includes 1,873 files that have been deleted at some point, most will end up in a recovered items folder so you can throw them out again.

This could very well be a bad block in the directory tree. A bad block could cause real problems for DW. If in doubt, let TTP3 test-mount the repaired volume in memory. Copy everything you want from that test volume to a safe partition, you do not need to let TTP3 complete the repair in order to do this.

The week-old backup sounds like the best thing. See if you can salvage just the files you have saved during the last week, from the TTP3 test-repair volume.

Whatever you recover, once you are done recovering, reformat that partition. I don't like it that DW froze trying to recover from it, and a reformat will map out the bad block(s).

[artlewis]

Thanks, greatly.
I'll give it a go and see what I can salvage.
I'll post the results.

[artlewis]

Nothing worked. I couldn't even reformat the drive with DW, Drive 10 or the OS X discs.
I'll toss the harddrive and see if I can install a new one.
Thanks, again for your help.