3    Installation Notes

The notes in this chapter discuss the following topics:

Do not attempt to install Tru64 UNIX Version 5.0A without first reading the notes in this chapter and in Chapter 4 that are appropriate to your processor. Failure to read these notes can result in installation problems. Also, before you start your installation, be sure to review the hardware documentation that came with your system.

3.1    General Information About Installation

The following notes apply to the installation process in general.

3.1.1    Disk Space Requirements

The minimum disk size requirement for single-disk installations is now 1 GB. It is possible to perform single-disk installations on disks with less than 1 GB of disk space, however, performance may be degraded and it is not recommended. If you attempt a single-disk installation on a disk smaller than 1 GB, you will receive a warning message.

For more information about disk space requirements, see Appendix A, which lists the size requirements for each subset.

3.1.2    Firmware Revision

The proper firmware for your system is included on the Alpha Systems Firmware Update CD-ROM that came with your kit. The Release Notes Overview included with the firmware CD-ROM provides all the information you need to install the proper firmware.

Alternatively, you can obtain this information from the Internet by using the following URL with a web browser:

http://ftp.digital.com/pub/Digital/Alpha/firmware/readme.html You can also obtain this information from the Internet by using the following address to access the firmware using FTP: 

ftp.digital.com/pub/Digital/Alpha/firmware

You can determine the current level of the firmware on your system by entering the following command on most systems: 


# consvar -v -l | grep "Firmware Rev"

If this command is not supported on your system, you can use the following command: 

# uerf | grep "Firmware revision:" | tail -1

3.1.3    HSZ Firmware Requirements

The following list provides the firmware requirements for HSZ controllers:

3.1.4    IMAP and POP

In order to use the Internet Message Access Protocol (IMAP) and Post Office Protocol (POP) servers after performing an update installation or installing the OSFINET (Additional Networking Services) subset, you need to do the following:

  1. Make sure that the /etc/passwd file (local, yp, or NIS) contains entries for the IMAP and POP users. If it does not, create them. For example: 

    pop:*:13:6:POP Mail Service Account:/:
imap:*:14:6:IMAP Mail Service Account:/:

    Substitute the values 13 and 14 with a user ID that is appropriate for your system. For more information, see the passwd(4) reference page. Also, substitute the value 6 with the group ID of the mail group on your system; see the group(4) reference page.

  2. Enter the following command as root so that the IMAP and POP files and directories have the correct permission, owner, and group: 

    # setld -c OSFINET500 MAILSERVERSETUP

3.1.5    Initial sendmail Warning Message

The first time you boot the system after a full installation, the following warning message is displayed as a result of starting sendmail: 

warning: local host name (hostname) is not qualified;
fix $j in config file.

This indicates that the system does not have a qualified name because neither DNS (BIND) nor mail has been configured. However, sendmail will continue to operate.

3.1.6    The autopush Message Displayed During Boot

The following message is displayed on the console while booting: 

/usr/sbin/autopush: Can't push requested modules on STREAM for entry 39
/usr/sbin/autopush: Device (6,-1) already configured

You can ignore this message.

3.1.7    Join Database Migration

If your system provides Dynamic Host Configuration Protocol (DHCP) Services, Remote Installation Services (RIS), or Dataless Management Services (DMS) to other systems, you must update the database files for the join daemon after you complete the installation. See Section 5.4.1 for additional information.

3.1.8    I/O Error Message

After the installation process has completed installing all of the requested subsets, you may encounter the following benign error message: 

I/O error (errno 5) for block ( xxx , xxx ) on device xxx , x

You can ignore this message. The installation will complete successfully.

3.1.9    Worldwide Language Support Error

During the installation of the Worldwide Language Support subsets, the following error may appear in the installation log: 

Loading subset 1 of 36 ...
find: ./usr/dt/config/psfonts : No such file or directory
 
Worldwide Base System
Copying from kit (disk)
Working....Tue Mar 28 16:56:16 EST 2000
Verifying

You can ignore this error; it has no adverse affect on the installation.

3.2    Layered Product Considerations

The following notes apply to layered products for Tru64 UNIX Version 5.0A.

3.2.1    Mounting the Associated Products CD-ROM

You can mount the Associated Products CD-ROMs (APCDs) with the mount command on Tru64 UNIX systems running Version 4.0E or later, as follows: 


# mount -r /dev/rz4c /mnt

To mount the APCDs on releases prior to Version 4.0E, you must mount the CD-ROMs with the following options: 


# mount -r -t cdfs -o rrip /dev/rz4c /mnt

