System Panics When Upgrading With Solaris Live Upgrade Running Veritas VxVM

When you use Solaris Live Upgrade while upgrading and running Veritas VxVM, the system panics on reboot unless you upgrade by using the following procedure. The problem occurs if packages do not conform to Solaris advanced packaging guidelines.

1. Become superuser or assume an equivalent role.

   ---

   Note - Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.

   ---

   Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.

2. Create an inactive boot environment. See Creating a New Boot Environment in Oracle Solaris 10 9/10 Installation Guide: Solaris Live Upgrade and Upgrade Planning.
3. Before upgrading the inactive boot environment, you must disable the existing Veritas software on the inactive boot environment.
   1. Mount the inactive boot environment.

      # lumount inactive_boot_environment_name mount_point

      For example:

      # lumount solaris8 /mnt 

   2. Change to the directory that contains the vfstab, for example:

      # cd /mnt/etc

   3. Make a copy of the inactive boot environment's vfstab file, for example:

      # cp vfstab vfstab.501

   4. In the copied vfstab, comment out all Veritas file system entries, for example:

      #  sed '/vx\/dsk/s/^/#/g' < vfstab > vfstab.novxfs

      The first character of each line is changed to #, which makes the line a comment line. Note that this comment line is different than the system file-comment lines.

   5. Copy the changed vfstab file, for example:

      # cp vfstab.novxfs vfstab

   6. Change directories to the inactive boot environment's system file, for example:

      # cd /mnt/etc

   7. Make a copy of the inactive boot environment's system file, for example:

      # cp system system.501

   8. Comment out all “forceload:” entries that include drv/vx.

      # sed '/forceload: drv\/vx/s/^/*/' <system> system.novxfs

      The first character of each line is changed to *, which makes the line a command line. Note that this comment line is different than the vfstab file comment lines.

   9. Create the Veritas install-db file, for example:

      # touch vx/reconfig.d/state.d/install-db

   10. Unmount the inactive boot environment.

       # luumount inactive_boot_environment_name 

4. Upgrade the inactive boot environment. See Chapter 5, Upgrading With Solaris Live Upgrade (Tasks), in Oracle Solaris 10 9/10 Installation Guide: Solaris Live Upgrade and Upgrade Planning.
5. Activate the inactive boot environment. See Activating a Boot Environment in Oracle Solaris 10 9/10 Installation Guide: Solaris Live Upgrade and Upgrade Planning.
6. Shut down the system.

   # init 0

7. Boot the inactive boot environment in single-user mode:

   OK boot -s

   Several messages and error messages that contain “vxvm” or “VXVM” are displayed that can be ignored. The inactive boot environment becomes active.

8. Upgrade Veritas.
   1. Remove the Veritas VRTSvmsa package from the system, for example:

      # pkgrm VRTSvmsa

   2. Change directories to the Veritas packages.

      # cd /location_of_Veritas_software

   3. Add the latest Veritas packages to the system:

      #  pkgadd -d `pwd` VRTSvxvm VRTSvmsa VRTSvmdoc VRTSvmman VRTSvmdev

9. Restore the original vfstab and system files:

   # cp /etc/vfstab.original /etc/vfstab
   # cp /etc/system.original /etc/system

10. Reboot the system.

    # init 6

x86: Service Partition Not Created by Default on Systems With No Existing Service Partition

If you install the current Solaris release on a system that does not currently include a service or diagnostic partition, the installation program might not create a service partition by default. If you want to include a service partition on the same disk as the Solaris partition, you must re-create the service partition before you install the current Solaris release.

If you installed the Solaris 8 2/02 OS on a system with a service partition, the installation program might not have preserved the service partition. If you did not manually edit the fdisk boot partition layout to preserve the service partition, the installation program deleted the service partition during the installation.

If you want to include a service partition on the disk that contains the Solaris partition, choose one of the following workarounds.