Originally posted by headbirth:
Has anyone noticed this:
I built the new 3.0.1 boot cd and tested it out. When I ran it on my drive it told me that there were a couple of Text Encoding problems on two files (text clippings, always happens), but that my drive was to severely damaged to rebuild????
I then ran my old 3.0 CD and it immediately picked up a Volume Wrapper problem and offered to repair it. Whallah, repaired the problems and rebuilt the drive.
Is this a bug with 3.0.1?
I was going to post this too! I have the exact same problem with one of my drives. The drive is working
just fine and checks out OK in Disk Utility. DiskWarrior 3.0.1 claims my drive is too damaged to rebuild. Booting from the 3.0 CD, it finds a Volume Wrapper problem, fixes it, all is hunky dory. But if I run 3.0.1 again, it will still claim the drive is too messed up to fix!
And then if I run 3.0 again it will have the same wrapper problem (although if I run it a second time immediately after fixing it, it reports no problems).
What's going on? This is suspiciously reminding me of what Norton used to do - report problems it can't fix when every other utility says the disk is fine. Oh well, at least DiskWarrior tells you it can't fix the problems
before it starts making changes, unlike Norton which would "fix" a number of things and then crap out, leaving your drive unmountable.
EDIT: I just tried running DiskWarrior 3.0 again, and it reported no problems whatsoever except for a broken symlink (big deal). Not sure why it reported the Volume Wrapper error earlier after having already fixed it, but I am starting to get suspicious of 3.0.1, which of course still thinks my drive is borked beyond repair. As I see it, there are three possibilities:
1. 3.0.1 has some bug which is making it screw up while comparing the two directories, leading it to conclude that the drive is hosed
2. 3.0 was blind enough to miss a
giant hopeless unfixable error which, incidentally, is also missed by Disk Utility/fsck
3. 3.0.1 has some problem with OS 9 (the drive in question is my Classic drive which contains my OS 9 system folder and all my Classic apps)
Right now, I'm leaning towards #1. Another bug in 3.0.1 I've noticed is that when you have a disk that does show up fine on the Desktop, and you have DiskWarrior start working and it unmounts the disk, all of a sudden DiskWarrior says "This disk does not appear on the Desktop." when it clearly does, but DiskWarrior unmounted it. 3.0 didn't do this.
This is all making me
... I think I'm going to stick with booting from the 3.0 CD until this issue is cleared up.
Top
