Installation Bugs

The following bugs might occur during or after the installation of the Oracle Solaris 10 OS.

Jumpstart Installation Fails on Machines Attached to a SAN (7072761)

Jumpstart installation of the Oracle Solaris 8/11 operating system fails on machines that are attached to a SAN. The reason is because on a server with SAN based storage, Oracle Solaris 8/11 does not parse the rootdisk option correctly.

You might see error messages similar to the ones shown in the following example.

STK-UniversalXport-0760 doesn't have a VTOC label
STK-FLEXLINE380-0760 doesn't have a VTOC label
STK-FLEXLINE380-0760 doesn't have a VTOC label
LSI-MR9261-8i-2.90 doesn't have a VTOC label
other doesn't have a VTOC label
Warning: Could not find matching rule in rules.ok

Workaround: Install the Oracle Solaris 8/11 operating system manually.

ZFS Root System Might Hang When Swapping to zvol (6898318)

The ZFS root system can hang during installation or post installation when the system swaps to a ZFS swap volume.

Choose one of the following workarounds.

Workaround 1:

• Set the primarycache property on the ZFS swap volume. For example:

  # zfs set primarycache=metadata rpool/swap

Workaround 2:

• Create a raw swap partition and remove the ZFS swap volume.

  1. Create a slice and activate as a swap device.

     For example:

     # swap -a /dev/dsk/c0t0d0s1

  2. Add an entry for this swap device in the /etc/vfstab file.

     For example:

     /dev/dsk/c0t0d0s1   -      -       swap     -     no     -

  3. Delete the ZFS swap volume.

     1. Delete the ZFS swap volume.

        For example:

        # swap -d /dev/zvol/dsk/rpool/swap

     2. Remove the ZFS swap entry from the /etc/vfstab file.

Installing an Oracle Solaris ZFS Flash Archive (6889459)

If you create and install an Oracle Solaris ZFS flash archive, install the following recommended patches:

• SPARC: 119534-24, 140914–02

• x86: 119535-24 or later, 140915-02

Limitations With Installation of ZFS Flash Archives on an Alternate Boot Environment Using Oracle Solaris Live Upgrade (7055343)

Starting with the Oracle Solaris 10 8/11 release, you can use the luupgrade command to install a ZFS flash archive to an alternate boot environment. You can also get this feature on a system running Oracle Solaris 10 9/10 by applying the relevant patches listed for CR 6868012. However, installing a ZFS flash archive has the following limitations:

• The master system on which the flash archive is created and the clone system on which the flash archive will be installed should be at the same kernel patch level. Otherwise, the flash archive installation might fail because of errors from zfs receive. For example, if a ZFS flash archive is created on a system that runs Oracle Solaris 10 8/11, ensure that the clone system is also at the Oracle Solaris 10 8/11 kernel patch level.

• On systems that run on the Oracle Solaris 9/10 release, the flash archive installation will fail if the master system on which the flash archive is created has descendant datasets under the root dataset. For example, if the master system has a separate /var dataset, the ZFS flash archive created from the master system fails to install to an alternate boot environment on a system where the current boot environment is Oracle Solaris 10 9/10. However, this limitation does not apply to systems that run on the Oracle Solaris 10 8/11 release.

Localized Installation Note

The localized Oracle Solaris installer always runs in the EUC or ISO8859 locales. Therefore, the installation log is written in EUC or ISO8859 encoding.

Workaround: While performing a localized command-line interface (CLI) installation by using a terminal window, the locale on the terminal must be either the EUC or ISO8859 locale.

x86: Oracle Solaris Flash Archive Installation Fails on Releases Before the Solaris 10 10/08 Release (6735181)

If you are installing an Oracle Solaris flash archive from a system running a release before the Solaris 10 10/08 release, the archive fails to install. Starting with the Solaris 10 10/08 release, the archive can be installed. On prior releases, the following error message is displayed:

bootadm: biodev command failed for disk:
/dev/dsk/<c0t2d0s0>.
bootadm: 1s_bootdisk(): cannot determine BIOS disk ID "hd?" for disk:
/dev/dsk/<c0t2d0s0>
bootamd: get_grubroot(): cannot get (hd?, ?,?) for menu. menu not on bootdisk:
/dev/rdsk/<c0t2d0s0>

