HP Tru64 UNIX and TruCluster Server Version 5.1B-5 Patch Summary and Release Notes (March 2009)

Note that all filesets with clones that are served by the node on which the attribute is
set will also see this change. It may be advisable (though not required) to have those
filesets whose clone files have fewer extents be served by a different node during the
time the tunable attribute is set.
4.2.16 AlphaServer ES47 or AlphaServer GS1280 Hangs When Added to Cluster
If after running clu_add_member to add an AlphaServer ES47 or AlphaServer GS1280
as a member of a TruCluster the AlphaServer hangs during its first boot, try rebooting
it with the original V5.1B generic cluster kernel, clu_genvmunix.
Use the following instructions to extract and copy the V5.1B cluster genvmunix from
your original Tru64 UNIX kit to your AlphaServer ES47 or AlphaServer GS1280 system.
In these instructions, the AlphaServer ES47 or AlphaServer GS1280 is designated as
member 5. Substitute the appropriate member number for your cluster.
1. Insert the Tru64 UNIX Associated Products Disk 2 into the CD-ROM drive of an
active member.
2. Mount the CD-ROM to /mnt. For example:
# mount -r /dev/disk/cdrom0c /mnt
3. Mount the boot disk of the AlphaServer ES47 or AlphaServer GS1280 on its specific
mount point; for example:
# mount root5_domain#root /cluster/members/member5/boot_partition
4. Extract the original clu_genvmunix from the CD-ROM and copy it to the boot
disk of the AlphaServer ES47 or AlphaServer GS1280 member.
# zcat < TCRBASE540 | ( cd /cluster/admin/tmp; \
tar -xf - ./usr/opt/TruCluster/clu_genvmunix)
# cp /cluster/admin/tmp/usr/opt/TruCluster/clu_genvmunix \
/cluster/members/member?/boot_partition/genvmunix
# rm /cluster/admin/tmp/usr/opt/TruCluster/clu_genvmunix
5. Unmount the CD-ROM and the boot disk:
# umount /mnt
# umount /cluster/members/member5/boot_partition
6. Reboot the AlphaServer ES47 or AlphaServer GS1280.
4.2.17 Problems with clu_upgrade Switch Stage
If the clu_upgrade switch stage does not complete successfully, you may see a
message like the following:
versw: No switch due to inconsistent versions
The problem can be due to one or more members running genvmunix, a generic kernel.
Use the command clu_get_info -full and note each member's version number,
as reported in the line beginning
Member base O/S version
4.2 Prior Release Notes 215