On versions prior to Version 4.0D you might receive the following error message, indicating that compact disc file system (CDFS) support is not built in to the kernel that is currently running: 


# mount -r -t cdfs -o rrip /dev/rz4c /mnt
/dev/rz4c on /mnt: No valid filesystem exists on this partition

If you receive this error, you need to build your kernel with the following option: 

ISO 9660 Compact Disc File System (CDFS)

3.2.2    Internet AlphaServer System Software

The notes in this section apply to Internet AlphaServer System Software (IASS). It is expected that these problems will be corrected in the next release of IASS.

3.2.2.1    Disable ASE Failover for IASS Services Before Upgrade

IASS Version 4.2 and earlier versions are not supported on this version of the operating system. It is recommended that you upgrade to Open Source Internet Solutions Version 5.0 or later.

If you intend to continue running an older version of IASS and are upgrading to this version of the operating system, you must disable all ASE failover support of IASS services before the upgrade. Use the IASS Administration utility to disable ASE failover support.

ASE functionality is replaced by TruCluster Server Version 5.0A.

3.2.3    AlphaServer Console Revision 5.7 Firmware Required for TruCluster Server

Systems that will run TruCluster Server Version 5.0A or higher require AlphaServer Console Revision 5.7 or higher. If you use Revision 5.6 console firmware, the cluster member might fail to boot with Reservation Conflict errors.

Only clustered systems require Revision 5.7 or higher. All other systems are supported with the AlphaServer Console Revision 5.6 included with your kit.

The AlphaServer Console Revision 5.7 firmware is not included with your kit. However, you can obtain the firmware from the following URL:

http://ftp.digital.com/pub/DEC/Alpha/firmware

3.3    Full Installation

To perform a full installation on your system, refer to the instructions in the Installation Guide.

This section provides additional information on performing a full installation.

3.3.1    Systems with Large Numbers of Disks

Because of the new device naming technology in this release, a condition may arise where a machine with a large number of disks might not be able to be initially installed. (Note that a RAID disk is configured as a JBOD, it is seen as single disk.) This is because the number of inodes in the memory file systems used for devices might be exhausted. As a guide, you can refer to following table to determine if you will encounter this problem:

Memory Size Max Number of Disks
64 MB to 256 MB 63
256 MB to 512 MB 127
512 MB to 1 GB 190

Noted that a RAID device, namely a SWXVR device, is counted as a single disk device.

To avoid the problem, power down a number of the disks on the system prior to attempting the full installation. This reduces the number of inodes used and hence allows you to install the software on the system. Once the installation is complete, you can repower the disks and reboot the system, at which time the disks are reconfigured into the system.

3.3.2    Errors Displayed After a Full Installation

The first time you boot a system after a full installation, the device-naming verification fails. The error is reported as wrong major number and you are stopped in single-user mode. You can clear the error by executing the following command: 

# dsfmgr -vF

This command performs a verification with the fix option. After issuing this command, you can continue to boot the system.

The problem is caused by the installation process on systems where the minimal installation kernel's device switch table differs from the one that is saved. When the previous configuration data is restored to the new disk, there is a mismatch of major numbers. This causes some devices to be incorrectly created as cluster devices or causes cluster devices not to be created as cluster devices.

3.4    Update Installation

Version 5.0A supports update installations from Versions 4.0F and 5.0.

To update your Tru64 UNIX operating system software to Version 5.0A, you must use the installupdate utility or full installation procedures as described in the Installation Guide.

Note that the -i flag for the installupdate command will be retired in a future version of Tru64 UNIX. See Section 2.2.9 for more information.

The installupdate procedure checks to see if there is enough space on the disk you have selected to do the installation. If there are any conflicts, the installupdate procedure enables you to remove unecessary files to create space. For more information, see the Installation Guide.

The following sections apply to the update installation procedure.

3.4.1    Adaptec AIC-789x Ultra SCSI Driver Support

If you update a Version 4.0F system that supports the Adaptec AIC-789x Ultra SCSI Driver to Version 5.0A, the Adaptec Driver will no longer be supported.

This support was provided in Version 4.0F by the New Hardware Delivery-3 kit. Support for this device on Version 5.0A systems, will be provided through a later version of the New Hardware Delivery kit.

3.4.2    Hardware Product Kit

If the Update Installation process detects an installed hardware product kit, you are prompted to insert the appropriate version of the hardware product kit CD-ROM.

You can bypass the update of the hardware product kit by pressing the Return key at the Enter kit location prompt and continue the update installation.

