Go to main content

Oracle® Solaris 11.3 Release Notes

Exit Print View

Updated: October 2017

Issues When Installing Oracle Solaris 11.3

The following issues might occur during or after the installation of Oracle Solaris 11.3.

Automated Installer Fails to Install on Systems With High Memory and Low Disk Space Allocation (15741363)

When installing Oracle Solaris by using the Automated Installer (AI), the installation might fail if the system has more physical RAM than disk space. The space allocated to swap and dump devices might reduce the available space for installing the OS. The following error message might be displayed:

ImageInsufficentSpace: Insufficient disk space available (8.84 GB) for
estimated need (9.46 GB) for Root filesystem

Workaround: Choose one of the following workarounds:

  • If not limited by the size of the disk, allocate more space to the slice being used as a virtual device (vdev) in the root pool.

    Note -  On x86 systems, if necessary, allocate additional space to the Solaris2 partition.
  • Disable the need for a swap volume to be allocated. In the AI manifest, specify the value true for the noswap attribute in the <logical> tag of the <target> section. For example:

    <logical noswap="true">
  • Define the zpool and allocate smaller swap and dump sizes in the manifest.

    	<disk whole_disk="true" in_zpool="rpool">
    		<disk_keyword key="boot_disk"/>
    		<zpool name="rpool" root_pool="true">
    			<zvol name="swap" use="swap">
    				<size val="2gb"/>
    			<zvol name="dump" use="dump">
    				<size val="4gb"/>
  • Disable allocation of one swap or dump device, and allocate a specific size to the remaining device (dump or swap). The following example shows how to disable swap and add a 4 GB dump size:

    	<disk whole_disk="true" in_zpool="rpool">
    		<disk_keyword key="boot_disk"/>
    	<logical noswap="true">
    		<zpool name="rpool" root_pool="true">
    			<zvol name="dump" use="dump">
    				<size val="4gb"/>

For more information about how to edit the AI manifest, refer to the ai_manifest (4) man page.

Automated Installer Fails to Match Target Disks When Using Dual-Path Boot Disk (15735929)

If you install the Oracle Solaris OS on a dual-path FC boot disk, the installation fails with the following errors:

17:22:08 Error occurred during execution of 'target-selection' 
17:22:08 100% None
17:22:09 Failed Checkpoints:
17:22:09 target-selection
17:22:09 Checkpoint execution error:
17:22:09 Unable to locate the disk
		on the system.
17:22:09 Automated Installation Failed. See install log at 
Automated Installation failed
Please refer to the /system/volatile/install_log file for details.

Workaround: Disconnect one of the dual-path FC cables.

SPARC: 64-bit: Automated Installer Fails Due to Unlabeled Dual-Path FC Boot Disks (15656484)

On SPARC systems, if you install the Oracle Solaris OS on a dual-path FC boot disk, the installation fails with the following errors:

Automated Installation failed 
Please refer to the /system/volatile/install_log file for details 

Apr 19 23:12:12 ssra00u23.us.abc.com svc.startd[9]: 
application/auto-installer:default failed fatally: transitioned to 
maintenance (see 'svcs -xv' for details)

Workaround: Prior to installing Oracle Solaris, format disks by using the boot net -s command, label the disks, and then proceed with the installation.

Multiple AI Service Name Conflicts on AI Servers (15713975)

On AI servers configured to serve multiple networks, the mdns daemon might warn that identical instances of AI service names are registered. The following error message might be displayed:

mDNSResponder: [ID 702911 daemon.error] 
Client application registered 2 identical instances of service some-service._
OSInstall._tcp.local. port 5555.

mDNSResponder: [ID 702911 daemon.error] 
Excessive name conflicts (10) for some-service._
OSInstall._tcp.local. (SRV); rate limiting in effect 

Note -  AI clients can still obtain the necessary information to install.

Workaround: To avoid multiple AI service name conflicts, set the exclusion or inclusion property for the svc:/system/install/server:default SMF service.

The following example shows how to set the all_services/exclude_networks and all_services/networks properties to include all the networks that were configured on the system.

# svccfg -s svc:/system/install/server:default \
setprop all_services/exclude_networks = false

# svccfg -s svc:/system/install/server:default \
delprop all_services/networks #1.#1.#1.#1/#1

# svccfg -s svc:/system/install/server:default \
delprop all_services/networks #2.#2.#2.#2/#2


