[macibookg3]

I am have a 1.5Ghz Intel core solo Mac Mini with Leopard 10.5.1 and DiskWarrior 4.1 r42 and I have a Newer Tech USB/Fire case with a Seagate 300 Gig drive in it.
The drive is set to Journalized not case sensitive and is one partition. I use the drive for Time Machine and to store my Video files. but the other day I went to turn on the mini & Drive and the drive would not mount. The finder said "Do you want to Initializes, ignore or eject the drive. The Disc Utility said that there was a problem with the B-Tree and was not able to fix the problem and canceled the verification and repair. Disk Warrior gave me error 32.


Please help me out. you can aim me @ macibookg4

[CharlesS]

Open the Console application in the Utilities folder, then run DiskWarrior. At some point you'll see an entry like this in the console:

DiskWarrior App: disk1s10 Extents, Catalog and Attributes tree sizes total <some number> GB.

What size do you see there?

[pocsy]

Charles - I have the same issue as Macibookg3. I checked my console log and it says

2/3/08 9:58:24 AM [0x0-0x7d67d6].com.alsoft.diskwarrior[13347] DiskWarrior App: Rebuilding disk device: disk1s3
2/3/08 9:58:28 AM [0x0-0x7d67d6].com.alsoft.diskwarrior[13347] DiskWarrior App: Journal header checksum is bad.
2/3/08 9:58:28 AM [0x0-0x7d67d6].com.alsoft.diskwarrior[13347] DiskWarrior App: Journal header checksum is bad.
2/3/08 9:58:28 AM [0x0-0x7d67d6].com.alsoft.diskwarrior[13347] DiskWarrior App: disk1s3 Extents, Catalog and Attributes tree sizes total 1.05 GB.
2/3/08 9:58:29 AM [0x0-0x7d67d6].com.alsoft.diskwarrior[13347] DiskWarrior App: Journal header checksum is bad.
2/3/08 9:58:30 AM [0x0-0x7d67d6].com.alsoft.diskwarrior[13347] DiskWarrior App: Journal header checksum is bad.
2/3/08 9:58:50 AM [0x0-0x7d67d6].com.alsoft.diskwarrior[13347] DiskWarrior App: Journal header checksum is bad.
2/3/08 10:04:02 AM [0x0-0x7d67d6].com.alsoft.diskwarrior[13347] DiskWarrior App: The size of the AP extents is 40448.
2/3/08 10:04:09 AM [0x0-0x7d67d6].com.alsoft.diskwarrior[13347] DiskWarrior App: The size of the AP extents is 40448.
2/3/08 10:04:11 AM [0x0-0x7d67d6].com.alsoft.diskwarrior[13347] DiskWarriorRebuildServer: ERROR. Initial iterator failure, Applications (0)
2/3/08 10:04:11 AM [0x0-0x7d67d6].com.alsoft.diskwarrior[13347] DiskWarriorRebuildServer: ERROR. Unable to iterate for comarison, Applications (0)
2/3/08 10:04:12 AM [0x0-0x7d67d6].com.alsoft.diskwarrior[13347] DiskWarriorRebuildServer: ERROR. Initial iterator failure, Address Book Plug-Ins (0)
2/3/08 10:04:12 AM [0x0-0x7d67d6].com.alsoft.diskwarrior[13347] DiskWarriorRebuildServer: ERROR. Unable to iterate for comarison, Address Book Plug-Ins (0)
2/3/08 10:04:12 AM [0x0-0x7d67d6].com.alsoft.diskwarrior[13347] DiskWarriorRebuildServer: ERROR. Initial iterator failure, Application Support (0)
2/3/08 10:04:12 AM [0x0-0x7d67d6].com.alsoft.diskwarrior[13347] DiskWarriorRebuildServer: ERROR. Unable to iterate for comarison, Application Support (0)

It will go on and on like this until:

2/3/08 10:05:40 AM [0x0-0x7d67d6].com.alsoft.diskwarrior[13347] DiskWarrior App: Rebuilding disk device disk1s3 has ended.
2/3/08 10:05:41 AM [0x0-0x7d67d6].com.alsoft.diskwarrior[13347] DiskWarrior App: Error resolving disk with VM pages. (-43)

After that I tried to repair wit disk utility which found ownership issues with a lot of hard-links. I suspect I messed too much with the time machine files. Anyway, The disk utility repair as reported to be successful, so I ventured into another disk warrior session with the following console entries:

