I am trying to get solaris to install over a network (just connected
by a hub, no routers etc).
On the machine with the cdrom I have tried several different
add_install_client permutations.
For example:
"./add_install_client -d -e [mac address of machine to install to]
sun4m"
which responds with:
"This system is only set up as a boot server for install clients.
Use -s to specify a path to an install server."
The two machines can see each other because snoop on the server
reveals:
"OLD-BROADCAST -> (broadcast) RARP C Who is [mac address]?"
Also if I let the client boot (from an existing version of solaris on
the hdd) I can telnet back and forth between them.
On the install target I get the message:
"Timeout waiting for ARP/RARP packet"
in response to:
"boot net -install"
What am I doing wrong ?
cheers
Iain
>On the install target I get the message:
>"Timeout waiting for ARP/RARP packet"
Check whether "/etc/ethers" is correct.
As I recall, it is a little fussy. You can use 1:2:3:4:0:5
but 01:02:03:04:00:05 will give the failures you are seeing.
Check if you have any unneeded leading zeros.
# ./add_install_client -i [ip add] -e [ether add] -s [server host
name]:/cdrom/cdrom0/s0 [client host name] sun4m
it looks like the install is starting, but after a little while the screen
fills with messages like:
devfsadmp: symlink failed for /tmp/dev/md/shared/1/dsk/d77 ->
../../../../../devices/pseudo/md@0:1,77,blk,:no space left on device
?????? eh ?
target machine is a SparcStation LX, 16mb, 500mb
Help !!
Iain
"IKerr" <i.b....@leeds.ac.uk> wrote in message
news:83462b5a.02121...@posting.google.com...
> I am trying to get solaris to install over a network (just connected
> by a hub, no routers etc).
> On the machine with the cdrom I have tried several different
> add_install_client permutations.
> For example:
> "./add_install_client -d -e [mac address of machine to install to]
> sun4m"
> which responds with:
> "This system is only set up as a boot server for install clients.
> Use -s to specify a path to an install server."
So export the cdrom (or install it locally) and do something like
./add_install_client -d -e xxxxx -s server:/cdrom/cdrom0/Solaris8 host sun4m
> On the install target I get the message:
> "Timeout waiting for ARP/RARP packet"
> in response to:
> "boot net -install"
> What am I doing wrong ?
#1 Above you meant "boot net - install", not "boot net -install".
#2 That string is a "classic" jumpstart using RARP, but your add install
client is specifing -d for DHCP instead. Perhaps you want to do a
dhcp boot instead.. "boot net:dhcp - install". Either that or ditch
the -d on the install string.
--
Darren Dunham ddu...@taos.com
Unix System Administrator Taos - The SysAdmin Company
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >
> # ./add_install_client -i [ip add] -e [ether add] -s [server host
> name]:/cdrom/cdrom0/s0 [client host name] sun4m
> it looks like the install is starting, but after a little while the screen
> fills with messages like:
> devfsadmp: symlink failed for /tmp/dev/md/shared/1/dsk/d77 ->
> ../../../../../devices/pseudo/md@0:1,77,blk,:no space left on device
Is your boot partition shared properly (with ro and anon=0)?
For starters you're not reading the messages that are coming off of
your system. Notice that you posted;
"This system is only set up as a boot server for install clients.
Use -s to specify a path to an install server."
You need an install server (hint: it can be the same machine with the
CD-ROM that is the "boot server"). Under SOLARIS, a "boot server" is
used to allow a machine to contact an "install server" that is on a
different subnet. Remember that the RARP packets are broadcast and
won't be routed through the gateway. It's a similar situation to
specifying an NIS server that is on a different subnet rather than using
broadcast. Since you say that the machines are on the same subnet, you
need to set the one with the CDROM up as an install server and not just
as a boot server.
Hope this helps,
Don
--
*************************** You a bounty hunter?
* Rev. Don McDonald, SCSA * Man's gotta earn a living.
* Baltimore, MD * Dying ain't much of a living, boy.
*************************** "Outlaw Josey Wales"
thanks for the responses !
/etc/ethers states
[ethernet] hostname of target machine
the add starts 8:0 - so no leading zero
/etc/hosts maps
IP targethost
On the target machine I have tried:
"boot net - install" (it was a typo in my posting)
and
"boot net:dhcp - install"
/etc/bootparams has only the following
[target hostname] root=[server
hostname]:/cdrom/multi_icd_sol_9_902_sparc/s0/Boot install=[server
hostname]:/cdrom/cdrom0/s0 boottype=:in rootopts=:rsize=32768
>Is your boot partition shared properly (with ro and anon=0)?
on the server ? I don't know, how do I find out ?
/etc/mnttab lists
/dev/dsk/c0t0d0s0 / ufs
rw,intr,largefiles,xattr,onerror=panic,suid,dev=2200000 1039690902
and
/vol/dev/dsk/c0t2d0/multi_icd_sol_9_902_sparc/s5
/cdrom/multi_icd_sol_9_902_sparc/s5 ufs
ro,intr,largefiles,xattr,onerror=panic,nosuid,dev=16c0006 1039690956
/vol/dev/dsk/c0t2d0/multi_icd_sol_9_902_sparc/s4
/cdrom/multi_icd_sol_9_902_sparc/s4 ufs
ro,intr,largefiles,xattr,onerror=panic,nosuid,dev=16c0005 1039690956
/vol/dev/dsk/c0t2d0/multi_icd_sol_9_902_sparc/s3
/cdrom/multi_icd_sol_9_902_sparc/s3 ufs
ro,intr,largefiles,xattr,onerror=panic,nosuid,dev=16c0004 1039690957
/vol/dev/dsk/c0t2d0/multi_icd_sol_9_902_sparc/s2
/cdrom/multi_icd_sol_9_902_sparc/s2 ufs
ro,intr,largefiles,xattr,onerror=panic,nosuid,dev=16c0003 1039690957
when booting on the target machine starts I get:
"20200"
SunOS Release 5.9 etc
*whoami: no domain name
arp -a does not list the target, so I add it with arp -s [ip add] [ethernet
add], then arp -a lists the host, but has changed the ip add for the
hostname as in /etc/hosts (mask is listed as 255.255.255.255 for all
addresses except 224.0.0.0 which has a netmask of 224.0.0.0
And now things get worse ! ;-(
This morning when I turned the server machine on it won't recognise the
solaris installation cd (although boot cdrom works fine). When I say 'won't
recognise' I mean that s0,s1 etc are empty.
If on the otherhand I insert on older cd though (sol 9 as opposed to sol
9/02) it is recognised AND there is a Tools directory (which there isn't on
my downloaded Sol 9/02 dir), and there is a setup_install_server bin, which
there isn't on the Sol 9/02 disk !!!! Both are downloads from Sun.com
Unfortunatly, when I originally downloaded solaris I only got the
Installation CD, not software 1 & 2.
Anway now I can run ./setup_install_server
and get
./setup_install_server /var/Solaris9
Verifying target directory...
Calculating the required disk space for the Solaris_9 product
Calculating space required for the installation boot image
Copying the CD image to disk...
Copying Install Boot Image hierarchy...
Install Server setup complete
Then I try:
# ./rm_install_client [hostname]
removing [hostname] from bootparams
removing /etc/bootparams, since it is empty
removing /tftpboot/inetboot.SUN4M.Solaris_9-1
removing /tftpboot
disabling tftp in /etc/inetd.conf
# ./add_install_client -i [client IP] -e [client ethernet] -s [server
hostname]:/var/Solaris9 [hostname] sun4m
making /tftpboot
enabling tftp in /etc/inetd.conf
updating /etc/bootparams
copying inetboot to /tftpboot
#
However, when I
boot net - install
from the target exactly the same happens as before:
devfsadmp: symlink failed for /tmp/dev/md/shared/1/dsk/d77 ->
../../../../../devices/pseudo/md@0:1,77,blk,:no space left on device
The cdrom light is flashing as though the client is booting from it as
opposed to the /var/Solaris9 directory, although if I cd
/var/solaris9/Solaris_9/Tools and do ./add_client etc then the target
machine does start to boot from the hdd, but it still comes up with a
screenful of errors as above and if they is allowed to continue there are
lots of complaints re /tmp/xyz, "not enough space", "can't create" etc
If I try boot net:dhcp - install nothing happens after the "20200" - I guess
the machine is waiting to be supplied an IP and it isn't getting one (the
"server" is just a frech w/s install with no name service like dns,nis etc).
Iain
"IKerr" <i.b....@leeds.ac.uk> wrote in message
news:83462b5a.02121...@posting.google.com...
>If on the otherhand I insert on older cd though (sol 9 as opposed to sol
>9/02) it is recognised AND there is a Tools directory (which there isn't on
>my downloaded Sol 9/02 dir), and there is a setup_install_server bin, which
>there isn't on the Sol 9/02 disk !!!! Both are downloads from Sun.com
>Unfortunatly, when I originally downloaded solaris I only got the
>Installation CD, not software 1 & 2.
You really want to have software 1 & 2 to properly setup an install
server.
>boot net - install
>from the target exactly the same happens as before:
>devfsadmp: symlink failed for /tmp/dev/md/shared/1/dsk/d77 ->
>../../../../../devices/pseudo/md@0:1,77,blk,:no space left on device
You got a long way: it got the tfp file and booted the kernel; it
is running devfsadm.
How much memory does the system have?
Casper
--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.
I only need a core install + sunscreen.
> How much memory does the system have?
16 mb ;-(
I have been running Sol 8 installed via external cd (which I don't have
access to) on this machine with CDE, okay not the fastest, but it did all I
needed.
What puzzles me is why setup_install_server is on Sol 9 & not Sol 9/02 (does
sol 9 incorporate the functionality in add_install_client?). I do have
Software 1 & 2 for the Sol 9/02 release, but when I booted off 9 Install on
the Ultra 10 it wouldn't accept Software 1 & 2, so I had to download Sol
9/02 Install as well.
Someone mentioned sharing, from the info I provided can you tell whether
everything is as it should be as there are lots of complaints about mkdir
/tmp/dev/md/shared/2/dsk/rdsk (or dsk) 0x1ed "no space left on device"
and also /devices/pseudo/md@0:3,53,blk. max attempts exceeded
Iain
A message that was there before (I think) but I didn't post (there are
screenfuls of this stuff) was:
WARNING: tmp_memalloc:tmpfs over memory limit
This is still there after increasing the ram.
Iain
>> How much memory does the system have?
>16 mb ;-(
That is likely insufficient for the Solaris 9 kernel.
>What puzzles me is why setup_install_server is on Sol 9 & not Sol 9/02 (does
>sol 9 incorporate the functionality in add_install_client?). I do have
>Software 1 & 2 for the Sol 9/02 release, but when I booted off 9 Install on
>the Ultra 10 it wouldn't accept Software 1 & 2, so I had to download Sol
>9/02 Install as well.
Strange; Software 1of2 has the lowest overhead with installs.
>Someone mentioned sharing, from the info I provided can you tell whether
>everything is as it should be as there are lots of complaints about mkdir
>/tmp/dev/md/shared/2/dsk/rdsk (or dsk) 0x1ed "no space left on device"
>and also /devices/pseudo/md@0:3,53,blk. max attempts exceeded
You could try to exclude some devices in the /etc/system on the
install server; that may enable you to reclaim sufficient memory
to make it to the "swap mount".
Casper
Try setting tmpfs_minfree even lower; and perhaps kill the swap
reserve as well.
errm, would some kind soul hold my hand one this one :-)
I have no idea whatsoever on how to accomplish the above suggestions. As to
the previous post on /etc/services
which /etc/services was meant:
/etc/services or /var/Solaris9/Solaris_9/Tools/Boot/etc/services
I commented out a few lines (see below) in the latter and tried boot net -
install, but there was no change:
I don't know which I can safely comment out for the purposes of a network
install.
thanks
Iain
#ident "@(#)services 1.32 01/11/21 SMI"
#
#
# Copyright (c) 1999-2001 by Sun Microsystems, Inc.
# All rights reserved.
#
# Network services, Internet style
#
tcpmux 1/tcp
echo 7/tcp
echo 7/udp
discard 9/tcp sink null
discard 9/udp sink null
systat 11/tcp users
daytime 13/tcp
daytime 13/udp
netstat 15/tcp
chargen 19/tcp ttytst source
chargen 19/udp ttytst source
ftp-data 20/tcp
ftp 21/tcp
#ssh 22/tcp # Secure Shell
telnet 23/tcp
#smtp 25/tcp mail
#time 37/tcp timserver
#time 37/udp timserver
#name 42/udp nameserver
#whois 43/tcp nicname # usually to sri-nic
domain 53/udp
domain 53/tcp
bootps 67/udp # BOOTP/DHCP server
bootpc 68/udp # BOOTP/DHCP client
#kerberos 88/udp kdc # Kerberos V5 KDC
#kerberos 88/tcp kdc # Kerberos V5 KDC
hostnames 101/tcp hostname # usually to sri-nic
#pop2 109/tcp pop-2 # Post Office Protocol - V2
#pop3 110/tcp # Post Office Protocol - Version 3
sunrpc 111/udp rpcbind
sunrpc 111/tcp rpcbind
#imap 143/tcp imap2 # Internet Mail Access Protocol v2
#ldap 389/tcp # Lightweight Directory Access Protocol
#ldap 389/udp # Lightweight Directory Access Protocol
submission 587/tcp # Mail Message Submission
submission 587/udp # see RFC 2476
#ldaps 636/tcp # LDAP protocol over TLS/SSL (was sldap)
#ldaps 636/udp # LDAP protocol over TLS/SSL (was sldap)
#
# Host specific functions
#
tftp 69/udp
rje 77/tcp
#finger 79/tcp
link 87/tcp ttylink
supdup 95/tcp
#iso-tsap 102/tcp
#x400 103/tcp # ISO Mail
#x400-snd 104/tcp
csnet-ns 105/tcp
#pop-2 109/tcp # Post Office
uucp-path 117/tcp
#nntp 119/tcp usenet # Network News Transfer
#ntp 123/tcp # Network Time Protocol
#ntp 123/udp # Network Time Protocol
#netbios-ns 137/tcp # NETBIOS Name Service
#netbios-ns 137/udp # NETBIOS Name Service
#netbios-dgm 138/tcp # NETBIOS Datagram Service
#netbios-dgm 138/udp # NETBIOS Datagram Service
#netbios-ssn 139/tcp # NETBIOS Session Service
#netbios-ssn 139/udp # NETBIOS Session Service
#NeWS 144/tcp news # Window System
slp 427/tcp slp # Service Location Protocol, V2
slp 427/udp slp # Service Location Protocol,
V2
#mobile-ip 434/udp mobile-ip # Mobile-IP
cvc_hostd 442/tcp # Network Console
ike 500/udp ike # Internet Key Exchange
uuidgen 697/tcp # UUID Generator
uuidgen 697/udp # UUID Generator
#
# UNIX specific services
#
# these are NOT officially assigned
#
exec 512/tcp
login 513/tcp
shell 514/tcp cmd # no passwords used
#printer 515/tcp spooler # line printer spooler
#courier 530/tcp rpc # experimental
#uucp 540/tcp uucpd # uucp daemon
biff 512/udp comsat
who 513/udp whod
syslog 514/udp
talk 517/udp
route 520/udp router routed
ripng 521/udp
#klogin 543/tcp # Kerberos authenticated rlogin
#kshell 544/tcp cmd # Kerberos authenticated remote shell
new-rwho 550/udp new-who # experimental
rmonitor 560/udp rmonitord # experimental
monitor 561/udp # experimental
pcserver 600/tcp # ECD Integrated PC board srvr
sun-dr 665/tcp # Remote Dynamic Reconfiguration
#kerberos-adm 749/tcp # Kerberos V5 Administration
#kerberos-adm 749/udp # Kerberos V5 Administration
#kerberos-iv 750/udp # Kerberos V4 key server
#krb5_prop 754/tcp # Kerberos V5 KDC propogation
ufsd 1008/tcp ufsd # UFS-aware server
ufsd 1008/udp ufsd
cvc 1495/tcp # Network Console
ingreslock 1524/tcp
#www-ldap-gw 1760/tcp # HTTP to LDAP gateway
#www-ldap-gw 1760/udp # HTTP to LDAP gateway
listen 2766/tcp # System V listener port
nfsd 2049/udp nfs # NFS server daemon (clts)
nfsd 2049/tcp nfs # NFS server daemon (cots)
eklogin 2105/tcp # Kerberos encrypted rlogin
lockd 4045/udp # NFS lock daemon/manager
lockd 4045/tcp
dtspc 6112/tcp # CDE subprocess control
fs 7100/tcp # Font server
>> Try setting tmpfs_minfree even lower; and perhaps kill the swap
>> reserve as well.
>errm, would some kind soul hold my hand one this one :-)
Apparently these are already fairly low in the standard /etc/system
set tmpfs:tmpfs_minfree=1
set swapfs_minfree=0x040
>I have no idea whatsoever on how to accomplish the above suggestions. As to
>the previous post on /etc/services
>which /etc/services was meant:
>/etc/services or /var/Solaris9/Solaris_9/Tools/Boot/etc/services
The etc/system under Tools/Boot can be used to exclude device
drivers such as "md" which would cut down on the number of device
entries made on /tmp/
thanks for all your help.
set tmpfs:tmpfs_minfree=1
set swapfs_minfree=0x040
were already in etc/system
but couldn't see "md" listed there or in /services
I also tried the above "sets" at ok> bit got the following "Memory Address
not Aligned"
I will remove a few other entries in /services and see if that makes any
difference.
The system file is copied below, but it looks like everything but 4 lines
are commented
Iain
ident "@(#)system 1.18 97/06/27 SMI" /* SVR4 1.5 */
*
* SYSTEM SPECIFICATION FILE
*
* moddir:
*
* Set the search path for modules. This has a format similar to the
* csh path variable. If the module isn't found in the first directory
* it tries the second and so on. The default is /kernel /usr/kernel
*
* Example:
* moddir: /kernel /usr/kernel /other/modules
* root device and root filesystem configuration:
*
* The following may be used to override the defaults provided by
* the boot program:
*
* rootfs: Set the filesystem type of the root.
*
* rootdev: Set the root device. This should be a fully
* expanded physical pathname. The default is the
* physical pathname of the device where the boot
* program resides. The physical pathname is
* highly platform and configuration dependent.
*
* Example:
* rootfs:ufs
* rootdev:/sbus@1,f8000000/esp@0,800000/sd@3,0:a
*
* (Swap device configuration should be specified in /etc/vfstab.)
* exclude:
*
* Modules appearing in the moddir path which are NOT to be loaded,
* even if referenced. Note that `exclude' accepts either a module name,
* or a filename which includes the directory.
*
* Examples:
* exclude: win
* exclude: sys/shmsys
* forceload:
*
* Cause these modules to be loaded at boot time, (just before mounting
* the root filesystem) rather than at first reference. Note that
* forceload expects a filename which includes the directory. Also
* note that loading a module does not necessarily imply that it will
* be installed.
*
* Example:
* forceload: drv/foo
* set:
*
* Set an integer variable in the kernel or a module to a new value.
* This facility should be used with caution. See system(4).
*
* Examples:
*
* To set variables in 'unix':
*
* set nautopush=32
* set maxusers=40
*
* To set a variable named 'debug' in the module named 'test_module'
*
* set test_module:debug = 0x13
*
* Values set for install boottime environment
*
set scsi_options=0x58
set scsi_reset_delay=10000
/var/Solaris9/Solaris_9/Tools/Boot/etc/services
Still no joy. So I tried ./rm_install_client and ./setup_install_server
again from Sol 9/02 Software disk 1
and booted the LX with boot net - nowin install
No joy.
When I used ./add_client etc
I did get this though, is it relevant, someone mentioned way up the thread
about sharing ?
Adding "share -F nfs -o ro,anon=0 /export/sol9" to /etc/dfs/dfstab
share_nfs: /cdrom/multi_icd_sol_9_902_sparc/s0: No such file or directory
share_nfs: /cdrom/multi_icd_sol_9_902_sparc/s1: No such file or directory
share_nfs: /cdrom/sol_9_902_sparc/s0/Solaris_9/Tools: parent-directory
(/cdrom/sol_9_902_sparc/s0) already shared
share_nfs: /var/Solaris9: No such file or directory
making /tftpboot
enabling tftp in /etc/inetd.conf
updating /etc/bootparams
copying inetboot to /tftpboot
still no joy, so have we got to the conclusion that an LX with 24 mb ram
can't boot over the net, and only a ram upgrade / local cdrom will get me
sol 9 on this machine ?
Iain
message news:3df8e4e6$0$11742$e4fe...@news.xs4all.nl...
>but couldn't see "md" listed there or in /services
They're not listed; you'd need to add entries like:
exclude: drv/md
etc for all drivers you do not need during install of the specific
system; that way you may be able to get to "add swap" w/o running out
of memory.
Casper
I searched the newsgroups and found references to some things I could
exclude, bunged them in to /etc/system, but still no luck (not sure exactly
what can/not be excluded). I borrowed an external cdrom and booted off the
install cd. I get mostly the same messages, although I do get a prompt
asking which language the install should use. I make a selection and there
are a load of other errors and the prompt just returns to the language
prompt. So I guess I am on the lookout for some more ram !
thanks
for all the help!
Iain
"Casper H.S. Dik" <Caspe...@Sun.COM> wrote in message
news:3df8e4e6$0$11742$e4fe...@news.xs4all.nl...