# svccfg -s svc:/system/install/server:default \
addprop all_services/networks

# svcadm refresh svc:/system/install/server:default
# svcadm restart svc:/system/install/server:default

#1.#1.#1.#1/#1 and #2.#2.#2.#2/#2 are the IP addresses for the network interfaces that have been configured.

For more information about mDNS, see Administering Multicast DNS in Working With Oracle Solaris 11.3 Directory and Naming Services: DNS and NIS.

Text Installer Displays in English When Another Language Is Chosen (15744356)

When using the text installer on an equivalent of a physical console such as a web-based remote keyboard, video monitor, mouse, or VirtualBox console, the installer displays text in English even if you have chosen another language during the boot from the install media. The installer displays text in English to avoid a garbled display of non-ASCII characters.

The text installer displays localized text only on an equivalent of a serial console, for example, a service console based on SSH or telnet.

Workaround: None.

x86: Xorg VESA Driver Does Not Work on Oracle VM VirtualBox If the Extensible Firmware Interface Is Enabled (15782245)

The Xorg VESA driver does not work on Oracle VM VirtualBox if the Extensible Firmware Interface (EFI) is enabled, which means that the Live Media does not boot to Xorg. Therefore, a GUI installation is not possible.

Workaround: Perform the following steps:

  1. Install Oracle Solaris 11.3 using the text installer or Automated Installer (AI).

    For instructions about installing Oracle Solaris 11.3, see Installing Oracle Solaris 11.3 Systems.

  2. Use the pkg command to install the solaris-desktop group package.

    For instructions about installing the solaris-desktop group package, see Adding Software After a Live Media Installation in Installing Oracle Solaris 11.3 Systems.

  3. Install the VirtualBox guest tools that include the VirtualBox Xorg native driver.

Network-Based Automated Installer Fails on x2100 Platform With nge Drivers (15681004)

If you use the network-based Automated Installer to install Oracle Solaris on an x2100 platform with an nge driver, the following error message might be displayed after a duration of time:

kernel$ /s11-173-x86/platform/i86pc/kernel/$ISADIR/unix -B install_media=http://
loading '/s11-173-x86/platform/i86pc/kernel/$ISADIR/unix -B install_media=http://
module$ /s11-173-x86/platform/i86pc/$ISADIR/boot-archive
loading ' /s11-173-x86/platform/i86pc/$ISADIR/boot-archive' ...

Error 20: Mulitboot kernel must be loaded before modules

Press any key to continue...

This problem occurs in a PXE installation that uses BIOS version 1.1.1 and later when you use the x2100 BIOS with an nge driver.

Workaround: Choose one of the following workarounds to install Oracle Solaris on an x2100 platform with an nge driver:

  • Install Oracle Solaris by using one of the following methods:

    • Live Media

    • Text installer

  • Change the BIOS version to version 1.0.9.

x86: FMA Error Messages From the ixgbe Driver During Network Installation on Large System Configurations (20724005)

On some x86 systems with a large configuration, FMA error messages from the ixgbe driver about running out of MSI-X interrupt vectors during network installation might appear. The messages do not display after the installation is completed and the system is rebooted. The following error message is displayed:

The network device failed to configure a feature. A(n) unsupported
error has been detected during driver's attach context causing a(n)
config service impact while involving the device's rx_ring subsystem.

Workaround: Limit the maximum number of interrupts used by the network devices by adding the following limit to the GRUB boot arguments list at boot time:

-B ddi-msix-alloc-limit=X

X is a small number such as 1 or 2.

Note -  Setting this variable at boot time persists only until the system is rebooted and it is not a permanent setting.

Unified Archives Do Not Support Zones on Shared Storage (19627821)

Unified Archives do not support archives that contain zones on shared storage (ZOSS). Although you can use the archiveadm create command to create a recovery or clone archive containing a zone on shared storage, the resulting archive might fail to install.

Workaround: Choose one of the following workarounds:

  • To avoid installation issues with Unified Archives, you must exclude zones on shared storage in an archive.

  • When generating clone archives, you can use the –Z excluded_zone option to exclude specified zones on shared storage.

  • For recovery archives on systems containing zones on shared storage, all non-shared storage zones should be archived individually.

  • When generating a clone or recovery archive for the global zone, use the –D excluded-dataset option must be used to exclude any zones on shared storage zpools that are visible in the global zone.

