Booting the New Installation

Once the workstation has been configured, the jaz_install script will attempt to reboot the system:

The newly installed system can now be booted for operation.

If you must reboot later instead of now, 
use this command (as root): reboot -- -r

After reboot, you will be prompted to exchange the system
distribution disk with a data disk in the Jaz drive.
Do not leave before that!
After this reboot, subsequent reboots will start
automatically and accept the current Jaz disk as a data disk.

Are you ready to reboot? (y/n)

Enter y to continue with the reboot. If a log of the installation was successfully created, there will be a message about the log file being copied to /mnt/log/jaz_install.log. Once the system has been rebooted, this file will be in /log. The file should contain a transcript of the installation; it can be examined for details or possible errors.

After the first initial installation, the ISS system will not start before making sure that a system disk has not been left in the Jaz drive. Before beginning normal operation, the system disk should be replaced with a data disk. The startup asks whether a data disk needs to be created:

Do you need to create a new data disk? (y/n)

If a new data disk is needed, enter y. This will run jaz_install data and step through the process of creating a data disk. [1]

Eventually, a prompt appears for the last chance to insert a data disk.


Please insert a DATA DISK into the Jaz drive...
Press <enter> once a DATA DISK has been inserted:

Press enter and the ISS system will start normal realtime operation. All subsequent reboots, either manual or accidental, will proceed immediately to starting and running the realtime system. Whatever disk is loaded in the Jaz drive at boot time will be mounted and treated as a data disk. A system distribution disk will work as a data disk since the necessary data directories are created on the distribution disk when it is created. At this point, archiving will not work unless the disk really is a data disk or distribution disk, because the needed archive directories are not created automatically.

Notes

[1]

Running jaz_install data as root is the same as running jaz data when not the root user.