t UNIX is a registered trademark of AT&T.
Revision A of 20 May 1988
2.4. Loading and Booting the Exec
Before Booting
Halting the System
Unless you boot from tape, the Exec loads its programs from UNIX files located on a hard disk. Although the files can be in any directory, we strongly urge you to keep them in the / stand directory. This document will assume the Exec and its diagnostic programs are all in / stand.
The Exec cannot run unless the system has a minimum amount of functional hardware. The Exec depends on the system tests built into the boot PROMs to ensure the machine is minimumly functional. If you power up the workstation in DIAG mode and the PROM selftest prints out error messages on the attached ter-minal, the machine is not working well enough to test.
The Exec must be booted from the PROM monitor. To reach monitor mode, you must halt the operating system. This can be done a number of ways. The best way is ~ use the UNIX halt command. To run it, do the following:
be sure to shut down all your applicalions first!
example% au
Pa ssword : enter password exampletaync
Another, less preferable way of shutting down the system and bringing up the PROM monitor is to abort the system. Don't do this unless your you have NO OTHER ALTERNATIVE; aborting the operating system may damage your file systems. To abort, hold down the key on the upper left-hand comer of the key-board (usually (IIJ ) and press
W.
Do this IMMEDIATELY following theTesting _Megabytes of memory . . . . Completed message.
You should see the PROM monitor prompt, >.
Once you are in the monitor, you should reset the system to clear out all of the hardware settings. Do the following:
> 9 0 panic: zero
Syncing disks •.. done
press L1 and A again when the message above finishes dumping to dev XXX, offset XXXXX
Booting from Tape
Installing the Exec
lusrlstand
Installing a boot block
NOTE If you are booting the Execfrom a SCSI disk or tape, you must cycle the power before booting. Follow the directions to halt your system, turn the power OFF, then ON, then IMMEDIATELY abort the boot using Ll-a, as described above.
Now enter k2 to ensure that the system hardware is reset, in case the operating system began to boot before you aborted.
Now your system is ready to boot the Exec.
If you don't have the Exec installed on disk, you can boot it directly off the Exec Tape. Halt your system as previously described, perform a k2 reset, then type the following to the PROM monitor:
> b at (, ,N) N is 0 for Sun-2 or 1 for Sun-3 boot: at (, , 5)
Be' sure to follow the format shown above. The Exec booting syntax differs from
that ofL'1e SunOS syntax, so
besure and enter the command exactly as shown.
Do not leave parentheses off. The k 2 reset ensures that the operating system does not remain in memory anywhere on the CPU or memory boards.
At this point the Exec should boot up and display the Main Menu.
If you don't want to load the Exec from tape each time you run it, you must install it in a UNIX directory.
The Exec and its associated files require approximately 2 Mbytes of disk space.
On many systems, the default root partition is not large enough for this. If this is the case, the Exec may be installed in lusr/stand instead of /stand. To do this, fol-low the installation procedure befol-low, but use the directory lusr I stand instead of I stand.
If you want to boot the Exec directly from /usr/stand, bootblocks must be installed on the lusr partition. Otherwise, the -a option must be used to boot the Exec. Ifbootblocks are installed, perform a k2 reset from the PROM monitor mode, then boot the Exec with:
>b device (, , 6) standi exec
If bootblocks are not installed, boot the Exec with:
>b -a
Boot:device(O,O,O)vrnunix Load:device(O,O,O)vrnunix Boot: device (, , 6) standi exec
Where device is the type of disk the Exec is installed on.
If you have the Exec in /usr/stand, and you want to boot it directly, you must install a boot block in the /usr partition. To do this, use the following sequence:
~\sun
~~ microsystems Revision A of 20 May 1988SeNers vs Local Disk and Tape
Local Disk and Tape
server
% au
Password: enter super-user password
• cd /uar/mdec
# installboot bootdisk / dey / rpartition
• cp /boot /usr
disk is the disk controller type and partition is the disk partition /usr is on; it is usually 0 g for the first disk, g partition.
For example, installing a bootblock on the g partition of disk 0:
# installboot bootxy /dev/rxyOq
# cp /boot /usr
There are two logical places to install the Exec: on the local disk of the system you want to test (if you don't plan to download it), or on a seNer from which you want to remotely download the Exec.
To install the Exec on the test system, first detennine whether it is a Sun-2 or a Sun-3. Look at the model number on the workstation to detennine this. If you aren't sure, ask your system administrator.
Loading the Exec from tape is the same for Sun-2s and Sun-3s. First you must load the file called extract_exec into the / stand directory. The example below applies to 1/2-inch tapes. For 1/4-inch tapes, substitute st for mt in the examples below. Do the following:
example% au
Password: enter super user (root) password example. cd /atand
example. mt -t /dev/n~O rewind example. mt -t /dev/nrmtO faf 3 example. tar xvf /dev/nrmtO
Once extract_exec is on the disk, run it by doing the following:
example. extract_exec mtO you will see a number of messages here ..
example. exit example%
All of the files on the tape should now be copied onto / stand.
Installing a seNer with the Exec is a little more involved. First, go to the / (root) directory of the server. When the Exec boots from / stand on a server, it is really booting from /pub/ stand, which can be either
/pub .MC68010/ stand (Sun-2) or /pub. MC68020/ stand (Sun-3). Use these pathnames to put the files in the right place.
Put the Exec and the Diagnostics in both /pub .MC68 01 0 / stand and /pub.MC68020/stand .
• \sun
~~ microsystems Revision A of 20 May 1988Remote Tape
Booting from Disk
If your seIVer is homogeneous, it will only have one of the two pub directories.
Put the Exec and diagnostics into that directory.
Loading the Exec from tape is the same for Sun-2s and Sun-3s. First you must load the file called extract_exec into the /pub.MC680XO/stand (X is 1 or 2) directory. Do the following, using at for SCSI tape and mt for l/2-inch tape:
example% au
Password: enJer superuser (root) password example. cd /atand
example.
me
- f /dev/nr~O rewind example#me
- f /dav/nrstO faf 3 example# tar xvf /dev/nrstOOnce
extract exec is on the disk, run it by doing the following:examplet extract_exec ~o
you will see a number of messages here ..
example# exit example%
All of the files on the tape should now be copied onto / stand.
If you are using a remote tape drive to install the SunDiagnostic Executive onto disk, the rpc . rexd daemon must be running on the remote device. If it is not, you will see the error message:
cannot connect to server
Refer to REXD (8C) in the SunOS Reference Manual ("man" pages).
Use this sequence to perfonn the remote tape installation. You may want to read the entry in the SunOS Reference Manual for the on command, prior to using