I'd still be interested to hear if there is anything more I should have done. Tried to do an "Archive and Install" re-installation, to save original disk contents, but the Installer refused to install on that drive due to filesystem corruption. The expert walked me through SMC reset, which did nothing. Tried resetting PRAM (Command-Option-PR on startup).This repeated every time I tried to reboot with the internal disk. DiskWarrior and other tools that modify or rebuild the directory of volumes should not be run after installing Mac OS X 10.5 (Leopard) until further notice or updates from the developers of these. Apple logo appeared, and wheel spun for about 15-20 seconds, then machine turned off. And when I did "exit", I saw error message "disk0s2: I/O error" followed by "CPU Halted". "/sbin/fsck -yf" gave more error messages. Restarted in single-user mode (Command-S on boot).Is there anything else I can do to try to repair the filesystem (besides erase and reinstall)?įWIW, here's what happened after I asked this question: When I run "Repair Disk", I get this output: Verify and Repair volume "Macintosh HD"Įrror: Filesystem verify or repair failed. So, I restarted with the Mac OS X Install Disc and ran Disk Utility again. The "Repair Disk" button was disabled, because this is the startup drive. It seems to work fine, but when I ran Disk Utility and did a "Verify Disk", it reported filesystem errors. All current indications are that the program will run, and rebuild directories on bootable Leopard volumes and could result in serious consequences, including an inability to startup from the drive.My wife has been complaining about her MacBook Air's performance. The update for DiskWarrior that makes it compatible with Leopard will be free of charge.ĭespite point #2, we highly recommend not running DiskWarrior at all after installing Mac OS X 10.5 until further information is available.The current version of DiskWarrior won't cause damage to Leopard disks because it will simply refuse to perform the process for which it is designed.They can't guarantee compatibility of the current DiskWarrior iteration with Leopard.More information will be posted on the Alsoft website, once Leopard is released.Įssentially it looks like Alsoft is claiming: Each of these updates was available through the process of downloading an updater which helps you burn an updated DiskWarrior CD.
The same is true for when Mac OS X 10.4 (Tiger) was released - no charge. When Mac OS X 10.3 (Panther) was released we updated DiskWarrior for compatibility at no charge. "When DiskWarrior 3 was released 3 1/2 years ago, Mac OS X 10.2 (Jaguar), was the current version of the operating system.
If a newer version of DiskWarrior is required, DiskWarrior will simply not allow the replacement of the old directory. "As for your current version of DiskWarrior, you can run the application knowing no harm will come to the hard drive or to your data. Apple engineering may make changes right up to the last few days before the release and we wouldn't know about them until after the fact. While we have the early builds of Mac OS X 10.5 to test with, Apple does not tell us ahead of time what changes or enhancements they plan to make until they provide us with the software and documentation. "We will absolutely support Mac OS X 10.5. " until we have a copy of the final build of Leopard, we cannot completely comment on Leopard compatibility. DiskWarrior and other tools that modify or rebuild the directory of volumes should not be run after installing Mac OS X 10.5 (Leopard) until further notice or updates from the developers of these tools.Īs part of our special report on preparing for Mac OS X 10.5 (Leopard) published yesterday we noted that previous major Mac OS X releases have made significant disk directory changes that can react adversely to the processes used by these applications.Īlsoft, the developer of DiskWarrior, has now released a statement on compatibility that is somewhat confusing.