This chapter provides information and describes issues that relate to the installation of the Solaris 10 Operating System.
To see which bugs and issues are fixed and no longer apply to the Solaris 10 10/09 software, refer to Appendix A, Table of Integrated Bug Fixes in the Solaris 10 Operating System.
This section provides general information such as behavior changes in Solaris 10 OS.
The Solaris 10 10/09 release of Solaris is tested on all supported Sun systems running the latest combinations of the following:
BIOS and ILOM
SPARC Firmware and OBP and Hypervisor
For best results using the Solaris 10 10/09 release, upgrade your BIOS/Firmware to the latest release listed in the matrix at http://www.sun.com/bigadmin/patches/firmware/release_history.jsp.
The following are the minimum and recommended memory requirements for the Solaris 10 10/09 release:
For UFS root file systems:
384 Mbytes of minimum memory
512 Mbytes is the recommended memory
For ZFS root file systems:
786 Mbytes of minimum memory
1 Gbyte of memory is recommended for overall ZFS performance
Starting with the Solaris 10 8/07 release, for SPARC systems, you can upgrade the Solaris OS only from the following releases:
Solaris 8 OS
Solaris 9 OS
Solaris 10 OS
For x86 systems, you can upgrade the Solaris OS only from the following releases:
Solaris 9 OS
Solaris 10 OS
To upgrade releases previous to the Solaris 8 software to the Solaris 10 10/09 software, upgrade to any of the releases in the preceding list first. Then upgrade to the Solaris 10 10/09 release.
The Solaris 10 10/09 has been tested for compatibility with previous releases in line with Solaris's compatibility guarantee. This means that applications, including third party applications, which adhere to Solaris's published ABI will work without modification on the Solaris 10 10/09 release. For more information, see the Solaris Application Guarantee Program at http://www.sun.com/software/solaris/guarantee.jsp.
Your system might run both a Solaris OS and other products that are not part of the Solaris software. These products might be supplied by either Sun or another company. If you upgrade this system to the Solaris 10 release, make sure that these other products are also supported on the Solaris 10 OS. Depending on the status of each of these products, you can perform one of the following options:
Verify that the existing version of the product is supported on the Solaris 10 software.
Install a new version of the product that is supported on the Solaris 10 release. You might need to remove the previous version of the product prior to upgrading to the Solaris software. See the product documentation for more details.
Remove the product prior to upgrading to the Solaris 10 software.
This section contains critical installation issues that you need to be aware of before installing or upgrading to Solaris 10 OS. These issues might have an impact that would prevent installation or upgrades from completing successfully. If bugs in this section apply to your system, you might need to perform the recommended workarounds before you install or upgrade.
Starting with the Solaris 10 8/07 release, using Solaris Live Upgrade with Solaris zones is supported. For more information about this, see InfoDoc 206844 at http://sunsolve.sun.com/search/document.do?assetkey=1-61-206844-1.
For Solaris Live Upgrade to operate correctly, a limited set of patch revisions must be installed for a given OS version. Make sure you have the most recently updated patch list by consulting http://sunsolve.sun.com. The Solaris 10 10/09 release has the following Solaris Live Upgrade restrictions:
To upgrade your current Solaris 8 OS to the Solaris 10 10/09 release using Solaris Live Upgrade, perform the following steps:
For SPARC systems– Solaris Live Upgrade from the Solaris 8 release to the Solaris 10 10/09 release is supported. For step-by-step procedures on how to use Solaris Live Upgrade, see http://www.sun.com/bigadmin/features/articles/live_upgrade_patch.jsp.
For x86 systems– Solaris Live Upgrade from the Solaris 8 release to the Solaris 10 10/09 release is not supported. Instead, use the standard upgrade procedure or perform a Solaris Live Upgrade from the Solaris 8 OS to the Solaris 9 OS or to the Solaris 10 OS. Then you can perform a Solaris Live Upgrade from the Solaris 9 release or the Solaris 10 release to the Solaris 10 10/09.
Solaris Live Upgrade from Solaris 8 to the Solaris 10 5/08, Solaris 10 10/08, Solaris 10 5/09, and Solaris 10 10/09 releases is supported through http://sunsolve.sun.com/search/document.do?assetkey=1-9-250526-1.
To upgrade your current Solaris 9 OS to the Solaris 10 10/09 release using Solaris Live Upgrade, apply the following patches:
For SPARC systems– 137477-01 or later
For x86 systems– 137478-01 or later
To upgrade your current Solaris 10 OS to the Solaris 10 10/09 release by using Solaris Live Upgrade, apply the following patches:
For SPARC systems– 137321-01 or later
For x86 systems– 137322-01 or later
These patches provide the new p7zip functionality. Solaris Live Upgrade requires p7zip functionality in order to support upgrade to Solaris 10 10/09.
The minimum required patch information for the live boot environment, prior to using Solaris Live Upgrade is provided in Infodoc 206844 at http://sunsolve.sun.com/search/document.do?assetkey=1-61-206844-1.
The Solaris 10 10/09 release provides the ability to install a ZFS root file system and configure a zone root on ZFS. Typically, you can create and configure a zone root on ZFS as you wish. If you plan to use Solaris Live Upgrade with ZFS and zone configurations, review the following information:
If you want to use Solaris Live Upgrade with zone configurations that are supported in the Solaris 10 10/09 release, you will need to first upgrade your system to the Solaris 10 10/09 release by using the standard upgrade program.
Then, with Solaris Live Upgrade, you can either migrate your UFS root file system with zone roots to a ZFS root file system or you can upgrade or patch your ZFS root file system and zone roots.
You cannot migrate unsupported zone configurations from a previous Solaris 10 release directly to the Solaris 10 10/09 release.
For a detailed description of supported zone configurations to be upgraded or patched in the Solaris 10 10/09 release, see Migrating a UFS Root File System to a ZFS Root File System (Solaris Live Upgrade) in Solaris ZFS Administration Guide.
For complete instructions on setting up these configurations, see Solaris Installation and Solaris Live Upgrade Requirements for ZFS Support in Solaris ZFS Administration Guide.
Review the information in this chapter before you begin your migration to a ZFS root file system or before setting up zones on a system with a ZFS root file system. Follow the recommended procedure exactly to set up zones on a system with ZFS root file system to ensure that you can use Solaris Live Upgrade on that system.
Solaris systems that are configured with Solaris Trusted Extensions use non-global zones. Upgrading these systems is the same as upgrading a Solaris system that uses zones, and has the same issues.
ZFS Zones– Solaris systems with ZFS zones cannot currently be upgraded. For Solaris Trusted Extensions systems with ZFS zones, the alternative is to recreate the zones. To recreate the zones, perform these steps:
First, back up all the data using the tar -T command.
Then delete the zones.
Upgrade the system and reconfigure all the zones.
After all the zones are configured, restore all the data.
NFSv4 domain– After upgrade, when you bring up each labeled zone, you will be prompted for the NFSv4 domain. To avoid this prompt, before upgrade add the correct NFSMAPID_DOMAIN value in the /etc/default/nfs file in each labeled zone. For more information, see CR 5110062.
Live Upgrade– The following bug affects Live Upgrade of Solaris systems with zones:
These bugs will also affect the Live Upgrade of systems that are configured with Solaris Trusted Extensions. The workarounds are also the same.
Name Service– If your system was configured at install time to use a name service that is different from the name service being used during upgrade, then the global zone may use the correct name service after boot.
For example, if you specified NIS as the name service to use during system install, but the system was later converted to be an LDAP client, the luactivate boot can revert to using NIS as the name service for the global zone. This is due to CR 6569407.
The workaround is to adjust the name_service.xml symbolic link in the /var/svc/profile directory to point to the correct xml file corresponding to the name service currently in use. For example, if NIS was specified as the name service during install, then name_service.xml will be a symbolic link to ns_nis.xml. If the system was subsequently converted to being an LDAP client, and LDAP was the name service in use during Live Upgrade, then run the following command:
# ln -fs ns_ldap.xml name_service.xml |
This should be done before starting Live Upgrade or before running the lucreate command. However, if you did not run this command before lucreate, then perform the following steps after running the luactivate command:
lumount the new boot environment:
# lumount <BE_name> |
Change to the /var/svc/profile directory of the boot environment:
# cd /.alt.<BE_name>/var/svc/profile |
Link the name_service.xml link as appropriate. For example:
# ln -fs ns_ldap.xml name_sevice.xml |
luumount the boot environment:
# luumount <BE_name> |
If the system is booted without performing the steps mentioned above, you will need to manually start the appropriate name service-related SMF client services.
The procedures for using patchadd with the -C destination specifier to patch a miniroot on SPARC and x86 machines have changed. You must now unpack the miniroot, apply patches, then repack the miniroot.
See the following for the detailed steps:
Starting with the Solaris 10 8/07 release, the Solaris Data Encryption Supplement packages are included by default with the Solaris 10 OS software. You no longer need to install and download these packages.
The following patches are applied to resolve problems that were reported in CR 6277164 and CR 6214222:
Patch ID 119366-05 for SPARC based systems
Patch ID 119367-05 for x86 based systems
The sections that follow provide further steps that you must perform to completely resolve the reported problems. For more information, read the Special Install Instructions section of the patch README for these patches.
Systems with an elx or a pcelx network interface card (NIC) fail to install. During the configuration of the NIC, the following error message might be displayed:
WARNING: elx: transmit or jabber underrun: d0<UNDER, INTR, CPLT> |
See the elxl(7D) or pcelx(7D) man page for more information.
Workaround: Install and run on systems that do not have elx or pcelx NICs.
The default size of the /var file system might be insufficient if the /var file system is located on a separate slice.
You must manually specify a larger slice size for the /var file system.
If the /var file system is not on a separate slice or partition, this problem does not occur.
Workaround: Choose one of the following workarounds.
If you are using the Solaris installation program GUI, follow these steps.
Begin the installation.
From Select Type of Install, select Custom Install.
The Solaris installation program displays several screens that enable you to customize the software localizations, products, and disk layout that you want to install.
From Lay Out File Systems, select Modify.
The disk layout screen is displayed.
Type /var in the File System column for a specific slice, then click Apply.
The installation program suggests a default size for the /var file system.
Edit the Size column entry for the /var file system to twice the disk space size.
For example, if the installation program assigns 40 Mbytes of space, change the Size value to 80.
Complete the installation.
If you are using the Solaris installation program's text installer, follow these steps.
Begin the installation.
From Select Type of Install, select Custom Install.
The Solaris installation program displays several screens that enable you to customize the software localizations, products, and disk layout that you want to install.
From Lay Out File Systems, select Auto Layout.
The disk layout screen is displayed.
Type /var in the File System column for a specific slice.
The installation program suggests a default size for the /var file system.
Press F4_Customize to customize the size of the /var file system.
Edit the Size column entry for the /var file system to twice the disk space size.
For example, if the installation program assigns 40 Mbytes of space, change the Size value to 80.
Complete the installation.
If you are using the custom JumpStart program, use the filesys profile keyword to set the size of the /var file system. The following example sets the size of the /var file system on slice 5 to 256 Mbytes.
filesys c0t0d0s5 256 /var |
The Solaris 10 software includes a feature that enables you to install large partitions. The system BIOS must support logical block addressing (LBA). BIOS Version GG.06.13 does not support LBA access. The Solaris boot programs cannot manage this conflict. This issue can also affect other HP Vectra systems.
If you perform this upgrade, your HP system can no longer boot. Only a blank black screen with a flashing underscore cursor is displayed.
Workaround: Do not upgrade HP Vectra XU Series systems with the latest BIOS Version GG.06.13 to the Solaris 10 release. This version no longer supports these systems.
You can still boot your system by using the boot diskette or boot CD because the boot paths do not use the hard disk code. Then select the hard disk as your bootable device instead of the network or CD-ROM drive.
On SPARC based systems, Solaris 10 OS runs in 64–bit mode only. Some Sun4UTM systems might need to be updated to a higher level of OpenBootTM firmware in the flash PROM to run the OS in 64-bit mode. The following systems might require a flash PROM update:
UltraTM 2
Ultra 450 and Sun EnterpriseTM 450
Sun Enterprise 3000, 4000, 5000, and 6000 systems
The following table lists the UltraSPARC systems and the minimum firmware versions that are required to run the 64–bit Solaris 10 OS. System type is the equivalent of the output of the uname -i command. You can determine which firmware version you are running by using the prtconf -V command.
Table 1–1 Minimum Firmware Versions Required to Run 64–Bit Solaris Software on UltraSPARC Systems
System Type From uname -i |
Minimum Firmware Version From prtconf -V |
---|---|
SUNW,Ultra-2 |
3.11.2 |
SUNW,Ultra-4 |
3.7.107 |
SUNW,Ultra-Enterprise |
3.2.16 |
If a system is not listed in the previous table, the system does not need a flash PROM update. For instructions to perform a flash PROM update, see any edition of the Solaris 8 Sun Hardware Platform Guide at http://docs.sun.com.
Upgrading firmware on both SPARC and x86 systems can lead to significant performance improvements. See the Firmware section on the BigAdmin Patching Hub at http://www.sun.com/bigadmin/patches/overview.jsp. See also, the FAQ at http://www.sun.com/bigadmin/patches/firmware/faq.jsp.
Solaris Management Console 2.1 software is not compatible with Solaris Management Console 1.0, 1.0.1, or 1.0.2 software. If you are upgrading to the Solaris 10 release, and you have Solaris Management Console 1.0, 1.0.1, or 1.0.2 software installed, you must first uninstall the Solaris Management Console software before you upgrade. Solaris Management Console software might exist on your system if you installed the SEAS 2.0 overbox, the SEAS 3.0 overbox, or the Solaris 8 Admin Pack.
Workaround: Choose one of the following workarounds:
Before you upgrade, use the /usr/bin/prodreg command to perform a full uninstall of Solaris Management Console software.
If you did not uninstall Solaris Management Console 1.0, 1.0.1, or 1.0.2 software before you upgraded to the Solaris 10 release, you must first remove all Solaris Management Console 1.0, 1.0.1, or 1.0.2 packages. Use the pkgrm command for package removal instead of the prodreg command. Carefully follow the order of package removal. Complete the following steps:
Become superuser.
Type the following command:
# pkginfo | grep “Solaris Management Console“ |
If the description does not start with “Solaris Management Console 2.1,” the package names in the output identify a Solaris Management Console 1.0 package.
Use the pkgrm command to remove all instances of Solaris Management Console 1.0 packages in the following order:
Do not remove any package that has “Solaris Management Console 2.1” in its description. For example, SUNWmc.2 might indicate Solaris Management Console 2.1 software.
If the pkginfo output displays multiple versions of Solaris Management Console 1.0 packages, use the pkgrm command to remove both packages. Remove the original package. Then, remove the package that has been appended with a number. For example, if the SUNWmcman and SUNWmcman.2 packages appear in the pkginfo output, first remove the SUNWmcman package and then remove the SUNWmcman.2 package. Do not use the prodreg command.
# pkgrm SUNWmcman # pkgrm SUNWmcapp # pkgrm SUNWmcsvr# pkgrm SUNWmcsvu # pkgrm SUNWmc # pkgrm SUNWmcc # pkgrm SUNWmcsws |
In a terminal window, type the following command:
# rm -rf /var/sadm/pkg/SUNWmcapp |
The Solaris Management Console 2.1 software should now function properly. For future maintenance, or if the Solaris Management Console 2.1 software does not function properly, remove the Solaris Management Console 2.1 software. Reinstall the software by completing the following steps:
Use the pkgrm command to remove all Solaris Management Console 2.1 packages and dependent packages in the following order:
If your installation has multiple instances of Solaris Management Console 2.1 packages, such as SUNWmc and SUNWmc.2, first remove SUNWmc, and then SUNWmc.2 . Do not use the prodreg command.
# pkgrm SUNWpmgr # pkgrm SUNWrmui # pkgrm SUNWlvmg # pkgrm SUNWlvma # pkgrm SUNWlvmr # pkgrm SUNWdclnt # pkgrm SUNWmga # pkgrm SUNWmgapp # pkgrm SUNWmcdev # pkgrm SUNWmcex # pkgrm SUNWwbmc # pkgrm SUNWmc # pkgrm SUNWmcc # pkgrm SUNWmccom |
Insert the Solaris 10 Software - 4 CD into your CD-ROM drive. Type the following in a terminal window:
# # cd /cdrom/cdrom0/Solaris_10/Product # pkgadd -d . SUNWmccom SUNWmcc SUNWmc SUNWwbmc SUNWmcex SUNWmcdev \ SUNWmgapp SUNWmga SUNWdclnt SUNWlvmr SUNWlvma SUNWlvmg SUNWpmgr \ SUNWrmui |
All previous Solaris Management Console versions are removed. The Solaris Management Console 2.1 software is now functional.
On certain occasions, the utility for BIOS devices (/sbin/biosdev) might fail and prevent a successful installation or upgrade. The failure can occur under either of the following circumstances:
Patch ID 117435-02 was applied, but the system was not rebooted.
The system contains two or more identical disks that have identical fdisk partitions.
The following error message is displayed:
biosdev: Could not match any!! |
Workaround: Make sure that you reboot the system after applying Patch ID 117435-02. Ensure that identical disks to be used in the installation or upgrade are configured with different fdisk-partition layouts.
The following example is based on a system that has two disks with identical fdisk-partition layouts. To change the layouts, perform the following steps.
Become superuser.
Start the disk maintenance utility.
# format |
A list of available disks in the system is displayed.
To select the disk whose fdisk partition you want to change, type the disk's number.
From the list of Format options, select fdisk.
The disk's partition information and a list of fdisk options are displayed.
To change the disk's layout, choose one of the following:
To specify a different active partition, press 2.
To add another disk partition, press 1.
To delete an unused partition, press 3.
To save your changes and exit the fdisk menu, press 5.
To exit the disk maintenance utility, select Quit from the Format options.
Reboot the system.
After the system reboots, verify that the error message no longer appears. As superuser, type the following command:
# /sbin/biosdev |
If the error message is still generated, repeat the procedure but select a different option in Step 5.
If the system contains other identical disks with identical fdisk-partition layouts, repeat Steps 1-9 on these disks. Otherwise, you can proceed with your Solaris installation or upgrade.
Starting with the current Solaris release, a Solaris Flash archive cannot be properly created when a non-global zone is installed. The Solaris Flash feature is not currently compatible with the Solaris containers (zones) feature.
Do not use the flar create command to create a Solaris Flash archive in these instances:
In any non-global zone
In the global zone if there are any non-global zones installed
If you create a Solaris Flash archive in such an instance, the resulting archive might not install properly when the archive is deployed.
Workaround: It might be possible to create a Solaris Flash archive of a system that has installed zones if they are all halted. For more information, see http://opensolaris.org/os/community/zones/faq/flar_zones/.
The DVD combo-drive firmware in a Sun Java Workstation 2100Z might cause a system panic. The panic occurs when you boot the workstation from the Solaris 10 Operating System DVD. After the kernel banner is displayed, the following message is very quickly flashed:
panic[cpu0]/thread=fec1be20: mod_hold_stub: Couldn't load stub module sched/TS_DTBL fec25cb0 genunix:mod_hold_stub+139 (fec04088, 63, fea11) fec25cc4 unix:stubs_common_code+9 (1, 8, fec026e4) fec25ce4 unix:disp_add+3d (fec026dc) fec25d00 genunix:mod_installsched+a4 (fef01530, fef01518) fec25d20 genunix:mod_install+2f (fef01518, fec25d3c,) fec25d2c TS:_init+d (0, d6d89c88, fec25d) fec25d3c genunix:modinstall+d9 (d6d89c88) fec25d50 genunix:mod_hold_installed_mod+2e (d6d77640, 1, fec25d) fec25d7c genunix:modload+ac (fec026c4, fec26c4) fec25d98 genunix:scheduler_load+3d (fec026c4, fec026dc) fec25db4 genunix:getcid+50 (fec026c4, fec28514) fec25dcc unix:dispinit+df (fec25ddc, fe814ba9) fec25dd4 unix:startup_modules+d5 (fec25dec, fe8cac37) fec25ddc unix:startup+19 (fe800000, 166130, 7) fec25dec genunix:main+16 () |
Then the system automatically resets.
Workaround: Choose one of the following options:
Workaround 1: Modify some BIOS configuration settings. This temporary workaround enables a Solaris 10 installation to be completed. However, this method might cause poor read-DVD performance. Follow these steps:
During system boot, press F2 at the prompt to enter the setup.
The screen displays attachment-type options similar to the following example:
Primary Master [ ] Primary Slave [ ] Secondary Master [CD-ROM] Secondary Slave [ ] |
Choose the DVD drive's attachment type by selecting the attachment type for CD-ROM.
The screen might display more than one attachment type for CD-ROM, for example, if your system has multiple optical drives. In such cases, you might need to open the system case to determine the DVD drive's point of attachment. Make sure that you select the correct attachment type that applies to the DVD drive.
After selecting the correct CD-ROM attachment type, press Enter.
The next screen appears with Type:[Auto] automatically selected.
Press the spacebar twice to change the selection to Type:[CD-ROM].
Use the arrow keys to select Transfer Mode.
Press Enter to display a list of other Transfer Mode options.
Use the arrow keys to select Standard, then press Enter to accept your selection.
Press F10 to save the configuration changes and exit BIOS setup.
The system restarts.
Workaround 2: Update the DVD combo drive's firmware to v1.12. This option requires your DVD combo drive to be attached to a system that is running Microsoft Windows. Follow these steps.
Remove your DVD combo drive from the Sun Java Workstation 2100z. See the workstation's user's guide for steps to remove the drive properly.
Connect the drive to a system that is running Microsoft Windows. Make sure to change the drive's master and slave jumper settings, if needed.
Go to AOpen's download center at http://download.aopen.com.tw/default.aspx.
Search for your DVD drive's firmware by using the following information:
Product: Combo drives
Model: COM5232/AAH
Categories: Firmware
Download and install the firmware version R1.12.
Reinstall the drive on the workstation. If needed, restore the original master and slave jumper settings.
Newer versions of the firmware might already be available at the site. Sun's tests confirm that the v1.12 release resolves the panic issue. Sun cannot confirm whether newer firmware revisions after v1.12 similarly resolve the problem.
The serial console (ttya) on the following Sun Fire systems does not work by default:
Sun Fire V20z
Sun Fire V40z
Sun Fire V60x
Sun Fire V65x
To use the serial console, you must manually configure the system's BIOS.
Workaround: This workaround requires your system to have a Sun keyboard and a display monitor. Follow these steps:
Boot the machine.
During system boot, press F2 at the prompt to access the Phoenix BIOS.
Under Peripherals, change the comm port from disabled to enabled.
Save the configuration and boot the system.
Use the eeprom command to change input-device and output-device to ttya.
Pressing the Stop and N keys at system boot to reset the low-level firmware to default settings does not work on these systems.
The Solaris installation GUI program might fail on a system with an existing x86 boot partition. The failure occurs if the existing x86 boot partition was created with the Solaris text-based installer. The following error message is displayed.
Default layout will not work on this system. Error: Error: ERROR: Could not create explicit fdisk partition on c0t0d0, requested cylinders 14581 - 14597 in use by fdisk partition 1 Error: Error: ERROR: System installation failed Pfinstall failed. Exit stat= java.lang.UNIXProcess@a89ce3 2 artition on c0t0d0, requested cylinders 14581 - 14597 in use by fdisk partition 1 ERROR: System installation failed |
Workaround: Choose one of the following workarounds.
Workaround 1: When the installation program prompts you to select an installation type, select 3 Solaris Interactive Text (Desktop Session).
Workaround 2: If you use the Solaris installation GUI program, follow these steps.
Begin the installation.
At the prompt to select an installation type, select Custom Install.
The custom installation panels prompt you for information about the locales, software, and disks that you want to install.
Answer the questions on the screens as appropriate for your system.
On the Fdisk Selection screen, check the disk that contains the x86boot partition.
Remove the x86boot partition by changing it to UNUSED in the pull-down menu.
Add the x86boot partition back by changing UNUSED back to x86boot.
Continue the installation.
The following bugs might occur during or after the installation of Solaris 10 OS.
For GUI-based installation of the Solaris 10 10/09 OS, the system should have a minimum 768 MB of memory. If the physical memory is less than 786 MB, an error message similar to the following is displayed and the installation switches to text installation.
Not enough memory for graphical installation. Graphical installation requires 768 MB of memory. Found 640 MB of memory. Reverting to text-based installation. |
Workaround: Ensure that you have 768 MB of memory for a GUI-based installation or upgrade.
Disk space reallocation (DSR) Upgrade using DVD or /net image might cause corruption of systems. Upgrade appears successful on the system console, but no packages are added after patch and package removal. After removal of patches or packages, the upgrade goes directly to creating boot blocks and reboots the system. As all packages, including ones that are necessary for booting, are removed and no packages are added, the system fails to boot. This failure is seen intermittently.
The following error message is displayed:
Can't open boot_archive Fast Data Access MMU Miss %TL:1 %TT:68 %TPC:f0009ca4 %TnPC:f0009ca8 %TSTATE:8840001600 %PSTATE:16 ( IE:1 PRIV:1 PEF:1 ) DTLB-MATCH:ffffffffffffe ( VA:-2000 CTX:0 ) |
Workaround: Use Solaris Live Upgrade in place of DSR upgrade for change disk allocation.
On systems with low memory, installation might fail if either / or /var have just minimum or recommended disk sizes. The following error message is displayed:
Creating boot_archive for /a updating /a/platform/sun4u/boot_archive 15+0 records in 15+0 records out cat: write error: No space left on device |
Workaround: Increase the size of /var to at least 300 Mbytes on low memory systems.
DSR upgrade fails on systems installed with a Solaris 10 release prior to the Solaris 10 10/09 release. This failure is due to an auto-layout problem. For example, if you install with the following profile:
install_type initial_install system_type standalone cluster cxall partitioning explicit filesys rootdisk.s0 auto / logging filesys rootdisk.s1 512 swap filesys rootdisk.s6 10240 /backup logging filesys rootdisk.s7 free |
And, then you do DSR upgrade to the Solaris 10 10/09 release with the following profile:
install_type upgrade root_device rootdisk.s0 backup_media local_filesystem /backup layout_constraint rootdisk.s0 changeable layout_constraint rootdisk.s7 available |
The DSR upgrade fails with the following error message:
Auto-layout could not determine how to reallocate space on the file systems with the constraints you specified. Try other constraints |
Workaround: Label the rootdisk.s1 and rootdisk.s6 slices as “changeable”. If an extra disk is available in the system, and there is sufficient space on an unused slice for a backup, then modify the <backup_media> keyword, as shown in the following example:
backup_media local_filesystem /dev/dsk/c0t1d0s7 |
In this example, disk c0t1d0s7 is the second disk available, and the disk has enough space for a backup. Alternately, if there is only one rootdisk in the system, perform the backup on a remote system. Use the following syntax:
backup_media remote_filesystem hostname:/export/backup |
The DSR upgrade will succeed.
On multi-socket Nehalem systems, where DIMMs are installed on only one CPU, the system panics during boot with the following kernel panic error message:
Too many lgrps for platform (4) |
Workaround: Disable the use of the ACPI System Resource Affinity Table (SRAT) by performing one of the following two options:
Boot into kmdb(1) by adding '-k' to the GRUB menu kernel line, booting, and typing the following commands to kmdb(1):
lgrp_plat_srat_enable/W 0 :c |
When the system is booted, set the <lgrp_srat_enable> boot property to 0 using eeprom(1M). This setting disables the use of SRAT across reboots.
Localized Solaris installer always runs in the EUC or ISO8859 locales. Thus, the install log is written in EUC or ISO8859 encoding.
Workaround: While performing localized CLI (command line interface) install through a terminal, the locale on the terminal must be EUC or ISO8859 locale.
The installation fails, when installing WAN boot image from Solaris 10 10/09 release. The following error message is displayed:
boot_file=/wanboot/wanboot.u-137111-04 root_file=/miniroot/miniroot.s10-1008 |
Workaround: The Solaris 10 10/09 miniroot image must be patched to proceed with the installation. Perform the following steps to patch a network installation miniroot image:
These steps assume that you have a system on your network that is running the current Solaris release, and that system is accessible over the network.
On a system that is running the current Solaris release, log in as superuser or assume an equivalent role.
Change to the Tools directory of the installation image you created.
# cd install-server-path/install-dir-path/Solaris_10/Tools |
Specifies the path to the install server system on your network, for example, /net/installserver-1.
Create a new installation image, and place that image on the system that is running the current Solaris release.
# ./setup_install_server remote_install_dir_path |
Specifies the path on the current Solaris release in which to create the new installation image.
This command creates a new installation image on the current Solaris release. In order to patch this image, you must temporarily place this image on a system that is running the current Solaris release.
On the current Solaris release, unpack the network installation boot archive.
# /boot/solaris/bin/root_archive unpackmedia remote_install_dir_path \ destination_dir |
Specifies the path to the network installation image on the current Solaris release.
Specifies the path to the directory to contain the unpacked boot archive.
On the current Solaris release, patch the unpacked boot archive.
# patchadd -C destination_dir path-to-patch/patch-id |
Specifies the path to the patch that you want to add, for example, /var/sadm/spool.
Specifies the patch ID that you want to apply.
You can specify multiple patches with the patchadd -M option. For more information, see patchadd(1M).
Don't use the patchadd -C command unless you have read the Patch README instructions or have contacted your local Sun support office.
On the current Solaris release, pack the boot archive.
# /boot/solaris/bin/root_archive packmedia remote_install_dir_path \ destination_dir |
Copy the patched archives to the installation image on the install server.
# cd remote_install_dir_path # find boot Solaris_10/Tools/Boot | cpio -pdum \ install-server-path/install_dir_path |
If you are installing a Solaris Flash archive from a release before the Solaris 10 10/08 release, the archive fails to install. Starting with the Solaris 10 10/08 release, if the archive is from the Solaris 10 10/08 release or later, the archive can be installed. 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 a Solaris Flash archive from the Solaris 10 10/08 release or later.
If you need to install a Solaris Flash archive from a previous release, boot from the previous release and extract the archive.
Installation fails if you attempt to boot the system by using the following command:
# boot -F wanboot -vV -o prompt |
As a result, a system panic occurs. The following error message is displayed:
wanboot: panic - boot: can't alloc ramdisk memory |
This problem occurs on both Sun4u and Sun4v platform types. This problem was introduced in the Solaris 10 10/08 release.
Workaround: Do not use wanboot program to boot the system. Instead, boot the system directly from the installation media.
Some Asian locales like, 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 cannot be used while installing with Custom JumpStart. 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 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,
While upgrading Solaris Trusted Extensions from the Solaris 10 11/06 or Solaris 10 8/07 release to the Solaris 10 10/08, Solaris 10 5/09 release or the current Solaris 10 10/09 release, the prodreg entry for Solaris Trusted extensions is not removed. No error message is displayed.
Workaround: After upgrading Solaris Trusted Extensions to the current release, remove the prodreg entry manually as follows:
# prodreg unregister -f -r -u "Solaris Trusted Extensions" -i 1 |
The driver for the NVidia SATA controller MCP55 and CK804 chipsets included in the Solaris 10 10/09 release does not support ATAPI CD/DVD devices.
During system installation or upgrade by using a SATA CD/DVD device, the Solaris installer starts and appears to function but fails with the following error messages:
ERROR: The disc you inserted is not a Solaris OS CD/DVD |
Or
There were problems loading the media from /cdrom |
During normal system operation, the SATA CD/DVD drive is not configured and cannot be used.
Workaround: Use the USB CD/DVD.
During a Solaris upgrade, if you select Detailed Analysis to see the patches that 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:
# cd <cdrom>/Solaris_10/Misc # ./analyze_patches -R rootdir -N netdir -D databasedir |
The command options are as follows:
rootdir is the root of the installed system. The default root directory is /.
netdir is the path to the root of the OS image to be installed. /cdrom/cdrom0 is the default path. netdir is the path to the directory that contains the Solaris_10_606 directory. You must use this option if you are running the patch_analyzer from an NFS mount point.
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 on the OS image, the script will not run correctly.
During a Solaris Serial installation, the system does not have an attached keyboard, but a prompt for selecting the keyboard layout is displayed.
Workaround: Select the keyboard layout. You can change the keyboard layout using the kbd command with -s option if needed when a keyboard is attached.
The Solaris OS might panic with a null pointer dereference if the driver.conf file has been modified using the parent attribute. The following error message is displayed:
System panic: BAD TRAP: type=31 rp=2a101d31200 addr=8 mmu_fsr=0 occurred in module "pcie" due to a NULL pointer dereference |
Workaround: Before you install the Solaris 10 10/09 OS on a PCI Express (PCIe) based SPARC system, check if you have modified the driver.conf files as described below:
Change to the /kernel/drv directory.
Check if the parent attribute is set in the driver.conf file. If the parent attribute has been set and the last node in the parent has the word pci in it, comment out that line. Ensure that you comment out the entire property. For example:
# name="ACME,simple" parent="/pci@7c0/pci@0/pci@9" # unit-address="3,1" debug-mode=12; name="ACME,example" parent="pseudo" instance=1; name="ACME,scsi" parent="/pci@7c0/pci@0/pci@9/scsi" unit-address="3,1" debug-mode=12; |
Repeat step 2 for the driver.conf files in the following directories:
/usr/kernel/drv
/platform/`uname -i`/drv
/platform/`uname -m`/drv
Install the Solaris 10 10/09 OS.
Install patch 127747-01.
Change to the directories listed in steps 1 and 3. Uncomment all the lines that were commented out in step 2 in the driver.conf files.
If Linux is installed on your disk and you installed the Solaris OS on a separate partition, the Linux partition does not display on 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:
Boot the Solaris OS.
Edit the menu.lst file at /boot/grub/menu.lst. For more information, see the System Administration Guide: Basic Administration.
Installations can run out of memory and hang on 512-Mbyte systems under the following conditions:
You install using a network installation image of the OS.
The Solaris installation program is in a windowing environment:
The graphical user interface (GUI).
The -text option or “3. Solaris Interactive Text (Desktop session)” in the menu below.
When the system exhausts available memory, the GUI installation process slows and eventually fails. The text does not display in a windowing environment.
Workaround:
To avoid this problem, select a non-windowing environment during the initial installation startup. During startup from the installation media the following menu is displayed:
----------- 1. Solaris Interactive (default) 2. Custom JumpStart 3. Solaris Interactive Text (Desktop session) 4. Solaris Interactive Text (Console session) 5. Apply driver updates 6. Single user shell Enter the number of your choice. ----------- |
At this point, choose “4. Solaris Interactive Text (Console session)”. This non-windowing environment will initiate a text-only installation, without using memory-intense processes.
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.
A problem might occur when you are using the Solaris installation program and are using CD media. After the installation of the Solaris software from the Solaris 10 10/09 Software CD - 4, the following prompt is displayed:
Press Reboot now to continue. |
If you press Reboot, the system might not respond. The installation is successful. However, the error prevents the installation program from exiting normally. Consequently, the typical postinstallation cleanup and system reboot cannot occur.
An error message similar to the following example is logged in /tmp/disk0_install.log file:
Exception in thread "Thread-70" java.lang.IndexOutOfBoundsException: Index: 6, Size: 5 at java.util.ArrayList.add(ArrayList.java:369) at com.sun.wizards.core.WizardTreeManager. actualExitButtonPressed(WizardTreeManager.java:1499) at com.sun.wizards.core.WizardTreeManager. exitButtonPressed(WizardTreeManager.java:1486) at com.sun.wizards.core.AutonextController. run(AutonextController.java:736) at java.lang.Thread.run(Thread.java:595) |
Workaround: Choose one of the following workarounds.
Workaround 1: Follow these steps.
Shut down the system, then turn on the power again.
After the system starts up, insert the appropriate CD at the prompt. Although the CD is inserted, no additional software is installed on the system. In a moment, the system reboots normally.
Workaround 2: Follow these steps.
Open a terminal window.
Log in as superuser.
Create or modify access to the .instsuccess file.
# touch /tmp/.instsuccess |
Stop the Java process.
# pkill -9 java |
The system reboots without prompting for the CD media.
If you use the Custom JumpStart installation method to install on an x86 based system, and 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 Custom JumpStart profile, remove the filesys keyword entry that configures slice 2 as the overlap slice. For example, you would remove a keyword entry that is similar to the following entry.
filesys c0t0d0s2 all overlap |
After you remove the entry, perform the Custom JumpStart installation.
For the latest information about upgrade support beginning with the Solaris 10 10/09 release, see Changes in Upgrade Support for Solaris Releases.
This section describes upgrade bugs. Some might occur while you are upgrading to Solaris 10 OS. Others might occur after you have completed upgrading.
On systems configured for Solaris Trusted Extensions, audio devices are unavailable for allocation at user labels, after upgrading from the Solaris 10 5/08 or earlier releases to the Solaris 10 10/08 or later releases. This bug occurs because the /etc/logindevperm changes are lost during the upgrade. No error message is displayed.
Workaround: After upgrading, manually merge the /etc/logindevperm.old and /etc/logindevperm files to restore Solaris Trusted Extensions configuration changes to logindevperm.
During system upgrade to the Solaris 10 10/09 OS, the /etc/services and /etc/inet/services files are removed when the SUNWsmbar is installed. The following error messages are displayed on the system console upon reboot:
line1-v215 console login: Oct 6 15:40:57 inetd[457]: Property 'name' of instance svc:/network/stdiscover:default is missing, inconsistent or invalid Oct 6 15:40:57 inetd[457]: Property 'proto' of instance svc:/network/stdiscover:default is missing, inconsistent or invalid Oct 6 15:40:57 inetd[457]: Invalid configuration for instance svc:/network/stdiscover:default, placing in maintenance Oct 6 15:40:57 inetd[457]: Property 'name' of instance svc:/network/stlisten:default is missing, inconsistent or invalid Oct 6 15:40:57 inetd[457]: Property 'proto' of instance svc:/network/stlisten:default is missing, inconsistent or invalid Oct 6 15:40:57 inetd[457]: Invalid configuration for instance svc:/network/stlisten:default, placing in maintenance |
Workaround: To prevent removal of the /etc/services and /etc/inet/services during OS upgrade perform the following steps:
Stop all running Samba services:
#svcadm disable samba:default swat:default wins:default winbind:default |
Uninstall the SUNWsmbar package before upgrading the OS:
#pkgrm SUNWsmbar |
Upgrade the OS to the Solaris 10 10/09 release.
Re-install the SUNWsmbar package:
#pkgadd SUNWsmbar |
The shutdown command might cause the system to hang after it is upgraded to the Solaris 10 10/09 release. The hang occurs while the svc.startd daemon halts system services.
The Sun Java Web Console debug log file at /var/log/webconsole/console/console_debug_log displays if the web console service is cycling, starting and stopping.
Workaround: Type the following commands:
/usr/share/webconsole/private/bin/wcremove -i console svcadm clear system/webconsole:console smcwebserver start |
The wcremove command removes the server domain instance that was created for that specific console. When the console is restarted, a new domain instance is created.
When the lucreate and lumake commands are used on non-global zones which are not in the running state, the commands might not execute successfully. The contents of the original non-global zone and the copy might differ. Users might be unable to log in to the zone's console using the zlogin command. The following error message is displayed while using the zlogin command:
zlogin: makeutx failed |
The diagnostic output of the lucreate and lumake commands do not display any errors.
Workaround: Ensure that all non-global zones are in the running state before using the lucreate and lumake commands.
Upgrading to the Solaris 10 10/09 release using Solaris Live Upgrade, from the previous Solaris 8 and Solaris 9 releases fails. The install images compression file is now unzipped by using the 7za utility. The SUNWp7zip package is not included in the Solaris 8 and 9 releases. As a result, Solaris Live Upgrade fails.
Workaround: To upgrade your system to the Solaris 10 10/09 release using Solaris Live Upgrade from the previous Solaris 8 and Solaris 9 releases, perform the steps listed under Solaris Live Upgrade Restrictions.
Disk space reallocation (DSR) upgrade with zones fails if zones are installed in the /opt directory. Upgrade might fail during the restoration of the DSR archive. In some cases, the upgrade might be successful, but the system cannot be rebooted.
Workaround: Ensure that the root file system is not 100% full before upgrade. Remove some files before upgrade so that the root slice is less than 90% full.
When you upgrade Solaris Trusted Extensions from the Solaris 10 11/06 or Solaris 10 8/07 release to the Solaris 10 10/08, Solaris 10 5/09 release or the current Solaris 10 10/09 release, unwanted localized Solaris Trusted Extensions packages are installed on your system. This bug occurs because the Solaris Trusted Extensions installer in theSolaris 10 11/06 or Solaris 10 8/07 releases installs localized packages by default. No error message is displayed.
Workaround: Before upgrading Solaris Trusted Extensions to the current release, remove the following localized Solaris Trusted Extensions packages:
SUNWjdtts |
SUNWkdtts |
SUNWjmgts |
SUNWkmgts |
SUNWjtsman |
SUNWktsu |
SUNWjtsu |
SUNWodtts |
SUNWtgnome-l10n-doc-ja |
SUNWtgnome-l10n-ui-ko |
SUNWtgnome-l10n-ui-it |
SUNWtgnome-l10n-ui-zhHK |
SUNWtgnome-l10n-ui-sv |
SUNWtgnome-l10n-ui-es |
SUNWtgnome-l10n-doc-ko |
SUNWtgnome-l10n-ui-ptBR |
SUNWtgnome-l10n-ui-ja |
SUNWtgnome-l10n-ui-zhTW |
SUNWtgnome-l10n-ui-zhCN |
SUNWtgnome-l10n-ui-fr |
SUNWtgnome-l10n-ui-de |
SUNWtgnome-l10n-ui-ru |
This bug occurs during an upgrade from Solaris 10 Hardware 2 release to the current Solaris 10 10/09 release.
In the Solaris 10 Hardware 2 release, the name_service.xml file for any name service, such as NIS, NIS+, FILES, or LDAP is as follows:
# ls -l name_service.xml lrwxrwxrwx 1 root root 10 Apr 10 16:26 name_service.xml -> ns_files.xml |
If the name service is NIS, the name_service.xml file links to ns_files.xml. However, the contents of the ns_files.xml are the same as ns_nis.xml.
# cat /etc/release Solaris 10 3/05 HW2 s10s_hw2wos_05 SPARC Copyright 2005 Sun Microsystems, Inc. All Rights Reserved. Use is subject to license terms. Assembled 26 September 2005 # cd /var/svc/profile # ls -l name_service.xml ns_files.xml ns_nis.xml lrwxrwxrwx 1 root other 12 May 21 04:06 name_service.xml -> ns_files.xml -r--r--r-- 1 root sys 779 May 21 04:25 ns_files.xml -r--r--r-- 1 root sys 779 Jan 21 2005 ns_nis.xml # # diff ns_files.xml ns_nis.xml # diff name_service.xml ns_nis.xml |
In the above output, the ns_nis.xml and ns_files.xml files are the same. This means that the name_service.xml file symbolically links to the wrong name service file. The name_service.xml file links to ns_files.xml. Instead, the name_service.xml file should link to the ns_nis.xml.
The fix for CR 6411084, the SUNWcsr install or postinstall script, creates the correct link only if name_service.xml is not a link file. If name_service.xml is already a symbolic link file, as in the Solaris 10 Hardware 2 release, the fix for CR 6411084 will not work.
After an upgrade from Solaris 10 Hardware 2 to the current Solaris 10 10/09 release, the following message is displayed on the console or logged in the messages file:
Oct 23 12:18:45 vt2000a automount[301]: [ID 366266 daemon.error] can't read nis map auto_master: can't communicate with ypbind - retrying |
Also, the /network/nis/client:default service is offline.
Workaround: Choose one of the following workarounds:
Workaround 1: Before an upgrade, remove the /var/svc/profile/name_service.xml file.
Workaround 2: After an upgrade, change the /var/svc/profile/name_service.xml link to the correct ns_<xxx>.xml file, based on the name service.
A non-global zone that has been installed but never booted or made ready prevents a system from being upgraded correctly. No error message is displayed.
Workaround:
If such a zone is found, the zone should be made ready and then halted prior to starting the upgrade. For example:
global# zoneadm -z myzone ready ; zoneadm -z myzone halt |
Upgrading a Solaris 10 3/05 system or a Solaris 10 1/06 system to the Solaris 10 10/09 release with non-global zones might cause the SMF service that mounts local file systems to fail in the non-global zones. As a result, other services in the non-global zones might fail to start.
After upgrading a Solaris 10 system with non-global zones to the Solaris 10 10/09 release, services might be in the maintenance state. For example:
# zlogin myzone svcs -x svc:/system/filesystem/local:default (local file system mounts) State: maintenance since Wed May 24 13:18:06 2006 Reason: Start method exited with $SMF_EXIT_ERR_FATAL. See: http://sun.com/msg/SMF-8000-KS See: /var/svc/log/system-filesystem-local:default.log Impact: 18 dependent services are not running. (Use -v for list.) |
Workaround:
Reboot the non-global zone from the global zone. For example:
global# zoneadm -z myzone reboot |
In this Solaris 10 release, Solaris Volume Manager displays device ID output in a new format. Solaris 9 9/04 OS, which introduced device ID support in disk sets, does not recognize the new format. When you upgrade to Solaris 10 OS from the Solaris 9 9/04 release, device IDs that are associated with existing disk sets are not updated in the Solaris Volume Manager configuration. If you need to revert to Solaris 9 9/04 OS, configuration changes made to disk sets after the upgrade might not be available to Solaris 9 9/04 OS. For more information, see Chapter 25, Troubleshooting Solaris Volume Manager (Tasks), in Solaris Volume Manager Administration Guide.
The upgrade progress bar does not appear when you use the Solaris Live Upgrade software in the following manner:
You use the Solaris 10 10/09 CD media to upgrade the OS.
You upgrade a boot environment by using the luupgrade command with the following options:
-i to install from the CD media
-O “-nodisplay -noconsole” to run the installer on the second CD in text mode and without user interaction
You are upgrading to the Solaris 10 10/09 software from the following releases:
Solaris 9 release
Solaris 10 release
For example, if you run the following command, the progress bar should be displayed after you see the following output:
Running installer on BE s10u1. |
However, the bar fails to appear.
# luupgrade -i -n s10u1 -s /net/installsrv/export/s10u1 -O "-nodisplay -noconsole" Validating the contents of the media /net/installsvr/export/s10u1. The media is a standard Solaris media. The media contains a standard Solaris installer. The media contains Solaris 3 version 10. Mounting BE s10u1. Running installer on BE s10u1. |
No error message is displayed.
Workaround: Use the prstat command. This command enables you to watch the progress while packages are being added during the installation.
If you use Solaris Live Upgrade to upgrade from the Solaris 8 or Solaris 9 releases to Solaris 10 OS, obsolete uninstaller programs are not removed. These uninstaller programs from the previous OS remain in the system's /var/sadm/prod directory.
The following obsolete uninstallers are not removed.
uninstall_Alternate_Pathing_2_3_1.class uninstall_CDRW_1_1.class o uninstall_CDRW_1_0.class uninstall_Bonus_Localization_-_Catalan_CDE_Desktop.class uninstall_Bonus_Localization_-_Polish_CDE_Desktop.class uninstall_Bonus_Localizations_-_Russian_CDE_Desktop.class uninstall_Capacity_on_Demand_1_0.class uninstall_Java3D_1_3_1.class uninstall_Java3D_1_3.class uninstall_Java3D_1_2_1_04.class uninstall_Java3D_1_2_1_03.class uninstall_Lights_Out_Management_2_0.class uninstall_Man_Page_Supplement.class uninstall_OpenGL_1_3.class uninstall_OpenGL_1_2_3.class uninstall_Netra_ct_Platform_1_0.class uninstall_Netra_t11xx_Alarms_2_0.class uninstall_Netscape_6_2_3.class uninstall_Netscape_6_2_1_Beta.class uninstall_PC_launcher_1_0_2.class uninstall_PC_launcher_1_0_1_PCfileviewer_1_0_1.class uninstall_RSC_2_2_2.class uninstall_RSC_2_2_1.class uninstall_RSC_2_2.class uninstall_ShowMeTV_1_3.class uninstall_Solaris_9_French_Localization.class uninstall_Solaris_9_German_Localization.class uninstall_Solaris_9_Hong_Kong_Traditional_Chinese_Localization.class uninstall_Solaris_9_Italian_Localization.class uninstall_Solaris_9_Japanese_Localization.class uninstall_Solaris_9_Korean_Localization.class uninstall_Solaris_9_Simplified_Chinese_Localization.class uninstall_Solaris_9_Spanish_Localization.class uninstall_Solaris_9_Swedish_Localization.class uninstall_Solaris_9_Traditional_Chinese_Localization.class uninstall_Solaris_On_Sun_Hardware_Documentation.class uninstall_Sun_Hardware_AnswerBook.class uninstall_SunATM_5_0.class uninstall_SunATM_5_1.class uninstall_SunFDDI_PCI_3_0.class uninstall_SunFDDI_SBus_7_0.class uninstall_Sun_Fire_880_FC-AL_Backplane_Firmware_1_0.class uninstall_Sun_Fire_B10n_Load_Balancing_Blade_1_1.class uninstall_SunForum_3_1.class uninstall_SunForum_3_2.class uninstall_SunHSI_PCI_3_0.class uninstall_SunHSI_SBus_3_0.class uninstall_SunScreen_3_2.class uninstall_SunVTS_5_1_PS6.class uninstall_SunVTS_5_1_PS5.class uninstall_SunVTS_5_1_PS4.class uninstall_SunVTS_5_1_PS3.class uninstall_SunVTS_5_1_PS2.class uninstall_SunVTS_5_1_PS1.class uninstall_SunVTS_5_0.class uninstall_System_Management_Services_1_4.class uninstall_System_Management_Services_1_3.class uninstall_System_Management_Services_1_2.class uninstall_System_Service_Processor_3_5.class uninstall_WBEM_DR_1_0.class uninstall_Web_Start_Wizards_SDK_3_0_2.class uninstall_Web_Start_Wizards_SDK_3_0_1.class uninstall_Web_Start_Wizards_SDK.class uninstall_XML_Libraries_2_4_12.class |
Workaround: After you upgrade the system, manually remove the obsolete uninstallers in the /var/sadm/prod directory.
This section describes issues that are related to the installation of the Solaris OS.
When you install Solaris 10 OS, either the StarOffice or the StarSuiteTM software is also automatically installed, depending on which language you select. The languages and the corresponding software that these languages support are listed as follows:
Selected Language |
Supported Software |
---|---|
Chinese, Japanese, Korean |
StarSuite |
Other languages |
StarOffice |
StarOffice and StarSuite cannot coexist in the same system. If you want to replace a software that you accidentally installed, follow these steps.
Insert the Solaris 10 Software - 4 CD or Solaris 10 Operating System DVD in the drive.
Become superuser.
Change to the Product directory, for example, /cdrom/cdrom0/Solaris_10/Product.
Replace the software.
To replace StarOffice with StarSuite, use the following commands:
# pkgrm `pkginfo | grep staroffice- | awk '{print $2}'` # pkgadd -d .SUNWstarsuite-* |
To replace StarSuite with StarOffice, use the following commands:
# pkgrm `pkginfo | grep starsuite- | awk '{print $2}'` # pkgadd -d . SUNWstaroffice-* |
If you use Solaris CDs, the localization packages are included in either Language 1 or 2 CD. The package names are as follows:
SUNWstaroffice-lang* where lang = es, fr, de, sv, or it
SUNWstarsuite-lang* where lang = ja, ko, zh-CN, or zh-TW
When you select a locale for your installation, additional related locales might also be installed. This change in behavior occurs in the Solaris 10 release because all full locales, with message translations, and the Asian and Japanese partial locales, locale enabler, have been repackaged based on language support for locales. Other partial locales are still packaged and installed based on geographic region, such as Central Europe.