2/3/08 1:19:20 PM [0x0-0x28028].com.alsoft.diskwarrior[251] DiskWarriorRebuildServer: Couldn't open 'rc' file, error '2'
2/3/08 1:19:22 PM [0x0-0x28028].com.alsoft.diskwarrior[251] DiskWarriorRebuildServer: Error 1 executing '/sbin/kextunload',
2/3/08 1:19:22 PM [0x0-0x28028].com.alsoft.diskwarrior[251] kextunload: unload kext /Applications/Utilities/DiskWarrior.app/Contents/MacOS/DiskWarriorPreview.kext failed
2/3/08 1:19:22 PM [0x0-0x28028].com.alsoft.diskwarrior[251] DiskWarrior App: Error resolving disk with VM pages. (-43)
2/3/08 1:19:34 PM [0x0-0x28028].com.alsoft.diskwarrior[251] Wired PhysicalMemory = 440.69 MB
2/3/08 1:19:34 PM [0x0-0x28028].com.alsoft.diskwarrior[251] Active PhysicalMemory = 695.42 MB
2/3/08 1:19:34 PM [0x0-0x28028].com.alsoft.diskwarrior[251] Inactive PhysicalMemory = 305.31 MB
2/3/08 1:19:34 PM [0x0-0x28028].com.alsoft.diskwarrior[251] PhysicalMemory Used = 1.41 GB
2/3/08 1:19:34 PM [0x0-0x28028].com.alsoft.diskwarrior[251] Free Physical Memory = 2.58 GB
2/3/08 1:20:01 PM [0x0-0x28028].com.alsoft.diskwarrior[251] DiskWarrior App: Rebuilding disk device: disk2s3
2/3/08 1:20:02 PM [0x0-0x28028].com.alsoft.diskwarrior[251] DiskWarrior App: disk2s3 Extents, Catalog and Attributes tree sizes total 1.05 GB.
2/3/08 1:22:41 PM [0x0-0x28028].com.alsoft.diskwarrior[251] DiskWarrior App: DHLs, DIs, FHLs, FIs: 12580, 9947, 238835, 224033.
2/3/08 1:22:59 PM [0x0-0x28028].com.alsoft.diskwarrior[251] DiskWarrior App: Rebuilding disk device disk2s3 has ended.
2/3/08 1:23:00 PM [0x0-0x28028].com.alsoft.diskwarrior[251] DiskWarrior App: Error resolving disk with VM pages. (-43)

The third last line corresponded with the application reporting abortion of the process and stating an unexpected error (32).

What next?

Adam

[CharlesS]

Unfortunately, that error isn't what I was hoping it was going to be, so I don't have any answers for that one.

You might want to contact Alsoft and give them those logs, though - they'll probably be able to at least tell you what's going on based on that info, which is nicely detailed.

One thing I suppose you could try would be holding down the Option key while clicking the "Rebuild" button in DiskWarrior and then selecting the "Scavenge" option.

[Big Mac]

I feel so bad for people with drive problems. I've had exceptionally good luck with my many hard drives. I've only had a single drive failure on my Macs in my 17 years of Mac ownership, and that was a drive on a Mac that was backed up and no longer my primary.

[Cold Warrior]

Originally Posted by Big Mac 

I feel so bad for people with drive problems. I've had exceptionally good luck with my many hard drives. I've only had a single drive failure on my Macs in my 17 years of Mac ownership, and that was a drive on a Mac that was backed up and no longer my primary.

Seconded. In all my years owning Macs (not as long as you though), I've had one hard drive error. It was on a PB G3 Wallstreet running OS 8.x, and I picked up on the error a couple months into owning it (late 1998), when the system started locking up (more than normal, in those days). I ran Apple's utility, but it couldn't fix it. Then I ran a 3rd-party tool, which thankfully isolated the bad section of the drive and managed to recover 99% of the data there). It was good for several years until I upgraded the drive.

[pocsy]

Guys - thanks for your sympathy. Until recently I was one of you: 19 years without drive issues. In fact my 1988 MacSE, my second Mac is still running without any issues (fastest booting ever!).
Then my first MacBook drive failure occurred, where miraculously all backed-up data was lost and all data not backed up could be recovered. The replacement drive just failed a few days ago.

I love Apple truly for saving me from that cheap imitation from Redmond - but one has to say that the MacBook is the most unreliable product they ever shipped. 3 out of 4 I'm dealing with have severe issues to be handled under warranty. Not a good track record.

Cold Warrior: Glad to hear you are fighting that bear - it needs fighting!

[macibookg3]

Thanks you All for you help but I found out that Time Machine crashed my 300 Gig HD for good. I am now getting i/o errors when trying to save the drive with Disk Utility, Tech Tool Pro, Disk Ware, or Spin Right