1301 Views 5 Replies Latest reply: Mar 13, 2008 5:45 AM by Strontium90
Let's just say we are working on establishing it as known. You're description: 10.4.11 with AD/OD bind and Parallels with shared networking at startup is common to what I've been seeing in the field. The common thread is the automount process hanging and failing to recover as seen in the example below:
Mar 11 14:08:01 macstation9 Parallels: Restarting InternetSharing...
Mar 11 14:08:01 macstation9 Parallels: Initialization complete.
Mar 11 14:08:01 macstation9 /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow: Login Window Application Started
Mar 11 14:08:02 macstation9 automount: deferring user logout notification while init is in progress...
Mar 11 14:08:02 macstation9 loginwindow: Login Window Started Security Agent
Mar 11 14:08:04 macstation9 automount: deferring network change notification while initialization is in progress...
Mar 11 14:10:12 macstation9 automount: reposting deferred logout notification.
And that is it. Removing the Parallels' startup items allows the system to boot normal. Removing all DS bindings but putting the Parallel's startup items back allows the system to boot normal. Binding and placing the startup items in then pulling ethernet to startup will allow the uncheck of starting up ethernet at system boot. This appears to allow for "normal" booting.
I am still actively tracking this issue down and working with swsoft to see if there is a known problem. One of my field techs changed the order preference in Parallels' StartupParameters.plist from "First" to "Last" and claims that it has resolved the long/never startup issue. I have not confirmed.