[Update] - Jumpstart client hang at whoami

From: Alex Dyas (adyas@twowaytv.co.uk)
Date: Thu Oct 02 2003 - 10:02:59 EDT


Hi,

Unfortunately time not being on my side I had to abandon the problem and
  install Solaris from the CDs instead. Shame.

However thanks to Greg and Darren for suggesting the following :

>Hi Alex,
>
>This looks like you haven't got the right file in the /tftpboot
>dirctory.
>
>Did you use the add_install_client script or just add the entries into
>/etc/bootparams and /etc/hosts manually??
>
>HTH,
>
>Greg

>Hard to tell exactly where that is. On the assumption that it's
>already started rcS, I'd modify the script.
>
>Edit (on the server) jumpstart/Solaris../Tools/Boot/sbin/rcS and add a
>'set -x' to near the top. If it starts, at least you'll start getting
>some verbose output.
>
>Darren Dunham

Alex..

Original message :

> Hi all,
>
> I am having problems jumpstarting an E450. The jumpstart server has
> been used to successfully jumpstart around 20 machines already (Ultra 5,
> E220), and other machines still jumpstart without problems. In fact I'm
> fairly certain I have jumpstarted this particular machine in the past.
> The problem with the E450 seems to be happening at or after the whoami
> line seen on the console:
>
> ...
> Copywright 1983-2001 Sun Microsystems, Inc All rights reserved.
> whoami: no domain name
> ..hang..
>
> I thought maybe it was just slow, but I left it like this over night and
> it hadn't progressed by the morning.
>
> <ethers>
> 08:00:20:b2:76:da db-e1
> </ethers>
>
> <hosts>
> 172.17.128.234 db-e1
> </hosts>
>
> <bootparams>
> db-e1 root=deploy1:/jumpstart/OS/Solaris_8_2002-02/Solaris_8/Tools/Boot
> install=deploy1:/jumpstart/OS/Solaris_8_2002-02 boottype=:in
> sysid_config=deploy1:/jumpstart/Sysidcfg/Solaris_8
> install_config=deploy1:/jumpstart rootopts=:rsize=32768
> </bootparams>
>
> A snoop of the traffic at this point shows :
>
> <snoop>
> ...
> deploy1 -> db-e1 TCP D=1023 S=2049 Ack=30035194
> Seq=2892135500 Len=1460 Win=24820
> deploy1 -> db-e1 TCP D=1023 S=2049 Ack=30035194
> Seq=2892136960 Len=1460 Win=24820
> db-e1 -> deploy1 TCP D=2049 S=1023 Ack=2892125280
> Seq=30035194 Len=0 Win=24820
> db-e1 -> deploy1 TCP D=2049 S=1023 Ack=2892136960
> Seq=30035194 Len=0 Win=24820
> deploy1 -> db-e1 TCP D=1023 S=2049 Ack=30035194
> Seq=2892138420 Len=1460 Win=24820
> deploy1 -> db-e1 TCP D=1023 S=2049 Ack=30035194
> Seq=2892139880 Len=1040 Win=24820
> db-e1 -> deploy1 NFS C LOOKUP3 FH=8AF0 se.conf
> deploy1 -> db-e1 NFS R LOOKUP3 No such file or directory
> db-e1 -> deploy1 NFS C LOOKUP3 FH=CE78 se.conf
> deploy1 -> db-e1 NFS R LOOKUP3 No such file or directory
> db-e1 -> deploy1 NFS C LOOKUP3 FH=D860 se.conf
> deploy1 -> db-e1 NFS R LOOKUP3 No such file or directory
> db-e1 -> deploy1 NFS C LOOKUP3 FH=FB89 se.conf
> deploy1 -> db-e1 NFS R LOOKUP3 No such file or directory
> db-e1 -> deploy1 TCP D=2049 S=1023 Ack=2892141400
> Seq=30035674 Len=0 Win=24820
> </snoop>
>
> A successful jumpstart looks exactly the same at this point, but then
> carries on. I'm stumped.
>
> Any help much appreciated.
>
> Cheers,
>
> Alex..
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers



This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:27:13 EDT