Installation

Once the system has finished booting, it will automatically run the installation script, /iss/bin/jaz_install. This script is the main ISS setup script for creating and installing Jaz distribution disks, creating Jaz data disks, and backing up workstations to Jaz disks. Press Enter to continue with the installation.

The script searches through the SCSI disk devices to detect the two system disk devices and the external Jaz device. While searching it prints Searching for disks..., and when finished displays the device names and their types:

Jaz disk:    c0t4d0 (Jaz 2GB)
First disk:  c0t3d0 (SUN0535)
Second disk: c0t1d0 (SUN1.05)

In the device name c0t3d0, the SCSI target ID is the number following the letter t. For most of the ISS workstations, the target ID numbers will be the same as in the above example. The Jaz disk has ID 4, while the smaller internal disk (root filesystem and swap partition) has ID 3 and the larger disk (/u2 filesystem) has ID 0.

The script will notice that the root filesystem is being mounted from the Jaz drive and conclude that this must be an installation onto the internal workstation disks.

----- Installing an ISS system from the Jaz disk...

The jaz_install script provides the option of just configuring an existing installation, instead of erasing the internal disks and copying all of the files from scratch. Just press return to accept the default of performing a normal, full installation.

If the ISS system only needs to be configured, enter
'config' here, else press <enter> to continue with installation.

Next, the script wants to know whether this should be a complete restoration of a previous backup.

This script can generate only what is needed for ISS installations,
or it can generate a full copy of the source system.
The only difference is that a full copy will contain all of the
directories in /u2, including data and spooling, and not just the
/u2/local directory.
Do you want a full copy (y/n)? [y]

For most initial installations, the only directory which needs to be copied into the /u2 filesystem from the distribution disk is the local directory, which contains programs and utilities not provided by the base Solaris system. The rest of the /u2 filesystem only contains data, log files, and other temporary files which are not necessary for the ISS system to begin running and collecting data. In most cases a full copy will not be necessary, and it could take longer if there are many data files.

Each of the two system disks must be prepared before copying the ISS system onto them. The script guides the disk preparation through three steps: low-level formatting, partition labelling, and finally filesystem creation. Before attempting the low-level format, the disk is polled with the Solaris format command:

Polling disk with Solaris format:
selecting c0t3d0
[disk formatted]
Current Disk = c0t3d0

If the poll shows [disk formatted], then the disk does not need to be low-level formatted again. This is a good thing because formatting can take on the order of an hour. Low-level formatting has never been needed yet, so the option to low-level format will not be enabled unless the format option was passed on the jaz_install command line.

Low-level formatting might be desirable when a disk is suspected of having surface errors or bad sectors. Brand new Jaz disks might need low-level formatting if the format command does not recognize them as having been formatted. If the low-level format option is enabled with the format command-line flag, the script will prompt before formatting:

About to low-level format drive SUN0535!
Low-level formatting is not necessary if the disk is
shown above as already formatted.
(f)ormat disk, (s)kip the low-level format, or (a)bort? (f/s/a):

The next steps in disk preparation are partitioning and file system creation. If the disk was not low-level formatted, then the partitioning will be the first step which actually erases the destination disk. Therefore the script gives one last chance to be interrupted before losing all the information on the disk:

___________________________________________________________________
Partitioning destination disk c0t3d0 (SUN0535)

Press <enter> to partition the disk.  This will erase it...

The partitioning is immediately followed by the creation of a new filesystem.

___________________________________________________________________
Creating ufs filesystem on partition c0t3d0s0...

Remember that each of the disk preparation steps, formatting, partitioning, and filesystem creation, will be done for each of the internal disks. Once those steps have been completed, the script will immediately beginning copying files from the Jaz distribution disk to the workstation internal disks.[1] The copying takes from 30 minutes to an hour.

Once the copy has finished, directories and file permissions must be set up on the workstation disks, especially in /u2, if the directories besides local were not restored with the full copy option.

Eventually jaz_install will install a boot block onto the root filesystem disk so the workstation can boot from its internal disk.

Installing boot block onto c0t3d0s0...

Now that the ISS software has been installed onto the workstation disks, it must be configured. At this point, the jaz_install script runs the iss_config script in /iss/bin/iss_config. See the chapter on Configuration to step through the configuration process.

Caution

The monitor usually enters energy-saving sleep mode before the file copying completes. When resuming an installation where the monitor is dark, do not press the Enter key to awaken the monitor, since the installation process may have already begun the configuration script. Instead, just press space or shift.

Notes

[1]

The copying is done by piping a ufsdump of the Jaz filesystem into a ufsrestore on the mounted internal disks.