JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris 10 1/13 Installation Guide: Network-Based Installations     Oracle Solaris 10 1/13 Information Library
search filter icon
search icon

Document Information


Part I Planning to Install Over the Network

1.  Where to Find Oracle Solaris Installation Planning Information

2.  Preconfiguring System Configuration Information (Tasks)

3.  Preconfiguring With a Naming Service or DHCP

Part II Installing Over a Local Area Network

4.  Installing From the Network (Overview)

5.  Installing From the Network With DVD Media (Tasks)

6.  Installing From the Network With CD Media (Tasks)

7.  Patching the Miniroot Image (Tasks)

8.  Installing Over the Network (Examples)

9.  Installing From the Network (Command Reference)

Part III Installing Over a Wide Area Network

10.  WAN Boot (Overview)

11.  Preparing to Install With WAN Boot (Planning)

12.  Installing With WAN Boot (Tasks)

13.  SPARC: Installing With WAN Boot (Tasks)

14.  SPARC: Installing With WAN Boot (Examples)

15.  WAN Boot (Reference)

Part IV Appendixes

A.  Troubleshooting (Tasks)

Problems With Setting Up Network Installations

Problems With Booting a System

Error Messages When Booting From Media

General Problems When Booting From Media

Booting From the Network, Error Messages

General Problems When Booting From the Network

Initial Installation of the Oracle Solaris OS

x86: How to Check an IDE Disk for Bad Blocks

Upgrading the Oracle Solaris OS

Upgrading Error Messages

General Problems When Upgrading

How to Continue Upgrading After a Failed Upgrade

x86: Problems With Live Upgrade When You Use GRUB

System Panics When Upgrading With Live Upgrade Running Veritas VxVM

How to Upgrade When Running Veritas VxVM

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

How to Include a Service Partition When Installing Software From a Network Installation Image or From the Oracle Solaris DVD

How to Include a Service Partition When Installing From the Oracle Solaris Software - 1 CD or From a Network Installation Image

B.  Installing or Upgrading Remotely (Tasks)



Upgrading the Oracle Solaris OS

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:

usr/bin/bzcat not found

Cause: Live Upgrade fails because of needing a patch cluster.

Solution: A patch is needed to install Live Upgrade. Ensure that you have the most recently updated patch list by consulting (My Oracle Support). Search for the knowledge document 1004881.1 - Solaris Live Upgrade Software Patch Requirements (formerly 206844) on My Oracle Support.

Upgradeable Solaris root devices were found, however, no suitable partitions to hold the Solaris install software were found. Upgrading using the Solaris Installer is not possible. It might be possible to upgrade using the Solaris Software 1 CDROM. (x86 based systems only)

Cause: You cannot upgrade with the Oracle Solaris Software - 1 CD because you do not have enough space.

Solution: To upgrade, you can either create a swap slice that is larger than or equal to 512 MB or use another method of upgrading such as the Oracle Solaris installation program from Oracle Solaris DVD, a net installation image, or JumpStart.

ERROR: Could not select locale (x86 based systems only)

Cause: When you test your JumpStart profile by using the pfinstall -D command, the dry run test fails under the following conditions:

With the introduction of GRUB software, the miniroot is compressed. The software can no longer find the list of locales from the compressed miniroot. The miniroot is the smallest possible Oracle Solaris root (/) file system and is found on the Oracle Solaris installation media.

Solution: Perform the following steps. Use the following values.

  1. Become superuser or assume an equivalent role.

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

  2. Uncompress the miniroot archive.

    # /usr/bin/gzcat $MINIROOT_ARCHIVE > $TEMP_FILE_NAME
  3. Create the miniroot device by using the lofiadm command.

    # LOFI_DEVICE=/usr/sbin/lofiadm -a $TEMP_FILE_NAME
    # echo $LOFI_DEVICE
  4. Mount the miniroot with the lofi command under the Miniroot directory.

    # /usr/sbin/mount -F ufs  $LOFI_DEVICE  $MINIROOT_DIR
  5. Test the profile.

    # /usr/sbin/install.d/pfinstall -D -c $MEDIA_DIR $path-to-jumpstart_profile
  6. After the testing is completed, unmount the lofi device.

    # umount  $LOFI_DEVICE
  7. Delete the lofi device.

    # lofiadm -d $TEMP_FILE_NAME

General Problems When Upgrading

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:


The version of Oracle Solaris software on the system

Cause: Reason 3: The package SUNWusr is missing from /var/sadm/softinfo.

Solution: Solution 3: You need to do an initial installation. The Oracle Solaris software is not upgradable.

Couldn't shut down or initialize the md driver

Solution: Perform the following:

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.

Solution: 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 Oracle Solaris installation 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 Upgrading With Disk Space Reallocation in Oracle Solaris 10 1/13 Installation Guide: Planning for Installation and Upgrade for the space requirement and see if you can fix this issue without using auto-layout to reallocate space.

Problems upgrading RAID–1 volume root (/) file systems

Solution: If you have problems upgrading when using Solaris Volume Manager RAID-1 volumes that are the root (/) file system, see Chapter 25, Troubleshooting Solaris Volume Manager (Tasks), in Solaris Volume Manager Administration Guide.