3 Installation Notes

The notes in this chapter discuss the following topics:

General information about installation (Section 3.1)

Layered product considerations (Section 3.2)

Full installation (Section 3.3)

Update installation (Section 3.4)

RIS installation (Section 3.5)

Dataless Server installation (Section 3.6)

Do not attempt to install Tru64 UNIX Version 5.1 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 process, 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.

Although the minimum disk space for installing the operating system is a 1 GB disk, Compaq recommends that systems have at least two 2 GB disks to ensure sufficient disk space for swap, patches, and storage.

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

3.1.2 Firmware Revision

Systems that will run the TruCluster Server Version 5.1 software on Tru64 UNIX Version 5.1 require Alpha System Reference Manual (SRM) console firmware Version 5.7 or later. If you use Revision 5.6 or earlier console firmware, the cluster member might fail to boot with Reservation Conflict errors.

Systems that will run on Tru64 UNIX Version 5.1 and use both unit partitioning and multipathing on an HSG80 device require Alpha SRM console firmware Version 5.6 or later.

Systems that will run on Tru64 UNIX Version 5.1 and use Fibre Channel Arbitrated Loop require Alpha SRM console firmware Version 5.8.

3.1.2.1 HSZ Firmware Requirements

The following list provides the minimum firmware requirements for HSZ controllers:

HSZ40 - Version 3.7 or higher firmware.

HSZ50 - Version 5.7 or higher.

HSZ70 - Version 7.7 or higher.

HSZ80 - Version 8.3-1 or higher.

HSG80 - Version 8.5 or higher.

You cannot put the HSZ40A controller on a multi-initiator bus in a cluster or multi-initiator from the same host. You must put these controllers on a bus with a single-host adapter. If you need to put them on a shared bus, you can upgrade them to HSZ40B, HSZ40C, or HSZ50 controllers and then put them on a shared SCSI bus.

3.1.3 Nonconfigured Subsets and the setld Menu Restriction

The setld -D command manages software in an alternate root directory. You can use this feature to install software onto a disk and then move the disk to a different system. When you use the -D option, the software is loaded onto the disk; however, it is not configured. The software is configured later, in a separate step by using setld -c command.

If you use the setld -D command, name the subsets to load on the setld command line. Do not use the interactive software selection menu provided with setld to choose the subsets. If you use the software selection menu to choose the subsets, failures, similar to the following, can occur:

5 OSFJAVADEV510 Java 1.1.8-7 Development Environment
cannot be installed as one of the required subsets is not available.
PLEASE BEGIN YOUR SELECTIONS AGAIN.

3.1.4 Reloading Subsets with setld

Some layered product subsets check when they are installed to see if the subsets are already on the system. If they are, they prevent you from reinstalling them. This introduces an error into the software management database after which the setld -i command reports that the subset is not installed, even though all of its files are present on the system.

To avoid this problem, use the setld -d command to delete a subset before using the setld -l command to reinstall it.

If you accidentally have the situation where you want to delete a subset but you cannot, you can correct the problem by using the touch command and then the setld -d command. For example, if the situation occurred with the DFARTL388 subset, you would do the following:

# touch /usr/.smdb./DFARTL388.lk
# setld -d DFARTL388

Afterwards, you can reinstall the subset using the setld -l command.

3.1.5 The setld Utility Does Not Handle White Space in Directory Names

The setld utility does not handle directory names that contain white space.

3.1.6 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:

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.

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.7 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.8 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.9 I/O Error Message

After the installation process has completed installing all of the requested subsets, you might see 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.10 Ignore the error writing output file Message

During the installation of software subsets, ignore the error writing output file message. The error is harmless.

3.1.11 Persistent Reservation Errors

Under certain circumstances, you can encounter persistent reservation errors. If this problem occurs, see Appendix B.

3.2 Layered Product Considerations

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

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/disk/cdrom0c /mnt

On releases prior to Version 4.0E, you must mount the APCDs 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 Open Source Internet Solutions

The notes in this section apply to the Open Source Internet Solutions (OSIS) product. The OSIS product was formerly called the Internet AlphaServer System Software (IASS). OSIS Version 5.2 and earlier versions, including IASS, are not supported on this version of the operating system. It is recommended that you upgrade to Open Source Internet Solutions (OSIS) Version 5.3 or higher.

3.2.2.1 Disable ASE Failover for OSIS Services Before Upgrade

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

ASE functionality is replaced by TruCluster Server Version 5.1.

3.3 Full Installation

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

3.4 Update Installation

Version 5.1 supports update installations from Versions 4.0G and 5.0A.

To update your Tru64 UNIX operating system software to Version 5.1, 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.7 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 Update Installation of UFS File System on LSM Volumes Will Fail

Due to a problem setting the FSTYPE of LSM volumes on Version 4.0 systems, systems with UFS file systems on LSM volumes might experience problems during the update installation process when booting Version 5.0 and higher. If the /usr or /var file system is an encapsulated LSM volume, then the system will not come up to multiuser mode. There are two workarounds for this problem, depending on whether you determine if there are any LSM volumes containing UFS file systems on your system before or after performing an update installation process.

