From: true64@shore-lines.com
Date: Mon Nov 10 2003 - 08:58:09 EST
Managers,
I have a problem with diskless booting that after googling, I couldn't
find a solution. Some people have had this problem before, but I never
saw a solution. It just randomly happens when powering on my diskless
clients. Sometimes it'll happen to 1-3 of the clients, sometimes it'll
never happen.
The main problem looks like it can't mount its NFS shares to finish the
boot process. I can't tell if it's because the client isn't setting it's
hostname or what. Both of the following output snippets were taken from
the same machine, just at different times. When it hangs, I just cycle
the power and they work the next time.
On a GOOD boot I normally see:
------------------------------
kernel console: ace0
dli: configured
Booted from Network Interface (BOOTP 0 1001 0 0 0 3 0 00-C0-8B-06-88-5F 1)
bootp: Skipped type: 13 data
netblk.cliipadr ac104990
hostname: dlnetlca
...continues boot...
But on a BAD boot I see:
------------------------
kernel console: ace0
dli: configured
Booted from Network Interface (BOOTP 0 1001 0 0 0 3 0 00-C0-8B-06-88-5F 1)
bootp: Skipped type: 53 data
bootp: Skipped type: 54 data
bootp: Skipped type: 43 data
netblk.cliipadr 0
hostname: CLIENT
mountnfs: SERVER: portmap not responding
...hangs here forever...
I have no idea what netblk.cliipaddr is, but I guess it has something to
do with my problem. I'm not sure if it's a network load problem, or that
it "forgets" its hostname for some reason and doesn't have permision to
mount its shares. If anyone has ANY insights on this, I am desperate for
a solution.
Thanks in advance,
Joseph
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:43 EDT