SPARC: NFSv4 Cannot Determine Local Hostname Binding for Transport TCP6 (19664353, 19716203)

If you enable tcp6 in /etc/netconfig when the system does not support an IPv6 address, the following NFC warning message appears during installation:

nfs4cbd[3806]: [ID 867284 daemon.notice] nfsv4 cannot determine local hostname binding for transport
tcp6 - delegations will not be available on this transport

Workaround: None.

SPARC: stop Method of the ilomconfig-interconnect Service Is Timed Out During Shut Down (20696474)

When you reboot the system using the init 6 command, the services that are using the SVC dependency rules are shut down before the ilomconfig-interconnect service. The following message is displayed:

[ID 122153 daemon.warning] svc:/network/ilomconfig-interconnect:default: Method or service exit timed out.  Killing contract 179.

Workaround: None.

SPARC: Vanity Names Change Between Install and Reboot (20747264)

Vanity names change between the system installation and reboot. For example, during the install the following vanity names:

vanity_map=net0:e1000g0 net1:bge0 net2:bge1 net3:e1000g1

change to:

vanity_map=net0:bge0 net1:bge1 net2:e1000g0 net3:e1000g1

Workaround: None.

SPARC: A Warning Message Appears During Initial Boot Up (21503898)

During the initial boot up on SPARC systems the following warning message is displayed:

Jul 23 14:41:38 xxx.com fctl: [ID 517869 kern.warning]
WARNING: fp(3)::Topology discovery failederror=0x7

Workaround: You can safely ignore this message.

SPARC: Power Off or On Messages of One or More Hosts Is Displayed in Other Hosts (21511552)

Within an M5 chassis, ILOM messages from one or more Oracle Solaris HOSTs is displayed in the /var/adm/messages file of a different HOST. The following message is displayed:

Jul 23 15:03:41 HOST2-pd2.com SC Alert: [ID 552608
daemon.error] Power | major: Power to /HOST1 has been turned off by: Shell session, Username:root
Jul 23 15:03:41 HOST2-pd2.com SC Alert: [ID 936275
daemon.notice] SDM | minor: Power to /Servers/PDomains/PDomain_1/System
(Hardware Domain 1) has been turned off by Shell session, Username:root.
Jul 23 15:03:41 HOST2-pd2.com SC Alert: [ID 555134
daemon.notice] Audit | minor: root : Set : object =
"/Servers/PDomains/PDomain_1/HOST/power_state" : value = "off" : success

Workaround: You can safely ignore this message.

SPARC: Error Messages Are Displayed When Using the suriadm check raid Command of the mpt_sas Host Driver (21366581)

When you use the check raid option of the suriadm command of the mpt_sas host driver, the following error message is displayed:

Failing case:
# suriadm lookup-uri
/dev/dsk/c1t3E8234F87E7DC134d0 Assertion failed: parent_iport != NULL,
 file /export/builds/s11u3_23/usr/src/lib/libsuri/common/suri_devinfo.c, line 995,
    function lookup_lu_uri Abort(coredump)
Working case:
# suriadm lookup-uri
/dev/dsk/c1t3E8234F87E7DC134d0s2 dev:dsk/c1t3E8234F87E7DC134d0s2

Workaround: You can safely ignore this message.

A Warning Message Appears When estes Card Connected to SAS Storage Array LUN is Used as a Boot Device (21651971)

When any estes card (lsc driver) connected to an SAS storage array LUN is used as a boot device, the following warning message is displayed during the system boot up:

WARNING: scsi_enumeration_failed: lsc4/enclosure

Although the enclosure device fails to attach, the installation and boot are still successful.

Workaround: Add the line forceload drv/ses into /etc/system file.

SPARC: stmsboot Man Page Does Not Contain pmcs Driver Information (20157402)

The stmsboot man page does not fully document the stmsboot command because the man page does not indicate that the pmcs driver is a valid option for the command. However, the pmcs driver can be specified with the –D option. For example:

man stmsboot
System Administration Commands                        stmsboot(1M)
NAME       stmsboot - administration program for the Solaris I/O multipathing feature
SYNOPSIS       /usr/sbin/stmsboot [[-D (fp | mpt | mpt_sas | iscsi) ] -d | -e | -u] | -L | -l controller_number]

Workaround: None.