Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!ICAEN.UIOWA.EDU!dbfunk
From: dbfunk@ICAEN.UIOWA.EDU (David B Funk)
Newsgroups: comp.sys.apollo
Subject: Re: Yet another SR10.1 problem
Message-ID: <8909080942.AA00712@icaen.uiowa.edu>
Date: 8 Sep 89 09:20:43 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: Iowa Computer Aided Engineering Network, University of Iowa
Lines: 39

Re the diskless node booting failure with  "boot error: uid request failed" error:

Yes there is a problem with netman at sr10.1 and diskless node
booting. The really strange part of it is it only occurs when you
do a forced partnering. If you partner via the "diskless_list" file
then things work OK. IE the problem only shows up when you use the
MD command "DI N node-id" and then try to boot. If you edit the
"diskless_list" file on the sr10 disked node and then let the
diskless node auto-partner then its OK. I've found 3 different
work-arounds for this problem.

1) Just use the "diskless_list" and auto-partner.

If you can't do that, or don't want to because it's a temporary
partnering, then there are 2 options.

2) do the "DI N node-id", then do a "LD", and then try to boot.
    For some strange reason, doing the MD command "LD" to get a
    directory listing from the disked node will make the boot
    succeed  (most of the time). IE:
   > DI N 12345
   > LD
   > EX DOMAIN_OS

3) If things are really tough, (IE the "LD" trick won't do it),
    then run netman in debug mode on the disked node. For some
    strange reason if netman is running in debug mode then it's
    better behaived. To run netman in debug mode, invoke it in a
    window and give it the "-db" option.

Be aware, if you have this booting problem then it's going to leave some
strange trash processes on your disked node after the boot request fails.
After you get the "boot error: uid request failed" error, do a "/com/pst -l1"
command on the disked node. You'll see some strange "level 1" process
appear. An additional one of these will appear for each failed boot attempt.
I don't know what the ramifications of these things are but I don't like
them. I'd reboot the disked node to get rid of them if I were you.

Dave Funk