[The OSX Guy]

Well, went to the apple store today, picked up my shiney new copy of 10.5. Brought it home, ran the upgrade on my MBP. It installed, rebooted and seemed to boot for what took about 45 mins. Nothing happened....I rebooted in cmd-s mode, ran fsck -f to do a diskcheck. Came back no errors. Rebooted, the machine was stuck for another 1/2 hour. I did a force reboot again, this time in verbose mode. Now I am looking at the screen that is hung on localhost, directory service, launched version 5.0, then the next line says crash report located at a certain area of the machine. too much crap to write out. I have been searching forums and have nothing yet.

ANy clues?

[ginoledesma]

It seems you've fallen victim to a failed install. Same thing happened to me -- what seems to be happening is that nibindd was crashing (in my case). I didn't have any hacks (e.g. Unsanity haxies, APE, etc), but my straight upgrade didn't work.

My recommendation: reinstall Leopard again, but this time use Archive and Install. You'll preserve your previous data and apps but start with a "fresh" copy of Leopard.

[~bash $]

Another thing to do during the install process is go to one of the menu options and there is a choice to view an installer log while the install is happening. In this, there is a 'detailed' view all events mode that is really cool and gives you a good idea of what's going on. Might be helpful for troubleshooting, who knows. Hope all goes well ...

[The OSX Guy]

Well, here is an update. I just tried to do a archive and install. Same thing: directoryservice crashes.

[krove]

My install went off without a hitch, but directory service kicks up to 100% cpu usage and stays there. Only way to fix it is to restart. I could kill it, but isn't it a necessary service?