lavachr strager idelia
Gene Honnette
I just got a copy of diskwarrior and after it scanned my main drive, I opened the "Graph" section. It told me 33% of that partition was out of order. It had blue items at the beginning instead of all white and gradually going to blue.
DiskWarrior is one of the most highly respected disk repair utilities in the Mac universe. It is very well written and has been a last resort for disk fixing especially in the OS 9 days when Macs crashed a lot more and screwed up the disk directory much more.
But if your disk works fine and is fixable by Apple Disk Utility, DiskWarrior isn't going to help much more. And honestly, there has been a lot less of a need for DiskWarrior as OS X has improved how it handles the disk directory over the past 15 years.
If you already paid for DiskWarrior and it says it should fix something, you have nothing to lose. It won't hurt anything and might help prevent invisble problems from compounding. But what you shouldn't expect is some kind of dramatic improvement. DiskWarrior will probably fix something worth fixing but the difference in actual use might not be noticeable unless it was a serious problem.
OS X defragments files under 20MB by itself, but that is a different operation than defragmenting the disk directory. I don't think OS X does that by itself, but it not normally a problem for most people. Again, a fragmented disk directory was probably a much bigger problem when DiskWarrior was originally invented, back in the days of much slower systems and no SSDs.
If you're in that position, then instead of spending about $100 on software that you should never need again, make a "Genius" appointment at an Apple Store, where the program is available for the "Geniuses" to use on customers' machines at no charge.
The kind of directory corruption that you might need Disk Warrior to recover from can, for all practical purposes, only happen because of a hardware malfunction. It is not caused by forced shutdowns or system crashes. Any drive that malfunctions in that way should preferably be replaced at once. Even if you choose to take the risk of continuing to use the drive after the first such incident, after any repetition the drive should be wiped and recycled, not restored. Occasionally the fault might be in another internal component, or in an external drive enclosure, rather than in the drive mechanism itself.
after around 50 hours, diskwarrior gave me my drive back, with all the files intact. it ended up with 1961 overlapped files. i guess i was lucky, but from now on i will make sure i have a copy the diskwarrior cd with me wherever i go. i love this program!
Ran DW for a couple of days (step 6) too long. The drive will not mount in OS X but will mount with OS 9.3.9. So, I think I will have to purchase anoyher drive and transfer the data, then format the bad drive.
Because I have run Diskwarrior probably thousands of times (tech job), I can say with the utmost confidence that you should bail out on Diskwarrior when it finds more than 2 overlapped files. It will attempt to fix, and then fail.
How could it fail though? It was working just fine a couple minutes ago. How could software physically destroy the drive, (not by any means underestimating what people could do i suppose, but an osx disk?)
I had to call a quit on DW. Right now, once I turn it on, the DW screen does not show up any more. The laptop is on for a little while and automatically shut down by itself. The DW disk is still inside my laptop. How can I get it out? so that I can insert the Snow and get it over with. thanks for help guys!!! My computer is the black Macbook.
My 10 day Dilemma:
Last week Sunday ( today is wednesday) whilst my Lacie 1 tb hardrive was on i was currently editing a video piece on my mac book pro Final cut version 7 as normal. My 1 tb drive had a bout 300gb free.
I tried a variety of options turning on and off the computer and hardrive , changing power cables , fire wire cables. I also checked the Lacie Hardrive on a Pc and it booted so this gave me a feeling that it at least could be repaired on Disk Utility on my Mac.
I Followed a few online examples in which i changed the casing on my Lacie 1 tb with another identical 1 tb drive.
After changing casing on the drives the hardrive which previously was un readable was still unreadable by my mac book pro and the one that worked still was readable.
Last week Monday i started Disk warrior 4.4 on Mac it has been running for nearly 10! full days and is still going. Even though I can not click on the disk warrior application it has the spinning beach ball , But the numbers of Disk Malfunctions are painfully slowly climbing.
The files are important and contain client files , the capture files of a project I was working on. Most of the finished files are backed up but there are files such as digitised footage for projects I was in the process of working on . I have no other way to retrieve those files as the only place they exist is on this drive.
As my External drive was previously bootable on a pc ( which I checked before starting disk warrior 10 days ago) I am thinking to maybe cancel disk warrior try booting on the pc and connecting another drive to copy the files over. Do you think this would work ?
Has anybody ever been in a similar positions in which Step 5 has hanged for so long , with a similar amount of Disk Malfunctions I have and it actually turned out for Drive to be fixed , repaired and work smoothly afterwards ?
Diskwarrior 5 stuck in Step 6 for almost 1 week (6 day and 15 hours) and after detecting over 55k overlapped files. Then I view the report, and click the replace. It quickly goes to Step 12 of 12 repairing overlapped file. there was no progress on diskwarrior progress bar to tell how many overlapped file is fixed. This step 12 stuck for another 5 days, then it give me the following error:
At this point, fsck_hfs verification has NO error anymore. TimeMachine backup verification also passed. but I am still not sure, so let diskwarrior5 do another rebuild. this time it finished in 30 minute and replace take about 5 minute only. No overlapped file detected anymore.
c01484d022