|Skip Navigation Links|
|Exit Print View|
|Oracle Solaris 11.1 Release Notes Oracle Solaris 11.1 Information Library|
The following issues might occur during or after the installation of Oracle Solaris 11.1.
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 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 vdev in the root pool.
Note - On x86 systems, if necessary, allocate additional space to the Solaris2 partition.
Disable the need for a dump and swap volume to be allocated. In the AI manifest, specify the value true for the nodump and noswap attributes in the <logical> tag of the <target> section. For example:
<logical noswap="true" nodump="true"> </logical>
Define the zpool and allocate smaller swap and dump sizes in the manifest:
<target> <disk whole_disk="true" in_zpool="rpool"> <disk_keyword key="boot_disk"/> </disk> <logical> <zpool name="rpool" root_pool="true"> <zvol name="swap" use="swap"> <size val="2gb"/> </zvol> <zvol name="dump" use="dump"> <size val="4gb"/> </zvol> </zpool> </logical> </target>
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:
<target> <disk whole_disk="true" in_zpool="rpool"> <disk_keyword key="boot_disk"/> </disk> <logical noswap="true"> <zpool name="rpool" root_pool="true"> <zvol name="dump" use="dump"> <size val="4gb"/> </zvol> </zpool> </logical> </target>
For more information about how to edit the AI manifest, refer to the ai_manifest(4) man page.
The default AI manifest for an install service created from an Oracle Solaris 11 AI image contains the following entry in the <software_data> section:
This entry has the effect of installing the latest release of the Oracle Solaris operating system (OS) that is available from the publisher specified in the AI manifest.
If the package repository referenced by the Oracle Solaris 11 AI manifest contains both Oracle Solaris 11 and Oracle Solaris 11.1 system packages, the Oracle Solaris 11 install service installs the Oracle Solaris 11.1 OS instead of Oracle Solaris 11, because that is the latest release of the Oracle Solaris OS available in the repository.
For i386 AI client installations using an Oracle Solaris 11 install service where the referenced package repository contains Oracle Solaris 11.1 system packages, the installation starts but then fails with a PlanCreationException error because of intra-release incompatibilities. The following error message will be displayed:
Reason: Installed version in root image is too old for origin dependency
For SPARC AI client installations, the installation does not fail but installs Oracle Solaris 11.1 rather than Oracle Solaris 11.
Note - Installing Oracle Solaris 11.1 from an Oracle Solaris 11 install service is not a supported operation.
Workaround: To ensure that an Oracle Solaris 11 AI install service continues to install the latest version of Oracle Solaris 11 in the specified publisher's repository, perform the following steps:
Determine the manifest to modify.
$ installadm list -n svcname -m
$ installadm list -n default-i386 -m
Export the manifest to a file.
$ pfexec installadm export -n svcname \ -m manifest-name -o /path-to-save-manifest
$ pfexec installadm export -n default-i386 \ -m orig_default -o /home/me/orig_default.xml
Modify the <name>pkg:/entire@latest</name> line in the saved manifest to specify the Oracle Solaris 11 release.
The following example specifies the latest version of the Oracle Solaris 11 release that is available in the referenced repository:
The version string 0.5.11,5.11-0.175.0 specifies the Oracle Solaris 11 release. The version string 0.5.11,5.11-0.175.1 specifies the Oracle Solaris 11.1 release.
To install a specific version of the Oracle Solaris 11 release, make the version string more specific. The following example uses the original Oracle Solaris 11 11/11 release:
Obtain the value of the publisher origin in the saved manifest.
The following example is the value from the default AI manifest:
Verify that the version you want to install is available in the referenced repository.
$ pkg list -afvg http://pkg.oracle.com/solaris/release email@example.com,5.11-0.175.0
Update the manifest in the service.
$ pfexec installadm update-manifest -n svcname \ -m manifest-name -f /path-to-save-manifest
$ pfexec installadm update-manifest -n default-i386 \ -m orig_default -f /home/me/orig_default.xml
During the installation of Oracle Solaris 11.1 on a SPARC T4 server, the following warning might be displayed on the console:
usbecm0: object not found
This warning is not fatal and does not affect the normal operation of the system.
Workaround: Perform the following steps:
Identify the Fault Management Resource Identifier (FMRI).
# fmadm faulty
Clear the faults and the Fault Management (FM) log file.
# fmadm acquit <fmri>
# fmadm flush <fmri>
For more information, see the “Repairing Faults or Defects" chapter in the Oracle Solaris Administration: Common Tasks guide.
The zoneadm install command has a -c option that can take a directory as a parameter. This directory can contain subdirectories with system configuration profiles in them.
Due to the flattening of the directory structure, if files with the same name are within the directory structure, then only one of those files is copied to the installed zone.
For example, assume that you have the following directory tree:
directory-name/profiles1/sc_profile.xml directory-name/profiles2/sc_profile.xml directory-name/profiles3/sc_profile.xml
Assume that you then run the following zoneadm install command:
# zoneadm -z zone install -c directory-name
The files in the directory structure are copied to the new zone as if you issued the following commands in sequence:
# cp directory-name/profiles1/sc_profile.xml \ zoneroot/etc/svc/profile/site/sc_profile.xml # cp directory-name/profiles2/sc_profile.xml \ zoneroot/etc/svc/profile/site/sc_profile.xml # cp directory-name/profiles3/sc_profile.xml \ zoneroot/etc/svc/profile/site/sc_profile.xml
As a result, each subsequent copy overwrites the previous copy, leaving only one file. The system therefore is not configured properly after installation.
Workaround: Ensure that each profile, regardless of its location in the directory tree, has a unique name so that profiles will not overwrite each other when copied. For example, assume the following directory structure:
directory-name/profiles1/sc_profile_a.xml directory-name/profiles2/sc_profile_b.xml directory-name/profiles3/sc_profile_c.xml
Executing the zoneadm command copies the files to the zone as follows:
zoneroot/etc/svc/profile/site/sc_profile_a.xml zoneroot/etc/svc/profile/site/sc_profile_b.xml zoneroot/etc/svc/profile/site/sc_profile_c.xml
The configuration profiles that Automated Installer servers provide to install clients are openly accessible over the network through the web server. Hence, any encrypted passwords that are provided as part of the configuration profiles are not secure.
Workaround: Choose one of the following workarounds:
Use the IP Filter feature, which helps limit access to the Automated Installer web server port to only specific networks or clients.
For more information about the IP Filter feature, see Packet Filtering in Oracle Solaris 11 Security Guidelines.
During the first boot after installation of a system, log in and change the passwords that were configured by using the Automated Installer. For security, boot the system to single-user mode.
On SPARC based systems, add the -s option to the boot command.
On x86 systems, edit the GRUB menu interactively, and append the -s option to the kernel$ command.
Automated Installer manifests are modified from a Derived Manifest script by using the aimanifest command.
When adding a new element or a subtree to an AI manifest using the add or load subcommand of aimanifest, the new element or subtree root might be misplaced among its sibling elements. If all of the following conditions are met, the new element or the root of the subtree is added to the end of the list of sibling elements, even if that is not the correct place:
Other elements exist under the parent where the new element would be added.
Other elements with the same tag are not present under the parent where the new element would be added.
No elements that follow the new element are present.
As a result, the manifest validation might fail. You might see a similar error message when you run AI or in the /system/volatile/install_log file as a failure of the derived manifest module (DMM) checkpoint:
16:48:04: aimanifest: INFO: command:add, path:/auto_install/ai_instance/ target/logical/zpool[@name=rpool]/filesystem@name, value:zones 16:48:04: aimanifest: INFO: cmd:success, validation:Fail, node:/auto_install/ai_instance/ target/logical/zpool/filesystem 16:48:05 Derived Manifest Module: script completed successfully 16:48:05 Derived Manifest Module: Manifest header refers to no DTD. 16:48:05 Derived Manifest Module: Validating against DTD: /usr/share/install/ai.dtd.1 16:48:05 Validation against DTD /usr/share/install/ai.dtd.1] failed 16:48:05 /system/volatile/manifest.xml:6:0:ERROR:VALID:DTD_CONTENT_MODEL: Element zpool content does not follow the DTD, expecting (vdev* , filesystem* , zvol* , pool_options? , dataset_options? , be?), got (be filesystem ) 16:48:05 Derived Manifest Module: Final manifest failed XML validation 16:48:05 Error occurred during execution of 'derived-manifest' checkpoint. 16:48:05 Aborting: Internal error in InstallEngine ERROR: an exception occurred. Derived Manifest Module: Final manifest failed XML validation
Workaround: Assemble the AI manifest in a different order or with a different series of add or load subcommands such that new elements or subtrees are added in their proper order. The order is determined by the DTD files in the /usr/share/install directory. The following DTD files are used to validate AI manifests:
Add all the origin elements before adding mirror elements. For example, if you are setting up the origin and mirror elements of a publisher, the software.dtd.1 file has the following line, which indicates that mirror elements must come after origin elements:
<!ELEMENT publisher (origin+, mirror*)>
If you install the Oracle Solaris OS on a dual-path FC boot disk, the installation fails with the following errors:
2011-08-16 18:41:38,434 InstallationLogger.target-selection DEBUG Traceback (most recent call last): File "/usr/lib/python2.6/vendor-packages/solaris_install/auto_ install/checkpoints/target_selection.py", line 3419, in execute self.select_targets(from_manifest, discovered, dry_run) 2011-08-16 18:41:38,642 InstallationLogger INFO Automated Installation Failed 2011-08-16 18:41:38,693 InstallationLogger INFO Please see logs for more information 2011-08-16 18:41:38,743 InstallationLogger DEBUG Shutting down Progress Handler
Workaround: Disconnect one of the dual-path FC cables.
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 0.0.0.0/0 # 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 Naming and Directory Services in Oracle Solaris 11.1.
When using the text installer on an equivalent of a physical console such as a web-based remote keyboard, video monitor, mouse, or a 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.
The text installer does not allow installation of Oracle Solaris to a slice within an existing Solaris2 partition. This issue occurs only if you have selected to preserve data on another slice or set of slices within that same partition.
The Select Slice in Fdisk Partition screen of the text installer displays one existing slice in the Solaris2 partition as having the type rpool. You cannot use the F5 key to change the type of an unused slice to rpool.
Unless you want to destroy data on the existing rpool slice, you have to quit the installer. This issue does not affect other changes in your system.
Workaround: To use the text installer, you must install Oracle Solaris onto a separate disk. You can install into another slice with free space in an existing Solaris2 partition using the Automated Installer (AI) with a customized manifest. The customized AI manifest specifies the slice to be used for the installation.
For example, to install Oracle Solaris onto an s11-rpool root pool on slice 7 of an existing Solaris2 partition, specify the following in the targets section of the customized AI manifest:
<target> <disk> <disk_name name="c3d0" name_type="ctd"/> <partition action="use_existing_solaris2"> <slice name="7" in_zpool="s11-rpool"> <size val="6144mb"/> </slice> </partition> </disk> <logical> <zpool name="s11-rpool" is_root="true"> <filesystem name="export" mountpoint="/export"/> <filesystem name="export/home"/> <be name="solaris"/> </zpool> </logical> </target>
sysconfig and text installer applications might terminate unexpectedly from Timezone screens if you perform either of these operations:
Press Ctrl + L.
Press F9 and select the Cancel button.
This issue occurs only when you have selected one of the following time zone regions:
Note - Any selections you made before the applications are terminated are not saved.
Workaround: To avoid this behavior, do not attempt to quit these applications from the Timezone screens. Use the following workarounds:
If you are running the text installer, you will automatically return to the installation main menu. From the main menu, select the Install Oracle Solaris option to restart the text installer.
If you are running the sysconfig application, do the following:
Log in as root with an empty password.
Reboot to resume the interactive configuration process from the beginning.
If you are installing Oracle Solaris by using interactive installers or the sysconfig utility, the installation might fail if non-ASCII characters are specified in the Your Real Name field in the Users screen.
The installation might fail or characters might not be displayed correctly in the steps that follow after specifying the non-ASCII characters in the Users screen.
Workaround: Use only ASCII characters in the Real Name field.
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:
Install Oracle Solaris 11.1 using the text installer or Automated Installer (AI).
Use the pkg command to install the solaris-desktop group package.
Install the VirtualBox guest tools that include the VirtualBox Xorg native driver.
For instructions about installing the solaris-desktop group package, see Adding Software After Live Media Installation in Installing Oracle Solaris 11.1 Systems.
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:// $serverIP:5555//install/images/s11-x86,install_service=s11-173-x86,install_svc_address= $serverIP:5555 loading '/s11-173-x86/platform/i86pc/kernel/$ISADIR/unix -B install_media=http:// $serverIP:5555//install/images/s11-x86,install_service=s11-173-x86,install_svc_address= $serverIP:5555' 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:
Use the bge driver instead of the nge driver.
Change the BIOS version to version 1.0.9.
When you install Oracle Solaris on Oracle's Sun Fire x4170m3 and x4270m3 servers, the installation might crash intermittently with a bad marshal data error. The reason for this failure is a corrupted solaris.zlib file in the DVD mounted image.
Due to the corrupted file, the read operation will fail on some of the files in the lofi file device in the mounted ISO image. The system displays several error messages during installation.
Workaround: Perform the following steps to disable Virtualization Technology for Directed-IO (VT-d).
Restart or power on the server.
Press the F2 key when prompted to enter the BIOS Setup utility.
In the BIOS IO Menu screen, select IO > IO Virtualization and disable the VT-d setting.
To enable VT-d for the other EHCI controllers after installing Oracle Solaris, perform the following steps:
Add the following line to the /kernel/drv/ehci.conf file:
Reboot the system.
Enable VT-d in the BIOS Setup utility.