DYNIX/ptx V4.6.1 and Layered Products Software Installation Release Notes: Revert to the Previous V4.4/V4.5 Root Disk


Appendix D
Revert to the Previous V4.4/V4.5 Root Disk

The first time you boot the system on DYNIX/ptx V4.6, disk labels are written to your boot and swap disk(s). Additionally, there may be other disks on the system that have been labeled.


ATTENTION

On single-node systems, disk labeling is automatically enabled on the first boot. On clustered systems, disk labeling is enabled after all nodes are booted to multiuser on V4.6 and have run the rolling_upgrade_complete script.


If the upgrade does not complete successfully, you might need to reboot on your original V4.4/V4.5 root filesystem. If the V4.4/V4.5 root and swap partitions are on a disk(s) that is now labeled by the currently booted DYNIX/ptx V4.6, the boot will fail because DYNIX/ptx V4.4/V4.5 does not use disk labels. Depending on your site-specific situation, you can perform one of the following procedures:


Reboot V4.4/V4.5 and Reattempt the V4.6 Upgrade

To enable DYNIX/ptx V4.4/V4.5 to boot properly and prepare to reattempt the DYNIX/ptx V4.6 upgrade, complete the following steps:

  1. If the disk(s) containing the DYNIX/ptx V4.4/4.5 root and primary swap are labeled by the currently booted DYNIX/ptx V4.6, remove the disk label(s) during the reboot. To do this, boot on the DYNIX/ptx V4.4/4.5 root partition and add the -e flag to your bootpath. Additionally, set the bootflags to boot single-user mode so you can remove disk labels from other disks in a later step. For example:

    # /etc/bootflags -p -c 'f=2 n0=quad(0)pci(0)scsi(0)disk(0) -e'
  2. Reboot the system onto DYNIX/ptx V4.4 or V4.5:

    # init 6

    The purpose of this reboot is to remove the label from the disk(s) that contain root and swap. This must be done using the DYNIX/ptx V4.6 sak.dat.

  3. When the system reaches single-user mode on DYNIX/ptx V4.4/V4.5, remove the -e flag from the permanent bootflags. This option is not supported in the standalone kernels distributed with DYNIX/ptx V4.4 and V4.5:

    # /etc/bootflags -p -c 'f=2 n0=quad(0)pci(0)scsi(0)disk(0)'
  4. From single-user mode, remove the disk labels from any other disks that you wish to access while booted on DYNIX/ptx V4.4 or V4.5:

    1. Determine which disks have a disk label by using the lbledit command without any arguments. For example:

      # /usr/lbin/lbledit

      If the disk information that is output indicates any labels on disks you wish to use, then the disk label needs to be removed for the indicated disks.

      The /usr/lbin/lbledit command is not provided on the CDs for DYNIX/ptx V4.4.8 and earlier maintenance releases, nor DYNIX/ptx V4.5.2 and earlier maintenance releases. However, the /usr/lbin/lbledit command is automatically copied to the V4.4/V4.5 root filesystem during the upgrade to DYNIX/ptx V4.6.x.

    2. To remove a disk label from a disk, use the lbledit -r command. For example, to remove the disk label from sd5, enter the following command:

      # /usr/lbin/lbledit -r sd5
  5. Boot the system to multiuser mode:

    # init 2

At this point, you can reattempt to upgrade to DYNIX/ptx V4.6.1.

However, if you plan to keep the host booted on DYNIX/ptx V4.4/V4.5 for an extended period of time, you must complete additional steps to restore the complete DYNIX/ptx V4.4/V4.5 environment. Refer to the next procedure for details.


Reboot and Restore DYNIX/ptx V4.4/V4.5 Environment

