[SunHELP] Solaris 9 network install problems... continued

[Ryan Loiselle]

When tring to initiate a network install on my Netra t1 105 (client), I am
still getting the following error:

Using External Transceiver - Link Up.
24000
Server  IP address: 10.10.10.7
Client  IP address: 10.10.10.20
Using External Transceiver - Link Up.
boot: cannot open kernel/unix
Enter filename [kernel/unix]:


I have done a bit more reading in regards to the rules, rules.ok, and
profile files that are required to complete a Jumpstart installation. (I
had read about them, but had previously only created a sysidcfg file).
Below is a listing of the configurations present on my Sun Blade 100
(server):

bash-2.05$ cat /etc/bootparams
wwwserv
root=10.10.10.7:/export/storage/Solaris9_install/Solaris_9/Tools/Boot
install=10.10.10.7:/export/storage/Solaris9_install/ boottype=:in
sysid_config=10.10.10.7:/export/storage/Solaris9_install/Jumpstart/Jumpstart
install_config=10.10.10.7:/export/storage/Solaris9_install/Jumpstart/
rootopts=:rsize=32768


bash-2.05$ ls -la /export/storage/Solaris9_install/
total 36
drwxrwxr-x   5 root     sysadmin     512 Jul 16 01:45 .
drwxrwxr-x   7 root     sysadmin     512 Jun 26 13:22 ..
-r--r--r--   1 root     root          85 Apr 12  2002 .cdtoc
drwxr-xr-x   5 root     other        512 Jun 11 19:08 .install
lrwxrwxrwx   1 root     other         32 Jun 11 02:58 .install_config ->
./Solaris_9/Misc/.install_config
-r--r--r--   1 root     root         462 Jun 11 03:22 .slicemapfile
-r--r--r--   1 root     root          16 Apr 12  2002 .volume.inf
-r--r--r--   1 root     other         18 Jun 11 19:08 .volume.inf.2
-r--r--r--   1 root     root        6379 Apr 12  2002 Copyright
drwxr-xr-x   2 root     other        512 Jul 16 01:55 Jumpstart
drwxr-xr-x   8 root     root         512 Jun 11 19:04 Solaris_9
-rwxr-xr-x   1 root     other        257 Jun 11 19:08 installer


bash-2.05$ ls -la /export/storage/Solaris9_install/Jumpstart/
total 114
drwxr-xr-x   2 root     other        512 Jul 16 01:55 .
drwxrwxr-x   5 root     sysadmin     512 Jul 16 01:45 ..
-rw-r--r--   1 root     other        182 Jul 14 20:02 any_machine
-rwxr-xr-x   1 root     other      44928 Jul 14 20:02 check
-rw-r--r--   1 root     other          0 Jul 14 18:40 emailprofile
-rw-r--r--   1 root     other       4782 Jul 29 02:09 rules
-rw-r--r--   1 root     other         61 Jul 29 02:09 rules.ok
-rw-r--r--   1 root     other        348 Jun 26 13:45 sysidcfg
-rw-r--r--   1 root     other          0 Jul 14 18:40 wwwprofile

I have tried the rules file with the following 2 rules:

bash-2.05$ cat /export/storage/Solaris9_install/Jumpstart/rules.ok
any -   -   any_machine  -
# version=2 checksum=2562

&

bash-2.05$ cat /export/storage/Solaris9_install/Jumpstart/rules.ok
network 10.10.10.0      -       any_machine     -
# version=2 checksum=2562

And both attempts with those rules file use the default any_machine
profile (Untill I get this working properly, I will work with defaults,
then I will start playing with the config options that I need):

bash-2.05$ cat /export/storage/Solaris9_install/Jumpstart/any_machine
install_type    initial_install
system_type     standalone
partitioning    default
cluster         SUNWCuser
cluster         SUNWCxgl delete
package         SUNWaudmo add
filesys         any 40 swap
filesys         any 50 /opt

When I boot the netra, I see packet xfer on the ntwk, I see the tftpd chew
up some CPU time, I see the mount daemon, and a couple of rpc.xxx chew up
some CPU time, and then it just times out.

I was wondering if the fact that this is presently all on a hub might be
causing some problems (collisions?) I just recieved my replacement
Catalyst 1924 in the mail but the operational software was corrupt, so I
will have that in service in a couple of weeks.

Does anyone have any further suggestions? hints? things I should look at?

Oh, I guess the only other thing that I could provide would be:

bash-2.05$ tail /var/adm/messages
Jul 26 15:50:32 blade-azonicnet.com automountd[237]: [ID 784820
daemon.error] server unknown not responding
Jul 26 15:50:32 blade-azonicnet.com last message repeated 3 times
Jul 26 16:00:47 blade-azonicnet.com automountd[237]: [ID 784820
daemon.error] server unknown not responding
Jul 26 16:00:47 blade-azonicnet.com last message repeated 3 times
Jul 26 16:11:02 blade-azonicnet.com automountd[237]: [ID 784820
daemon.error] server unknown not responding
Jul 26 16:11:02 blade-azonicnet.com last message repeated 3 times
Jul 26 16:22:32 blade-azonicnet.com automountd[237]: [ID 784820
daemon.error] server unknown not responding
Jul 26 16:22:32 blade-azonicnet.com last message repeated 3 times

I am only posting this is because I was wondering if perhaps there was a
problem with the NFS mounts when the client is trying to mount the shared
dirs:

bash-2.05$ share
-               /export/storage/Solaris9_install   ro,anon=0   ""



Thanks!

Ryan Loiselle