Workaround: Choose one of the following workarounds:

• Install an Oracle Solaris flash archive from at least the Solaris 10 10/08 release.

• If you need to install an Oracle Solaris flash archive from a previous release, boot from the previous release and extract the archive.

Some Asian Locales Cannot Be Used for JumpStart Installation (6681454)

The following Asian locales cannot be used while installing the Oracle Solaris OS with JumpStart: th_TH.ISO8859-11, th_TH.TIS620, ko_KR.EUC, ko_KR.UTF-8, zh_TW.EUC, zh_CN.EUC, zh_CN.GBK, and zh_CN.UTF-8 . While setting locales in the sysidcfg file using the system_locale keyword, the following error message is displayed:

xx_xx.xxxxx is not a valid system locale

The JumpStart installation is stopped, and the interactive installation starts.

Workaround: Use shorter locale names such as th_TH, ko, ko.UTF-8, zh_TW, zh, zh.GBK, and zh.UTF-8, instead of longer locale names.

PRODRM Has Problems Deleting prodreg Entry for Trusted Extensions (6616592)

While upgrading Trusted Extensions from the Solaris 10 11/06 or Solaris 10 8/07 release to the Solaris 10 10/08, Solaris 10 5/09, Solaris 10 10/09, or Oracle Solaris 9/10 release, the prodreg entry for Trusted Extensions is not removed. No error message is displayed.

Workaround: After upgrading Trusted Extensions to the current release, remove the prodreg entry manually as follows:

# prodreg unregister -f -r -u "Solaris Trusted Extensions" -i 1

Upgrade Detailed Patch Analysis Panel Not Scrollable (6597686)

During an Oracle Solaris upgrade, if you select Detailed Analysis to view which patches will be removed, the panel that displays the patches is not scrollable. The complete list of patches to be removed cannot be viewed.

Workaround: Run the analyze_patches scripts manually as follows:

# cd <cdrom>/Solaris_10/Misc
# ./analyze_patches -R rootdir -N netdir -D databasedir

The command options are:

-R rootdir

rootdir is the root of the installed system. The default root directory is /.

-N netdir

netdir is the path to the root of the OS image to be installed and is also the path to the directory that contains the Solaris_10_606 directory. /cdrom/cdrom0 is the default path. You must use this option if you are running patch_analyzer from an NFS mount point.

-D databasedir

If the script is called from a directory other than the /Misc directory in the OS image, the program cannot find the database it uses for patch analysis. Use the -D option to supply the path to the database. Without this database, which is located in the Solaris_10_606/Misc/database directory in the OS image, the script will not run correctly.

Linux Partition Does Not Display on the GRUB Menu After Installation of the Oracle Solaris OS (6508647)

If Linux is installed on your system and you installed the Oracle Solaris OS in a separate partition, the Linux partition does not display in the GRUB menu. No error message is displayed.

Workaround: Edit the GRUB menu's menu.lst file to add Linux to the GRUB menu. Perform the following steps:

1. Boot the Oracle Solaris OS.

2. Edit the menu.lst file at /boot/grub/menu.lst. For more information, see the System Administration Guide: Basic Administration.

x86: Invalid /sbin/dhcpinfo Error During Installation (6332044)

If you install the Solaris 10 10/09 OS on an x86 based system, the following error message is displayed:

/sbin/dhcpinfo: primary interface requested but no primary interface is set

The error does not affect the installation, and the installation succeeds.

Workaround: Ignore the error message.

x86: System Fails to Boot After JumpStart Installation (6205478)

If you use the JumpStart installation method to install the Oracle Solaris OS on an x86 based system and you explicitly configure slice 2 as the overlap slice in the profile, an error occurs. The system does not reboot successfully after the installation is completed. The following error message is displayed:

Cannot find Solaris partition

This failure occurs because the overlap slice 2 (c0t0d0s2, for example) is set to begin at cylinder 1 rather than cylinder 0.

Workaround: In the JumpStart profile, remove the filesys keyword entry which configures slice 2 as the overlap slice. For example, you would remove a keyword entry that is similar to the following:

filesys c0t0d0s2 all overlap

After you remove the entry, perform the JumpStart installation.