Appendix A Troubleshooting

This chapter contains solutions for problems you might encounter when upgrading using Solaris Live Upgrade.

Upgrade Problems

Cannot Use the Solaris 8 Device Configuration Assistant Intel Platform Edition diskette to Boot the New Boot Environment

Mount Failed. Unable to mount a Solaris root file system from the device: DISK:

Description:

On an Intel system, when using the Device Configuration Assistant diskette and after upgrading and activating the new boot environment, the activation fails.

When booting from the Solaris 8 Device Configuration Assistant Intel Platform Edition diskette, the diskette does not find the correct path to partition with the root (/) file system. You must manually update the boot diskette before activating the new boot environment. For the procedure on updating the boot diskette, see x86: (Optional) Update Boot Diskette Before Activating.

Creation of New Boot Environment Fails When Reconfiguring Swap

ERROR: Template filesystem definition failed for -..

ERROR: Configuration of BE failed.

Cause:

The swap slice is being used by a boot environment other than the current boot environment or the source boot environment specified by the -s option and the creation of a new boot environment fails.

Description:

The swap slice cannot be in use by any boot environment except the current boot environment or if the -s option is used, the source boot environment. The boot environment creation fails if the swap slice is being used by any other boot environment whether the slice contains a swap, ufs, or any other file system.

Solution:

Choose a slice for swap following the above guidelines.

System Panics When Upgrading On Veritas VxVm

When using 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. Create an inactive boot environment. See Creating a New Boot Environment.

2. 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 /.alt.12345

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

      # cd /.alt.12345/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 vfstab.novxfs > vfstab < '/vx\/dsk/s/^/#/g'

      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 /.alt.12345/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: system.novxfs > system < drv\/vx/s/^/*/'

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

   9. Change directories to the install-db file on the inactive boot environment, for example:

      # cd /.alt.12345/etc

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

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

   11. Unmount the inactive boot environment.

       # luumount inactive_boot_environment_name mount_point

3. Upgrade the inactive boot environment. See Chapter 4, Upgrading With Solaris Live Upgrade.

4. Activate the inactive boot environment. See Activating a Boot Environment .

5. Shut down the system.

   # init 0

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

   OK boot -s

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

7. Upgrade Veritas.

   1. Remove the Veritas VRTSvmsa package from 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

8. Restore the original vfstab and system files:

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

9. Reboot the system.

   # init 6