To determine if any of the LSM volumes on your system contain UFS file systems, run the following command:

# mount -t ufs | grep /dev/vol/

If you determine prior to the update installation that one or more LSM volumes contain UFS file systems, run the following command to workaround the problem:

# voledit set fstype=4.2BSD UFSVOLUMES

The UFSVOLUMES variable is the list of LSM volumes containing UFS file systems. For example, isuppose the mount -t ufs | grep /dev/vol/ command returns the following information:

# mount -t ufs | grep /dev/vol/
/dev/vol/rootdg/rootvol on / type ufs (rw)
/dev/vol/rootdg/vol-rz8g on /usr type ufs (rw)
/dev/vol/rootdg/vol-rz8h on /var type ufs (rw)
/dev/vol/rootdg/vol-rz9c on /mnt type ufs (rw)

You would issue the following voledit command:


# voledit set fstype=4.2BSD rootvol vol-rz8g vol-rz8h vol-rz9c

If you cannot determine prior to the update installation that one or more LSM volumes contain UFS file systems, or if you have already performed the update installation, do the following:

Boot the system to single-user mode, as follows:
```
>>> boot -fl s
```

Mount the root directory as read/write:
```
# mount -u /
```

Restart LSM:
```
# vold -k
```

Manually set the volume file system types (fstype):
```
# voledit set fstype=4.2BSD UFSVOLUMES
 
 
```
The UFSVOLUMES variable is the list of LSM volumes containing UFS file systems.

Either continue to bring the system up to multiuser mode or reboot the system as normal.

3.4.2 Update Installation Might Exit While Removing SVE

If the update installation procedure 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 process terminates while attempting to remove 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:

Determine the exact subset name by issuing the following command:
```
# setld -i | grep SVEADM | grep installed
```

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

3.4.3 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 ensures that all mail leaving your system has a fully qualified return address and your mail configuration is cluster-ready.

When you reconfigure mail, 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.4 Failure to Merge /var/adm/sendmail/sendmail.cf

If you have a client mail configuration created by mailsetup and perform an update installation from Tru64 UNIXVersion 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.5 Dangerous Write Permission Warning for the Sendmail Configuration File

If you are performing an update installation from any variant of Tru64 UNIX Version 4.0, you might get the following warning when you start the sendmail daemon or run the newaliases command:


/var/adm/sendmail/sendmail.cf: WARNING: dangerous write permissions

The permissions of the /var/adm/sendmail/sendmail.cf file should be 0644. If they are not, run the following command as root:

# chmod 644 /var/adm/sendmail/sendmail.cf

Then restart the sendmail daemon:

# /sbin/init.d/sendmail restart

3.4.6 Restriction to Using the Graphical Update Installation Interface

There is a restriction that interferes with the ability to use the update installation's graphical user interface (GUI) in this release. The restriction only applies if the system you are updating is running Tru64 UNIX Version 5.0A, the system has the Wolrdwide Language Support (WLS) subsets installed, and you are performing the update from a CD-ROM.

If you use the update installation GUI under these circumstances, the text-based will be displayed instead of the GUI.

3.4.7 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 for recovering 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.8 Changes to /etc/doprc Are Not Preserved

After an update installation from Tru64 UNIXVersion 4.0G or 5.0A to Version 5.1, customizations to the /etc/doprc file are not preserved.

The existing /etc/doprc file on the system is copied to /etc/doprc.PreUPD and a new /etc/doprc file is installed on the system.

3.4.9 Ignore the /etc/doprc Error Message

When performing an update installation on a system with the Worldwide Language Support (WLS) software installed, the following error messages might appear when the system is trying to remove old WLS subsets:


 
Error occurred trying to update /etc/doprc:
Dop_delete_application i18nconfig /etc/doprc
can't read "action": no such variable

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

3.4.10 Ignore clu_get_info Warnings

If your system does not have enough free disk space to complete the update installation, 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.4.11 Ignore grep Error on Worldwide Language Support

If the Worldwide Language Support (WLS) software is installed on the system and you an update installation, the following error message might appear during the update installation process:

Restoring Worldwide Support tty features configuration
grep: can't open /usr/sys/conf/.product.list
Loading I18N tty kernel modules ... done

You can ignore this message. It does not affect the update installation procedure. The procedure will continue and complete successfully.

3.4.12 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.13 PanoramiX ADK

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

Log in as root.

Remove the ADK.

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

Run the xlogin start command.

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.1, 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.5.2 Rolling Upgrade Restriction

If you are performing a rolling upgrade from a RIS server, you must register both the cluster alias and the lead cluster member as RIS clients before you execute the Install Phase of the rolling upgrade.

3.5.3 Serving the Worldwide Language Support Product from a RIS Server

You cannot extract the Worldwide Language Support (WLS) product into a RIS area. Therefore, if you need to serve WLS to your RIS clients, create a symlink for this product into the RIS area. For more information on this procedure, see the Sharing Software on a Local Area Network manual.

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 or higher does not support the Dataless Management Services (DMS).