To enable DYNIX/ptx V4.4/V4.5 to boot properly and restore the original DYNIX/ptx V4.4/V4.5 environment, complete the following steps:

  1. If the disk(s) containing the DYNIX/ptx V4.4/4.5 root and primary swap are labeled by the currently booted DYNIX/ptx V4.6, remove the disk label(s) during the reboot. To do this, boot on the DYNIX/ptx V4.4/4.5 root partition and add the -e flag to your bootpath. Additionally, set the bootflags to boot single-user mode so you can remove disk labels from other disks in a later step. For example:

    # /etc/bootflags -p -c 'f=2 n0=quad(0)pci(0)scsi(0)disk(0) -e'
  2. Reboot the system onto DYNIX/ptx V4.4 or V4.5:

    # init 6

    The purpose of this reboot is to remove the label from the disk(s) that contain root and swap. This must be done using the DYNIX/ptx V4.6 sak.dat.

  3. When the system reaches single-user mode on DYNIX/ptx V4.4/V4.5, remove the -e flag from the permanent bootflags. This option is not supported in the standalone kernels distributed with DYNIX/ptx V4.4 and V4.5:

    # /etc/bootflags -p -c 'f=2 n0=quad(0)pci(0)scsi(0)disk(0)'
  4. From single-user mode, remove the disk labels from any other disks that you wish to access while booted on DYNIX/ptx V4.4 or V4.5.

    1. Determine which disks have a disk label by using the lbledit command without any arguments. For example:

      # /usr/lbin/lbledit

      If the disk information that is output indicates any labels on disks you wish to use, then the disk label needs to be removed for the indicated disks.

      The /usr/lbin/lbledit command is not provided on the CDs for DYNIX/ptx V4.4.8 and earlier maintenance releases, nor DYNIX/ptx V4.5.2 and earlier maintenance releases. However, the /usr/lbin/lbledit command is automatically copied to the V4.4/V4.5 root filesystem during the upgrade to DYNIX/ptx V4.6.x.

    2. To remove a disk label from a disk, use the lbledit -r command. For example, to remove the disk label from sd5, enter the following command:

      # /usr/lbin/lbledit -r sd5
  5. Reinstall and reflash the console software for DYNIX/ptx V4.4/V4.5. See the NUMA Console Software Release Notes for details.

    This step must be performed because the V4.6 sak.dat and prxldr.elf are not supported on these older operating systems.


    ATTENTION

    The sak.dat and ptxldr.elf programs must not be installed while the operating system is running. Severe console I/O operation problems will occur if this is attempted.


    1. Shut down the operating system (init 0), power off the quads, and exit VCS.

    2. Rename the current VCS directory and the previous VCS directory in preparation to flash the console software firmware:

      1. Rename the current VCS directory to something like VCS46. The default directory is C:\VCS.

      2. If you saved the VCS directory from DYNIX/ptx V4.4/V4.5, rename it back as the current VCS directory.

      3. If you no longer have the VCS directory from DYNIX/ptx V4.4/4.5, reload VCS from the distribution CD that was provided with DYNIX/ptx V4.4/V4.5.

    3. Flash the console software firmware for DYNIX/ptx V4.4/V4.5, including the stand-alone kernel (sak.dat) and bootstrap program (ptxldr.elf).

  6. From the PTX Console window, click the Boot button to boot to single-user mode.

  7. If the Fibre Channel Firmware recipe for DYNIX/ptx V4.6.1 has already been flashed onto FC subsystem components, you must reflash the FC firmware recipe for the DYNIX/ptx V4.4/4.5 system.

  8. If you deinstalled a layered product before the DYNIX/ptx V4.6 upgrade and you need to use it after reverting back to DYNIX/ptx V4.4/V4.5, you must reinstall the product. Refer to Chapter 2 for a list of unsupported software that might have been deinstalled before the upgrade.

  9. If you performed the DYNIX/ptx V4.6 upgrade with the INIT ALT DISK DELTA procedure and the host had SAMS:Alexandria installed on DYNIX/ptx V4.4/V4.5 and you plan to use it after reverting back to DYNIX/ptx V4.4/V4.5, you must update Backup Toolkit scripts with the installalex script. Otherwise, required SAMS:Alexandria kernel components for DYNIX/ptx V4.4/4.5 will not be available. (Before the installation of DYNIX/ptx V4.6, you had to manually delete required Backup Toolkit kernel files that were not compatible with DYNIX/ptx V4.6.) For details, refer to the Backup Toolkit Release Notes.

    This step does not apply to upgrades performed with ALT DISK DELTA. In this case, the alternate disk partition was manually created before the required Backup Toolkit kernel files were deleted, hence these files were not deleted on the original root partition.

  10. Boot the system to multiuser mode:

    # init 2