New jumpstart server installation not working
I recently set up a new jumpstart configuration on a Solaris 9 server. I believe I've followed all the various instructions but cannot get the jumpstart to work for either Sol 9 or 10 CD's I've loaded.
When I run the add_install_client for a Solaris 9 client, then do "boot net - install" it gets to a # prompt at /tmp/root, but no further with the jumpstart.
Then if I run add_install_client for a Solaris 10 client, do "boot net - install" on the same client, I get the error message
"waiting for X server to shutdown" which scrolls away and then the following:
Rebooting with command: boot net - install
Boot device: /pci@1f,0/pci@1,1/network@1,1 File and args: install
Timeout waiting for ARP/RARP package
SunOS Release 5.10 Version Generic_118833_17 64 bit
Copyright 1983-2005 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms
whoami: no domain name
svc configd: Fatal error /etc/svc/repository.db service_tbl table creation fails. Attempt to write a readonly database. Requested system maintenance mode. See lib/svc/share/README for more information. svc.configd exited with status 102 (database initialization failure)"
#
# pwd
# /tmp/root
# ls -al
# (shows /var and /etc directories dated Jun 9 2006 the same data as the CD's loaded to the jumpstart server)
My client is on the same network as the server. I might add that I had to use a different subnet because prior to getting this far - I found that another Solaris 10 server (without any jumpstart info!) was tried to answer the ARP messages.Using a different subnet temporarily resolved that, but issue will still be there if I ever get this to work.
[1769 byte] By [
hughesm1a] at [2007-11-26 13:33:20]
# 1
Hi,
I have two jumpstart servers.
One with NIS name service configured and one with no name service.
The NIS jumpstart server installes 11/06 clients ok.
The jumstart server with no name service configured fails with the same error listed below.
BTW
The server with no name service configured which fails can install 6/06 fine with no configuration changes.
I have the svcs coredump.
I will post any updates when I find.
# 3
We are not using NIS.
I'm very interested in your solution. Did you mean that you completely replaced the 06-06 version with 11-06? I have the following 06-06 version under:
/jumpstart/jump_5.10/Solaris_10/Tools/Boot
tsutils:hughesm> ls -al
total 60
drwxr-xr-x 18 rootother512 Nov 21 13:11 .
drwxr-xr-x4 rootbin 512 Dec 1 08:48 ..
lrwxrwxrwx1 rootother 16 Oct 23 11:32 .java -> ./tmp/root/.java
lrwxrwxrwx1 rootroot 13 Oct 23 11:32 .swapinfo -> tmp/.swapin fo
lrwxrwxrwx1 rootroot 13 Oct 23 11:32 .swappart -> tmp/.swappart
drwxr-xr-x3 rootother512 Jun 9 2006 .tmp_proto
drwxr-xr-x2 rootsys 512 Jun 9 2006 a
lrwxrwxrwx1 rootroot9 Oct 23 11:32 bin -> ./usr/bin
drwxr-xr-x2 rootsys 512 Jun 9 2006 cdrom
drwxr-xr-x10 rootsys 1024 Jun 9 2006 dev
drwxr-xr-x3 rootsys 512 Jun 9 2006 devices
drwxr-xr-x41 rootsys 3072 Jun 9 2006 etc
drwxr-xr-x13 rootsys 512 Jun 9 2006 kernel
drwxr-xr-x7 rootbin 3584 Jun 9 2006 lib
drwxr-xr-x2 rootsys 512 Jun 9 2006 mnt
drwxr-xr-x2 rootsys 512 Jun 9 2006 opt
drwxr-xr-x56 rootsys 2048 Jun 9 2006 platform
dr-xr-xr-x2 rootroot 512 Jun 9 2006 proc
-rw-r--r--1 rootother 0 Jun 9 2006 reconfigure
drwxr-xr-x3 rootsys 2048 Jun 9 2006 sbin
drwxr-xr-x4 rootroot 512 Jun 9 2006 system
-rw-r--r--1 rootother 0 Nov 21 13:11 testfile2
drwxrwxrwt4 rootsys 512 Jun 9 2006 tmp
drwxr-xr-x21 rootsys 512 Jun 9 2006 usr
lrwxrwxrwx1 rootother 14 Oct 23 11:52 var -> ./tmp/root/var
I just downloaded the 11-06 version so I'll need to make new CD's and DVD.
The funny thing is I also cannot get the Solaris 9 client to work, but with different results.
Thanks for replying.
# 5
Thanks to both of you for your help.
I couldn't get the "tar" of the older image to work but I installed the latest Solaris 10 11-06 version on the jumpstart server image in a new directory. I just got the first jumpstart to work with this new image without the errors I had before.
It still has some problems as of course it didn't work perfectly the first time, but at least I got the Solaris 10 OS loaded on the client!
Now if I can just get the Solaris 9 was fixed, too!
