JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris 10 9/10 Installation Guide: Custom JumpStart and Advanced Installations
search filter icon
search icon

Document Information


Part I Using Custom JumpStart

1.  Where to Find Solaris Installation Planning Information

2.  Custom JumpStart (Overview)

3.  Preparing Custom JumpStart Installations (Tasks)

4.  Using Optional Custom JumpStart Features (Tasks)

5.  Creating Custom Rule and Probe Keywords (Tasks)

6.  Performing a Custom JumpStart Installation (Tasks)

7.  Installing With Custom JumpStart (Examples)

8.  Custom JumpStart (Reference)

9.  Installing a ZFS Root Pool With JumpStart

Part II Appendixes

A.  Troubleshooting (Tasks)

Problems With Setting Up Network Installations

Problems With Booting a System

Booting From Media, Error Messages

Booting From Media, General Problems

Booting From the Network, Error Messages

Booting From the Network, General Problems

Initial Installation of the Solaris OS

x86: To Check IDE Disk for Bad Blocks

Upgrading the Solaris OS

Upgrading, Error Messages

Upgrading, General Problems

To Continue Upgrading After a Failed Upgrade

x86: Problems With Solaris Live Upgrade When You Use GRUB

System Panics When Upgrading With Solaris Live Upgrade Running Veritas VxVm

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

To Install Software From a Network Installation Image or From the Solaris Operating System DVD

To Install From the Solaris Software - 1 CD or From a Network Installation Image

B.  Additional SVR4 Packaging Requirements (Reference)



Upgrading the 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: Solaris Live Upgrade fails because of needing a patch cluster.

Solution: A patch is needed to install Solaris Live Upgrade. Ensure that you have the most recently updated patch list by consulting Search for the info doc 72099 on the SunSolve web site.

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 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 Mbytes or use another method of upgrading such as the Solaris installation program from Solaris Operating System 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 Solaris root (/) file system and is found on the 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

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:


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: Follow these instructions:

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 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 9/10 Installation Guide: Planning for Installation and Upgrade for the space problem and see if you can fix it 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.