You can decide to bypass the update of the kit, although this is not recommended, if you do not have the current hardware product kit CD-ROM in your possession or if you do not want to update the hardware product kit at all.

3.4.3    Update Installation Might Exit While Removing SVE

If the update installation detects that the System V Environment (SVE) product is installed on the system, it asks for that product to be removed. If the SVEADM subset is installed, the update installation is terminated by the removal of the SVEADM subset. The cause of this is an init command present in the SVEADM subset control program (.scp file).

To avoid this problem, remove the SVEADM subset prior to running the update installation by performing the following steps:

  1. Determine the exact subset name by issuing the following command: 

    # setld -i | grep SVEADM | grep installed

  2. Remove the subset by using the setld -d command and the name of the subset.

3.4.4    Reconfigure Mail After an Update Installation

After performing an update installation on any system running an earlier version of the operating system, you must reconfigure mail by using either /usr/sbin/mailconfig or /usr/sbin/mailsetup. The new sendmail configuration will ensure that all mail leaving your system has a fully qualified return address and your mail configuration is cluster-ready.

You must use the application that was used to create the current sendmail.cf file; otherwise, you will lose your previously saved configuration.

If you use the /usr/sbin/mailsetup program, the following message might be displayed:

An m4 configuration file has been found and it is different from the default produced by mailsetup. Mailsetup does not support a /var/adm/sendmail/sendmail.m4 file which has been modified. Use this file at your own risk. Do you wish to use this file (y/[n]) ?

If you want sendmail to fully qualify the return address when leaving the system and to be cluster-ready, answer no. If you do not want these features, answer yes.

3.4.5    Failure to Merge /var/adm/sendmail/sendmail.cf

If you have a client mail configuration created by mailsetup and perform an update installation from Version 4.0F, the /usr/adm/sendmail/sendmail.cf merge process fails to update IMAP rules. You can ignore this error.

If you want to use IMAP in a client configuration, rerun the configuration using either mailsetup or mailconfig.

3.4.6    Additional Disk Space Needed

If your system does not have enough free disk space to complete the update installation, you are presented with a list of three options to recover additional disk space.

If you remove software subsets belonging to the Operating System (OSF) or Worldwide Language Support (IOS) products to recover disk space, the update installation process must recalculate the disk space amount listed in the Total Needed category. Allow the update to continue so it can recalculate the disk space based upon the currently installed software subsets.

3.4.7    Core Files Present After Update Install

Due to a change in the stat system call, it was necessary to modify the update installation process so that the new executables could be run on a previous release of the operating system during the update process. However, after the update completes, the modifications are no longer accessible and therefore some commands fail.

The umount command is one of the commands that fail. The core files for this command are placed in the root directory.

The failure of these commands does not impact the successful completion of the update installation process.

3.4.8    PanoramiX ADK

If you previously installed the Advance Developers kit (ADK) for the PanoramiX extension to the X server, you must remove it before doing an update installation of Tru64 UNIX Version 5.0A. If you do not, the X server will not start. If this happens, do the following:

  1. Log in as root.

  2. Remove the ADK.

  3. Replace the X server configuration file with the original version of the Tru64 UNIX Version 5.0A file, /var/X11/Xserver.conf.

  4. Run the xlogin start command.

3.4.9    Ignore clu_get_info Warnings

When the update installation process determines that there is not enough disk space to complete the process, you can use the Remove Software Subsets option from the Recover of Disk Space dialog box. While subsets are being deleted, the following message might be displayed: 


Deleting subset_description_and_name/updmnt/isl/setld:
clu_get_info: not found

You can ignore these warnings; they do not affect the operation of the update installation process or the removal of the subsets.

3.5    RIS Installation

This section provides notes pertaining to Remote Installation Services (RIS).

3.5.1    Time Zone Restriction

New time zones have been added to this version of the operating system. Therefore, servers that might have indicated the US-Eastern time zone while running an earlier version of the operating system now indicate a time zone such as America-New York.

When you install an earlier version of the operating system on a client from a RIS server running Tru64 UNIX Version 5.0A, the earlier version of the operating system does not recognize the time zone and does not automatically set the time zone during the installation procedure. This occurs because the new time zones do not match those in the earlier versions. Therefore, you must set the time zone manually after the installation.

3.6    Dataless Server Installation

This section provides notes pertaining to Dataless Server installations.

3.6.1    Restriction Using TruCluster Server

TruCluster Server Version 5.0A does not support the Dataless Management Services (DMS).