[nuggetman]

so diskwarrior has been sitting at step 11/11 (rebuilding overlapped files) for a good 2 hours now. the progress bar is creeping like molasses. how long should this step take? i had somewhere around 4300 overlapped files. what would happen if this process got interrupted?

[msuper69]

Originally posted by nuggetman:
so diskwarrior has been sitting at step 11/11 (rebuilding overlapped files) for a good 2 hours now. the progress bar is creeping like molasses. how long should this step take? i had somewhere around 4300 overlapped files. what would happen if this process got interrupted?

If Diskwarrior is properly programmed, nothing should happen. But I've never stopped it before.

It can run for any incredibly looooong time in it's attempts at fixing all those errors. You have to have a boatload of patience.

[MM-o4]

had the same thing happen on my G5 at work. It had 19 overlapping files and took almost 2 full days to repair. But it did it! Got all the files back and the machine started up again.

BTW it only lasted a month before it happened again and we ended up getting it replaceed under warranty. So make sure your careful with what you do with the drive afterwards. I suggest a full (zeros) format and regular desktop file rebuilding to keep everything healthy. I could be a little bit of a panic merchant but. Your drive could be fine after it's done.

Just let DW do it's thing. Let it go as lond as you can

Good luck

MM-o4

[Podolsky]

Would love to hear back from you how this resolved itself but if the MM-o4's experience is indicative - we may not be hearing back from you for something like 450 days!!!! By that time, Dick Cheney could be president and oli may be $300 dollars per gallon!!!!

Good luck I am a HUGE fan of DiskWarrior - use it once per week.

[Xeo]

Originally posted by Podolsky:
Good luck I am a HUGE fan of DiskWarrior - use it once per week.

Good lord, why?

I have never run DiskWarrior on my iBook. Ever.

[Podolsky]

Originally posted by Xeo:
Good lord, why?

I have never run DiskWarrior on my iBook. Ever.

Why? Read this thread for one answer....regular use of DiskWarrior and few other tools could have saved the original poster from the significant problem he maybe facing. But, I am not here advocating for any products or any maintainance regimes and I don't really give a hoot or a holler for what anyone else does... I just mentioned that I use DW along with a few other system tools (such as Cocktail or Onyx) that together with those that are built into OSX allow me (if nothing else), tell myself, that I along with OSX are doing/have done what is best to maintain these complex systems. I aslo back up everything each and every week. So, if my system and/or hard drive crash, which they eventually will, and I go on the inevitable blame-fest - I won't have to blame myself or lose all my music, images, data....

But, I am not looking for a fight here or even a discussion of the merits. Rather, I was simply sharing my experince. I have had years of totally stable performance with no lose of data. And while I can not ever be sure what the contribution to that stability has been imparted by actions I take, I do feel that it does make a real, measurable positive difference. For example, I fix a lot of Macs for friends and invariably I find that they, like Xeo, do nothing whatsover to augment the stability of their systems. Whereas, folks I know who use a few of these tools I find they suffer fewer errors and lose of data or prodcutivity. OSX is simply great at having reduced the need for user involvment in system upkeep but in my opinion it has not totally obfuscated the need.

[badidea]

Originally posted by nuggetman:
so diskwarrior has been sitting at step 11/11 (rebuilding overlapped files) for a good 2 hours now. the progress bar is creeping like molasses. how long should this step take? i had somewhere around 4300 overlapped files. what would happen if this process got interrupted?

You don't have Norton Personal Firewall installed (or something else from Norton?), do you?

I also once had an overlapping files problem that always came back after I repaired it with DiskWarrior until I finally found out that it was NPF's fault...