Thursday, May 19, 2005

Creating a Solaris 10 x86 jumpstart server on a Netra t1 running Solaris 9

Message: 5
Date: Wed, 18 May 2005 15:35:21 +0100
From: Loris Serena
Content-Type: text/plain; charset="us-ascii"

Thank you very much to

Chad Mynhier
Dana Sparling
Bill Williams

whose replies (below) have shed a good technical light on the issue.

The way I got this working though is slightly different and not as elegant,
I'm afraid.
(or, in plain English, a quick and dirty trick!)

As far as I could see, on the Solaris 10 x86 cd 1of4 there is no Boot
information, either as a directory or as a ufs filesystem.

# prtvtoc /dev/rdsk/c1t2d0s2
* /dev/rdsk/c1t2d0s2 partition map
*
* Dimensions:
* 512 bytes/sector
* 35632 sectors/track
* 1 tracks/cylinder
* 35632 sectors/cylinder
* 1 cylinders
* 1 accessible cylinders
*
* Flags:
* 1: unmountable
* 10: read-only
*
* Unallocated space:
* First Sector Last
* Sector Count Sector
* 1215280 18446744073708336336 18446744073709551615
*
* First Sector Last
* Partition Tag Flags Sector Count Sector Mount Directory
0 0 00 0 1215280 1215279
2 0 00 0 1215280 1215279 /cdrom
#

So, I put the Solaris 10 x86 DVD into my wintel laptop, gzipped the Boot
directory, scp-ed Boot.zip across onto my Netra t1 and unzipped it into
/jsboot .

Then on the Netra, mounted the Solaris 10 x86 cd 1of4, cd into
/cdrom/Solaris_10/Tools and ran
./setup_install_server -t /jsboot/Boot /export/install/sol10x86

Et voil`, job done! ;-)
(plus running the add_to_install_server from cd 2/3/4 of course)

Cheers

Loris

------ Chad's email ----------------------

The first cd (1 of 4) contains two filesystems, an hsfs filesystem and a ufs
filesystem, this latter being the /cdrom/Solaris_10/Tools/Boot subtree. You
can't mount an x86 ufs filesystem on SPARC and vice versa because of
byte-endian issues.

The only real solution is to install Solaris x86 onto an x86 server directly
from CD, set up jumpstart on the x86 server, and then use rsync to copy the
jumpstart setup to the Netra.

Note: When copying the jumpstart setup, rsync is the tool to use. Using a
simple tar pipe or even rdist won't work, you won't be able to boot off this
image. Rsync will do the right thing with all of the special files.

Chad Mynhier
------------------------------------------

------ Dana's email ----------------------
I had a similar problem when I setup my Solaris 9 jumpstart box.
I believe the information you need is on slice 1, so you need to mount it
and use the -t option to point to it.
This is what I did:
Mount the cd
# mount -r -F hsfs /dev/dsk/c0t6d0s0 /mnt
Make slice1 mountable and mount it:
# lofiadm -a /dev/dsk/c0t6d0s1 /dev/lofi/1
# mkdir /s1
# mount -o ro /dev/lofi/1 /s1
# cd /mnt/Solaris_9/Tools
# ./setup_install_server -t /mnt/export/install/sparc9
Unmount and delete /dev/lofi/1 when you are finished:
# umount /s1
# lofiadm -d /dev/lofi/l
# rmdir s1

Your mileage may vary, or solaris 10 might be completely different.
Bayly Eley has written an interesting document on jumpstart, and it can be
found at:
http://www.giac.org/certified_professionals/practicals/gcux/0263.php
I hope this helps.
------------------------------------------

------ Bill's email ----------------------
Hi Loris,

I don't have a Netra, but I'm guessing it's a sparc platform rather than an
x86. Assuming that to be true ...

I don't have Solaris10, but do run Solaris9 and have been playing around
with the cross-platform jumpstart. My remarks are all based on Solaris9
(4/03) SPARC and X86; however, I suspect that the requirement holds true for
Solaris10.

In the case of Solaris9 (and prior releases I think)
It seems that the trick is that you must mount the 1st installation CD on
its NATIVE platform.
In my case I have an Sol9 x86 that I want to use to jumpstart SunFire
(SPARC) machines. I had to do this:

SPARC: (we'll call it SPARCSYSTEM)
# Insert the Sol9 CD1 (of 2) and let it mount (volcheck).
share -F nfs -o ro,anon=0 /cdrom/cdrom0/s0
share -F nfs -o ro,anon=0 /cdrom/cdrom0/s1

X86:
mkdir /tmp/s0 /tmp/s1
mount SPARCSYSTEM:/cdrom/cdrom0/s0 /tmp/s0
mount SPARCSYSTEM:/cdrom/cdrom0/s1 /tmp/s1

cd /tmp/s0/Solaris_9/Tools
# Just like it says in the book:
./setup_install_server -t /tmp/s1 /export/sparc9install

# Finishes...
cd /tmp
umount /tmp/s0
umount /tmp/s1

SPARC:
unshare /cdrom/cdrom0/s0
unshare /cdrom/cdrom0/s1
eject

All this is pretty much right out of the Solaris 9 Installation Guide (IG).
The IG then goes on to describe mounting (Sol9, remember) the SPARC CD2 of 2
directly on the x86 system and finishing up by adding the rest of the
installation software right there on the x86:
./add_to_install_server /export/sparc9install

Mr. Paranoid, here, did it -- SPARC mount, install from NFS -- just like
CD1.

I have read various remarks (opinions?) about *why* you have to mount/run
the CD1 from the native platform; suffice it to say that the consistant
opinion seems to be that you DO have to mount the Sol9 CD1 on it's NATIVE
architecture.

One more thing (Sol9):
You WILL have to mount the CD1 and export it from SPARC, then
mount and run setup_install_server from x86.
I (foolishly) tried to export the x86 install area
(sparc9install) and do the mount and setup_install_server on
the SPARC.
Guess what: setup_install_server will not accept an NFS as the
installation target.

Hope some of this helps.
---------------------------------------------

-----Original Message-----
From: Loris Serena
Sent: 18 May 2005 11:28

Subject: Creating a Solaris 10 x86 jumpstart server on a Netra t1 running
Solaris 9.

Sunmanagers,

I have a Netra t1 (with a cdrom, not a dvd) running Solaris 9 which I've
been tasked to build as a jumpstart server for Solaris 10 x86.

I've mounted Solaris 10 x86 cd 1of4, cd into /cdrom/Solaris_10/Tools and run
the following:

# ./setup_install_server /export/install/sol10x86
ERROR: Install boot image /cdrom/Solaris_10/Tools/Boot does not exist
Check that boot image exists, or use [-t] to
specify a valid boot image elsewhere.
#

Has anyone found a way around this or can point me to the right direction?

Thanks in advance

Loris

0 Comments:

Post a Comment

<< Home