Initial Installation of the Solaris 9 Operating Environment
Initial installation fails
Solution: If the Solaris installation fails, you must restart the installation. To restart the installation, boot the system from the Solaris 9 DVD, Solaris 9 Installation CD, the Solaris 9 Software 1 of 2, or from the network.
You cannot uninstall the Solaris software after the software has been partially installed. You must restore your system from a backup or begin the Solaris installation process again.
/cdrom/Solaris_9/SUNWxxxx/reloc.cpio: Broken pipe
Description: This error message does not affect the installation.
Solution: Ignore the message and continue with the installation.
Upgrading the Solaris 9 Operating Environment
Upgrading, Error Messages
No upgradable disks
Cause: A swap entry in the /etc/vfstab file is causing the upgrade to fail.
Solution: Comment out the following lines in the /etc/vfstab file:
All swap files and slices on disks not being upgraded
Swap files that are no longer present
Any unused swap slices
usr/bin/bzczt not found
Cause: Solaris Live Upgrade fails because of needing a patch cluster.
Solution: A patch is needed to install Solaris Live Upgrade. Go to http://sunsolve.sun.com for the patch.
Upgrading, General Problems
The upgrade option is not presented even though there is a version of Solaris software that's upgradable on the system.
Cause: Reason 1: The /var/sadm directory is a symlink or it is mounted from another file system.
Solution: Reason 1: Move the /var/sadm directory into the root (/) or /var file system.
Cause: Reason 2: The /var/sadm/softinfo/INST_RELEASE file is missing.
Solution: Reason 2: Create a new INST_RELEASE file by using the following template:
x
Is the version of Solaris software on the system
Cause: Reason 3: SUNWusr is missing from /var/sadm/softinfo
Solution: Solution 3: You need to do an initial installation. The Solaris software is not upgradable.
Couldn't shut down or initialize the md driver
Solution:
If not a mirror, comment out in the vsftab file.
If a mirror, break the mirror and reinstall.
The upgrade fails because the Solaris installation program cannot mount a file system.
Cause: During an upgrade, the script attempts to mount all the file systems that are listed in the system's /etc/vfstab file on the root (/) file system that is being upgraded. If the installation script cannot mount a file system, it fails and exits.
Ensure that all file systems in the system's /etc/vfstab file can be mounted. Comment out any file systems in the /etc/vfstab file that cannot be mounted or that might cause the problem so that the Solaris suninstall program does not try to mount them during the upgrade. Any system-based file systems that contain software to be upgraded (for example, /usr) cannot be commented out.
The upgrade fails
Description: The system does not have enough space for the upgrade.
Cause: Check Chapter 5, Guidelines for Allocating Disk Space (Planning) for the space problem and see if you can fix it without using auto-layout to reallocate space.
Problems upgrading mirrored roots
Solution: If you have problems upgrading when using Solaris Volume Manager mirrored roots, see "Solving Problems Related to Solaris Volume Manager" in Solaris Volume Manager Administration Guide.
To Continue Upgrading After a Failed Upgrade
The upgrade fails and the system cannot be soft-booted. The failure is for reasons beyond your control, such as a power failure or a network connection failure.
Reboot the system from the Solaris 9 DVD, Solaris 9 Installation CD, the Solaris 9 Software 1 of 2 CD, or from the network.
Choose the upgrade option for installation.
The Solaris installation program determines if the system has been partially upgraded and continues the upgrade.
System Panics When Upgrading With Solaris Live Upgrade Running 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.
Create an inactive boot environment. See "Creating a New Boot Environment".
Before upgrading the inactive boot environment, you must disable the existing Veritas software on the inactive boot environment.
Mount the inactive boot environment.
# lumount inactive_boot_environment_name mount_point
For example:
# lumount solaris8 /.alt.12345
Change to the directory that contains the vfstab, for example:
# cd /.alt.12345/etc
Make a copy of the inactive boot environment's vfstab file, for example:
# cp vfstab vfstab.501
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.
Copy the changed vfstab file, for example:
# cp vfstab.novxfs vfstab
Change directories to the inactive boot environment's system file, for example:
# cd /.alt.12345/etc
Make a copy of the inactive boot environment's system file, for example:
# cp system system.501
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 that this comment line is different than the vfstab file comment lines.
Change directories to the install-db file on the inactive boot environment, for example:
# cd /.alt.12345/etc
Create the Veritas install-db file, for example:
# touch vx/reconfig.d/state.d/install-db
Unmount the inactive boot environment.
# luumount inactive_boot_environment_name mount_point
Upgrade the inactive boot environment. See Chapter 33, Upgrading With Solaris Live Upgrade (Tasks).
Activate the inactive boot environment. See "Activating a Boot Environment".
Shut down the system.
# init 0
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.
Upgrade Veritas.
Restore the original vfstab and system files:
# cp /etc/vfstab.original /etc/vfstab # cp /etc/system.original /etc/system
Reboot the system.
# init 6