From: hume.spamfilter on
syd_p <sydneypuente(a)yahoo.com> wrote:
> specific version = 10 Update 8 (10/09)

I don't have any spare SPARC machines around here to experiment with (and
it's looking like I won't have any more, the more I'm hearing from Oracle)
so I'm not able to set up a test environment to try to duplicate this.

I strongly suspect that your machine isn't able to find that sparc.miniroot,
but I don't know how to tell it where to find it, especially since you
appear to be using RARP instead of DHCP to boot the client.

--
Brandon Hume - hume -> BOFH.Ca, http://WWW.BOFH.Ca/
From: syd_p on
On 26 Mar, 14:10, hume.spamfil...(a)bofh.ca wrote:
> syd_p <sydneypue...(a)yahoo.com> wrote:
> > specific version = 10 Update 8 (10/09)
>
> I don't have any spare SPARC machines around here to experiment with (and
> it's looking like I won't have any more, the more I'm hearing from Oracle)
> so I'm not able to set up a test environment to try to duplicate this.
>
> I strongly suspect that your machine isn't able to find that sparc.miniroot,
> but I don't know how to tell it where to find it, especially since you
> appear to be using RARP instead of DHCP to boot the client.
>
> --
> Brandon Hume    - hume -> BOFH.Ca,http://WWW.BOFH.Ca/
Well there is a boot_file available to the client via nfs. see below.
I have started again and /jumpstart dir is correctly spelled now.
I should mention that all I want to do is to have sparc clients boot
up over the network from the jumpstart server,
ideally read from a sysidcfg file and the I am quite happy to type in
the location of an nfs exported iso image.

mount -F nfs 192.168.15.42:/jumpstart/Solaris_10/Tools/Boot /mnt/boot
cd platform/sun4u
bash-3.00# ls -lrt
total 703650
-rw-r--r-- 1 root sys 71808 Oct 3 2008 bootlst
-rw-r--r-- 1 root sys 79976 Oct 3 2008 cprboot
-rw-r--r-- 1 root sys 1088576 Sep 15 2009 wanboot
drwxr-xr-x 4 root bin 512 Feb 13 23:39 lib
drwxr-xr-x 12 root sys 512 Feb 13 23:39 kernel
drwxr-xr-x 2 root bin 512 Feb 13 23:39 sbin
-rw-r--r-- 3 root root 186777600 Feb 13 23:41 failsafe
-rw-r--r-- 1 root root 172032000 Feb 13 23:43 boot_archive

From: hume.spamfilter on
syd_p <sydneypuente(a)yahoo.com> wrote:
> Well there is a boot_file available to the client via nfs. see below.
> I have started again and /jumpstart dir is correctly spelled now.

The question is whether or not the client even bothers trying NFS. I know
x86 clients will fetch their miniroot via TFTP, *not* NFS. Someone more
familiar with netbooting a SPARC using U8 than I will have to answer this.
I've tried experimenting with an LDOM, but I think I'm running into a bug
in the firmware.

--
Brandon Hume - hume -> BOFH.Ca, http://WWW.BOFH.Ca/
From: Victor on
On Mar 24, 12:00 pm, syd_p <sydneypue...(a)yahoo.com> wrote:
> Hi,
> I have installed a Solaris 10 jumpstart server on a Sun Blade.
> ./setup_install_server /jumstart (yes a missing p)
>
> ./add_install_client -i 192.168.15.40 -e xx:xx:xx:xx:xx:xx -s
> 192.168.15.42:/jumstart -p 192.168.15.42:/jumstart arthur sun4u
>
> and try to boot the client:
>
> boot net -v
> Internet address is: 192.168.15.40
> hostname arthur
> Found 192.168.15.42 @ xx:xx:xx:xx:xx
> root server : edward (192.168.15.42)
> root directory:/jumstart/Solaris_10/Tools/Boot
> cannot open neither boot_archive nor miniroot
>
> Not quite sure how to investigate this error?
>
> all looks OK?
>
> -bash-3.00$ grep arthur bootparams
> arthur  root=edward:/jumstart/Solaris_10/Tools/Boot
> install=192.168.15.42:/jumst
> art/ boottype=:in sysid_config=192.168.15.42:/jumstart/
> rootopts=:rsize=8192
>
> Please help if you can!
>
> Syd

You need to specify Config server where rules file is located.
../add_install_client -i 192.168.15.40 -e xx:xx:xx:xx:xx:xx -s
192.168.15.42:/jumstart -p 192.168.15.42:/jumstart -c 192.168.15.42:/
jumstart arthur sun4u

Victor
From: Victor on
On Mar 30, 2:52 pm, Victor <victorfeng1...(a)yahoo.com> wrote:
> On Mar 24, 12:00 pm, syd_p <sydneypue...(a)yahoo.com> wrote:
>
>
>
>
>
> > Hi,
> > I have installed a Solaris 10 jumpstart server on a Sun Blade.
> > ./setup_install_server /jumstart (yes a missing p)
>
> > ./add_install_client -i 192.168.15.40 -e xx:xx:xx:xx:xx:xx -s
> > 192.168.15.42:/jumstart -p 192.168.15.42:/jumstart arthur sun4u
>
> > and try to boot the client:
>
> > boot net -v
> > Internet address is: 192.168.15.40
> > hostname arthur
> > Found 192.168.15.42 @ xx:xx:xx:xx:xx
> > root server : edward (192.168.15.42)
> > root directory:/jumstart/Solaris_10/Tools/Boot
> > cannot open neither boot_archive nor miniroot
>
> > Not quite sure how to investigate this error?
>
> > all looks OK?
>
> > -bash-3.00$ grep arthur bootparams
> > arthur  root=edward:/jumstart/Solaris_10/Tools/Boot
> > install=192.168.15.42:/jumst
> > art/ boottype=:in sysid_config=192.168.15.42:/jumstart/
> > rootopts=:rsize=8192
>
> > Please help if you can!
>
> > Syd
>
> You need to specify Config server where rules file is located.
> ./add_install_client -i 192.168.15.40 -e xx:xx:xx:xx:xx:xx -s
> 192.168.15.42:/jumstart -p 192.168.15.42:/jumstart -c 192.168.15.42:/
> jumstart arthur sun4u
>
> Victor- Hide quoted text -
>
> - Show quoted text -

One time I set up a Sol 9 Jumpstart server, and -s, -p, -c had the
same location. The error was different from yours.

Victor