[jacobpearson]

Not really a lot of groups, no more than we’ve had running in this school, and in the last one I was in. This particular user is a member of five groups including Domain Users and Staff.

It just seems at random it will pick a staff member once every four months, and they’ll lose access to the xServe. having said that, only about 10 staff members need access to the xServe, and it could be messing with the 250 or so Windows users that don’t go near the xServe.

[jacobpearson]

I’m having almost the exact same problem,

I had two images enabled on the server, but the the netinstall process defaulted to the older image, even though I select the newer image. It did however install perfectly. I didn’t think to try a verbose install before I disabled the older image.

With the older image disabled, the newer image would hang there with the ticker flicking over. When I viewed the verbose output, it created the RAM discs, then:

[code]netinfod local[26]: unable to bind to parent – RPC: Timed Out
lookupd [43]: NetInfo connection failed on server 127.0.0.1/local
kern.maxunodes: 2500 -> 2864[/code]

later in the output it said:

[code]lookupd[96] Can’t load /system/library/PrivateFrameworks/NetInfo.framework/Resources/lookupd/Agents/DS.bundle/DS
/System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framework/Support/ATSServer: (-1) Cannot use ATS Persistent Store – switching to old FODB cache code
/etc/rc.cdrom.postWS: line 35: kill: (108) – No such process[/code]

it also reported that the files for quartz weren’t available, then [code]Network Installer has quit due to an unexpected error. (exit code 133) Please restart your computer[/code]

Interesting that without being in verbose mode, I’d never have seen these messages, the GUI doesn’t produce any notifications at all.

Now the annoying part: I’ve opened up both the old and new images, and those files that verbose mode marked as missing or not available are indeed not there, but are missing in both the working and not working images.

And the really annoying part: coolpor2 your way of fixing the image is exactly the way that I did it in the first place. I created the system on my G5, then started it as a firewire drive and hooked it up to my xServe, and created the image directly on the xServe with SIU. So I’m now trying the way that failed for you, and if that doesn’t work – and nobody here replies with a suggestion – I’ll be using Mike’s tools.

[Author]

Posts