This chapter describes problems that relate to the installation of the Solaris 8 10/01 operating environment.
The following installation bug descriptions have been added to this chapter since this document was published on the Solaris 8 10/01 Documentation CD and in the Installation Kiosk on the Solaris 8 10/01 Installation CD.
The name of this product is Solaris 8 10/01, but code and path or package path names might use Solaris 2.8 or SunOSTM 5.8. Always follow the code or path as it is written.
If Solaris Web Start 3.0 on the Solaris 8 Installation CD is unable to locate a Solaris fdisk partition on a system, you must create a Solaris fdisk partition on your root disk.
If you change the size of an existing fdisk partition, all data on that partition is automatically deleted. Back up your data before you create a Solaris fdisk partition.
Solaris Web Start 3.0 requires two fdisk partitions to perform an installation.
Solaris fdisk partition
This is the typical Solaris fdisk partition.
x86 Boot fdisk partition
This is a 10-Mbyte fdisk partition that enables Intel architecture to boot the miniroot that is placed on the newly created swap slice that is located on the Solaris fdisk partition.
The Solaris Web Start 3.0 installation utility creates the x86 boot partition, removing 10 Mbytes from the Solaris fdisk partition. This utility prevents any existing fdisk partitions from being altered.
Do not create this partition manually.
This requirement also prevents you from using Web Start 3.0 to upgrade from the Solaris 2.6 or Solaris 7 releases to the Solaris 8 operating environment. For more information, refer to "Cannot Use Solaris Installation CD to Upgrade Intel Systems to the Solaris 8 Operating Environment".
A network gateway is used to communicate with other networks. A gateway system contains multiple network interface adapters and each adapter connects with a different network.
If you use the Solaris 8 10/01 Installation CD to install the Solaris 8 10/01 operating environment on a gateway system, Solaris Web Start 3.0 uses the primary interface to gather system information. You cannot instruct Solaris Web Start 3.0 to use an alternate network interface to gather information for system identification.
Workaround: To specify another interface for gathering system information, choose one of the following workarounds.
Create a sysidcfg file that specifies the network interface to use during system identification. See "Guidelines for Preconfiguring With the sysidcfg File" in Solaris 8 Advanced Installation Guide and the man page sysidcfg(4) for information on how to create and modify a sysidcfg file.
Use the Solaris 8 10/01 Software 1 of 2 CD to launch an Interactive Installation of the Solaris 8 10/01 operating environment. Specify that the system is networked, and then select the alternate network interface to use for system identification from the list that is provided.
When you upgrade from the Solaris 2.6 and Solaris 7 operating environments using a CD or CD images, extra European languages might be installed for locales that are not present on the system. If there is insufficient space in the file system, the upgrade will not complete. Languages for locales that are present on the system may not be installed.
Workaround: Choose one of the following workarounds.
Manually select the languages you want installed during the upgrade process. Follow these steps.
When the Language CD install panel is displayed, click the Back button.
Deselect the extra languages and continue with the upgrade.
Use a combined net install image to upgrade from the Solaris 2.6 and Solaris 7 operating environments. Do not use CDs or CD images to upgrade.
After upgrading, follow these steps.
Login to the system.
Run prodreg.
Uninstall any extra languages.
Insert the Language CD into your CD-ROM drive and run the top level installer.
Choose Custom Install.
Select the languages you want installed.
Complete the Language CD installation by clicking the Next and Install Now buttons.
If you upgrade to the Solaris 8 10/01 , or compatible, operating environment and you have Solaris Management ConsoleTM 1.0, 1.0.1, or 1.0.2 software installed, you must uninstall the Solaris Management Console software before you upgrade. Solaris Management Console 2.0 software is not compatible with any previous version of the console. 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, run /usr/bin/prodreg and perform a full uninstall of the 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, you must remove all Solaris Management Console 1.0, 1.0.1., or 1.0.2 software packages. You must use pkgrm for package removal instead of prodreg and you must carefully follow the order of package removal. Follow these steps.
Become superuser.
In a terminal window, type the following commands.
# pkginfo |grep "Solaris Management Console" # pkginfo |grep "Solaris Management Applications" # pkginfo |grep "Solaris Diskless Client Management Application" |
The package names in the output identify a Solaris Management Console 1.0 software package if the description does not start with "Solaris Management Console 2.0."
Use pkgrm to remove all instances of Solaris Management Console 1.0 software packages in the following order.
Do not remove any package that has "Solaris Management Console 2.0" in the description. For example, SUNWmc.2 might indicate the Solaris Management Console 2.0 software.
If the pkginfo output displays multiple versions of Solaris Management Console 1.0 software packages, use pkgrm to remove both packages. Remove the original package first and then 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 SUNWmcman and then SUNWmcman.2. Do not use prodreg.
# 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.0 software should now function. For future maintenance, or if the console does not function properly, remove the Solaris Management Console 2.0 software and reinstall it by following the next steps.
In a terminal window type the following commands.
# pkginfo |grep "Solaris Management Console" # pkginfo |grep "Solaris Management Applications" # pkginfo |grep "Solaris Diskless Client Management Application" |
The package names in the output identify the remaining Solaris Management Console software packages that are installed on your system.
Use pkgrm to remove all Solaris Management Console 2.0 software packages in the following order.
If your system has multiple instances of Solaris Management Console 2.0 software packages, such as SUNWmc and SUNWmc.2, first remove SUNWmc, and then SUNWmc.2. Do not use prodreg.
# pkgrm SUNWdclnt # pkgrm SUNWmga # pkgrm SUNWmgapp # pkgrm SUNWmcdev # pkgrm SUNWmcex # pkgrm SUNWwbmc # pkgrm SUNWmc # pkgrm SUNWmcc # pkgrm SUNWmccom |
Insert the Solaris 8 Software (Intel Platform Edition) 1 of 2 CD into your CD-ROM drive and type the following in a terminal window.
# cd /cdrom/sol_8_1001_ia/s0/Solaris_8/Product # pkgadd -d . SUNWmccom SUNWmcc SUNWmc SUNWwbmc SUNWmcex SUNWmcdev \ SUNWmgapp SUNWmga SUNWdclnt |
All previous versions of the Solaris Management Console software are now removed and the Solaris Management Console 2.0 software is functional.
The locale support installation mechanism has changed in the Solaris 8 operating environment. In the Solaris 2.5.1, 2.6, and 7 operating environments, the level of locale support that was installed depended on the software cluster that was chosen. The Solaris 8 operating environment includes a new installation interface that prompts you to select specific geographic regions for which you require locale support. Therefore, you can customize the configuration of your system at installation of the Solaris 8 operating environment with more freedom than in the Solaris 2.5.1, 2.6, and 7 operating environments.
Notice especially the following behaviors:
You must select the locales to be installed during the initial installation in the Geographic Selection screen. C (POSIX locale) and en_US.UTF-8 (Unicode support) are the only locales that are automatically installed.
When you upgrade from previous releases, some of the locales are automatically selected, depending on the available locales on the system to be upgraded. Note that English, French, German, Italian, Spanish, and Swedish partial locales were always present on the system in the Solaris 2.5.1, 2.6, and 7 operating environments.
Unicode locales (UTF-8) have a feature to enable multilingual text input. Because these locales use Asian input methods that are provided by each individual locale, install those Asian locales for which you need to type text.
Do not attempt to install a large partition that extends beyond the 8-Gbyte boundary on a disk that uses any of the controllers that are listed next. If you do attempt to install such a partition, the installed system does not behave properly.
The Solaris operating environment installation program cannot detect that the driver does not support large partitions. The installation continues without displaying an error. However, when you reboot your system, the reboot might fail.
Even if you successfully reboot your system, it will fail later because of other changes that are related to boot devices or added packages. The disk controllers that are associated with these drivers are the following.
Symbios 53C896-based controllers (symhisl)
AMI MegaRAID controllers (mega)
Compaq 53C8xx-based SCSI controllers (cpqncr)
Workaround: Do not install a large partition that extends beyond the first 8 Gbytes of a disk on systems that have disk controllers that are driven by the symhisl, mega, or cpqncr drivers.
The Solaris 8 operating environment includes a new feature that enables you to install large partitions. The DPT PM2144UW controller's BIOS must support logical block addressing (LBA). The latest revision of the BIOS fully supports LBA access. The problem can also affect other DPT controller models.
Workaround: Prior to upgrading your system to the Solaris 8 operating environment, ensure that the DPT PM2144UW controller's BIOS is the latest available version from DPT.
To determine if your system has a DPT controller, perform the following steps:
Run the prtconf -D.
If the name dpt is displayed, run the card's configuration utility to obtain information about the model and BIOS revision.
Upgrade DPT PM2144UW controllers by flashing the BIOS or by installing the latest BIOS EPROM that you have obtained from DPT. See http://www.dpt.com for the latest BIOS images for all DPT controllers.
You can now upgrade the system to the Solaris 8 operating environment.
The Solaris 8 operating environment includes a new 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. The problem 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 8 operating environment because it 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.
By default, the Solaris ata device driver has the DMA feature disabled for ATA/ATAPI devices. Installing the Solaris 8 operating environment works properly with DMA disabled.
To enable the DMA feature for improved performance, see "Direct Memory Access (DMA) Is Disabled On PCI-IDE Systems".
If you use the Solaris 8 10/01 Installation CD, the following error messages are recorded in the /var/sadm/system/logs/cd0_install.log file.
cpio: Cannot chown() "/tmp/x86_boot/solaris", errno 22, Invalid argument cpio: Error during chown() of "/tmp/x86_boot/solaris/boot.bin", errno 22, Invalid argument cpio: Cannot chown() "/tmp/x86_boot/solaris/boot.bin", errno 22, Invalid argument |
These messages indicate that Web Start 3.0 on the Solaris 8 10/01 Installation CD cannot change the ownership of the files that are needed to boot from the IA boot partition. Because the IA boot partition is a PCFS file system and does not support the chown command, the cpio errors occur.
Workaround: Ignore the error messages.
Booting over the network must be done on the primary network interface of IA-based systems.
Identifying the primary network interface requires some experimentation, however the first or last network device that is listed on the Boot Solaris menu is likely to be the primary interface.
As soon as you have determined the primary interface, it remains the primary interface every time you boot unless you make a change to the hardware configuration. If you change the hardware configuration, the primary interface might or might not change, depending on the type of changes you have made.
If you boot from a non-primary network interface, the booting system hangs and a boot server is not contacted. This problem can also occur if the system is not registered as a client of the boot server.
The Installing Solaris Software - Progress bar sometimes indicates that an installation is complete when it is still in progress. The installation program might add packages for several minutes after the progress bar has indicated that the installation is complete.
Do not rely on the progress bar to indicate that the installation is complete. The installation displays the following message when the program has completed all installation operations.
Installation complete |
One of the following warning messages might be displayed when a file system is created during installation.
Warning: inode blocks/cyl group (87) >= data blocks (63) in last cylinder group. This implies 1008 sector(s) cannot be allocated. |
Or
Warning: 1 sector(s) in last cylinder unallocated |
The warning occurs when the size of the file system that is being created does not map exactly to the space on the disk that is being used. This discrepancy can result in unused space on the disk that is not incorporated into the indicated file system. This unused space is not available for use by other file systems.
Workaround: Ignore the warning message.
After you install the Solaris 8 Software 1 of 2 CD, a custom JumpStartTM installation does not prompt you to install the Solaris 8 Software 2 of 2 CD.
Workaround: Choose one of the following workarounds.
If you are installing only the End User software group, you do not need to install the Solaris 8 Software 2 of 2 CD because the End User software and its basic locale support are on the Solaris 8 Software 1 of 2 CD.
If you are installing the Entire Distribution plus OEM, Entire Distribution, or Developer software, and are using a custom JumpStart installation from a server, use a network install server that contains the Solaris 8 1 of 2, 2 of 2, and Languages CDs. See "Creating a Profile Server" in Solaris 8 Advanced Installation Guide.
If you are installing the Entire Distribution plus OEM, Entire Distribution, or Developer software and are using a custom JumpStart installation from a diskette, follow these steps to install the Solaris 8 Software 2 of 2 and Languages CDs:
After the custom JumpStart completes the installation of the Solaris 8 Software 1 of 2 CD, reboot the system.
Log in to the system.
Insert the Solaris 8 Software 2 of 2 CD.
Execute the installer script and follow the instructions on the screen to install the remaining software.
Insert the Solaris 8 Languages CD.
Execute the installer script and follow the instructions on the screen to install any languages.
You cannot use Solaris Web Start 3.0 on the Solaris 8 Installation CD to upgrade IA-based systems from the Solaris 2.6 or 7 operating environments to the Solaris 8 operating environment because of the x86 boot partition requirement. Use the Solaris Software 1 of 2 CD to upgrade to the Solaris 8 operating environment on IA-based systems.
The Solaris 8 operating environment introduces a new architecture for file system caching, which subsumes the Solaris 7 Priority Paging functionality. Do not set the system variable priority_paging in the Solaris 8 operating environment. Remove the variable from the /etc/system file when systems are upgraded to the Solaris 8 operating environment.
The new caching architecture removes most of the pressure on the virtual memory system that resulted from file system activity. As a result, the new caching architecture changes the dynamics of the memory-paging statistics, which simplifies the observation of system memory characteristics. However, several of the statistics report significantly different values. Consider these differences when you analyze memory behavior or set performance monitoring thresholds. The most notable differences are the following.
The number of page reclaims is higher, which you should consider normal operation during file system activity that is heavy.
The amount of free memory is higher because the free memory count now includes a large component of the file system cache.
Scan rates are almost zero unless there is a shortage of system-wide available memory. Scanning is no longer used to replace the free list during normal file system I/O.
Ensure that you read bug description ID 4121281 before you start upgrading your IA (Intel architecture) based system to the Solaris 8 operating environment.
If the /export directory is near full capacity and you upgrade to the Solaris 8 10/01 operating environment, the space requirements for /export are miscalculated and the upgrade fails. The problem commonly occurs if a diskless client is installed, or if third-party software is installed in /export. The following message is displayed.
WARNING: Insufficient space for the upgrade. |
Workaround: Before you upgrade, choose one of the following workarounds.
Temporarily rename the /export directory until the upgrade completes.
Temporarily comment out the /export line in the /etc/vfstab file until the upgrade completes.
If /export is a separate file system, then unmount /export before you perform the upgrade.
After upgrading from the Solaris 2.5.1 8/97 or 11/97 operating environment to the Solaris 8 operating environment, you might see the following error in /a/var/sadm/system/logs/upgrade_log.
rm: Unable to remove directory /a/var/sadm/pkg/.save.SUNWcsr: File exists |
Workaround: To prevent the error, before you upgrade to the Solaris 8 operating environment, perform fsck on the root file system.
To resolve the error after you upgrade, perform fsck on the root file system.
If your system currently supports diskless clients that were installed with the AdminSuite 2.3 Diskless Client tool, you must first delete all existing diskless clients prior to installing the Solaris 8 10/01 operating environment. For specific instructions, see "How to Set Up Your Diskless Client Environment" in Solaris 8 System Administration Supplement.
If you attempt to install the Solaris 8 10/01 operating environment over existing diskless clients, the following error message appears.
The Solaris Version (Solaris 7) on slice <xxxxxxxx> cannot be upgraded. There is an unknown problem with the software configuration installed on this disk. |
If you are upgrading from the Solaris 8 (Solaris WBEM Services 2.0), Solaris 8 6/00 (WBEM Services 2.1), Solaris 8 10/00 (WBEM Services 2.2), or Solaris 8 1/01 (WBEM Services 2.3) operating environments to the Solaris 8 10/01 operating environment (Solaris WBEM Services 2.4), you must convert any proprietary custom Managed Object Format (MOF) data to the new Reliable Log repository format that is used with Solaris WBEM Services 2.4. Failure to convert the data results in data loss.
Workaround: To convert WBEM data, before upgrading you must save the JavaSpacesTM software. After upgrading, you must run the wbemconfig convert command.
Before upgrading to the Solaris 8 10/01 operating environment, follow these steps to save the JavaSpaces software.
Become superuser.
Save the JavaSpaces software.
cp /usr/sadm/lib/wbem/outrigger.jar /usr/sadm/lib/wbem/outrigger.jar.tmp |
Check and record the version of the JDKTM software that is installed on your machine. For example:
# /usr/bin/java -version java version "1.2.1" Solaris VM (build Solaris_JDK_1.2.1_04c, native threads, sunwjit) |
You must be running the same version of the JDK software that was running when the original JavaSpaces datastore was created.
After upgrading to the Solaris 8 10/01 operating environment, you must convert the WBEM data. For specific instructions, see "Upgrading the WBEM Repository to Prevent WBEM Data Loss" in Solaris 8 Installation Supplement.
The DiskSuiteTM metadb replicas contain driver names as part of the DiskSuite configuration data. In IA-based systems that run versions 2.4, 2.5, 2.5.1, and 2.6 of the Solaris operating environment, the SCSI driver name is cmdk. The cmdk driver has been replaced by the sd driver in the Solaris 7 and 8 operating environments for IA-based systems.
Workaround: To avoid potential data loss during upgrades to the Solaris 7 and 8 operating environments, you must save the system's meta device configurations in text files and remove their metadb replicas before upgrading any IA-based system that is running DiskSuite software. After you finish upgrading your IA-based system, you must restore the meta device configurations by using the DiskSuite command line interface.
The DiskSuite Version 4.2 Release Notes describe a procedure for saving metadb configurations, removing metadb replicas, upgrading IA-based systems to the Solaris 7 and 8 operating environments, upgrading DiskSuite to version 4.2, and restoring metadevice configurations. Bourne shell scripts that automate the procedure are available for the Solaris 7 and 8 operating environments.
This problem affects systems that run the Solaris 2.5.1 and the Solaris 2.5.1 unbundled CDE operating environments. However, these systems are only affected if the unbundled CDE has been relocated to a directory other than /usr/dt. The CDE relocation on these systems has been accomplished by creating a symbolic link in /usr/dt that points to the relocated CDE.
When you upgrade to the Solaris 8 operating environment, CDE is reinstalled in /usr/dt, and the link to the relocated version is removed. The relocated CDE is not removed and is therefore orphaned.
If the upgrade involves the reallocation of file systems, the upgrade might fail because the reallocation mechanism does not allow for the extra space that is needed in /usr/dt for the new version of CDE. This failure is not visible until the upgrade has been completed. If this failure occurs, the upgrade log includes several messages that indicate more space is needed for an upgrade.
Workaround: Uninstall the relocated CDE before you start upgrading to the Solaris 8 operating environment. You can uninstall by using the install-cde script from the Solaris 2.5.1 CDE CD. You should run this script with the -uninstall flag to remove CDE.
If you installed WBEM 1.0 from the Solaris Easy Access Server (SEAS) 3.0 CD on a system that runs the Solaris 7 operating environment, you must remove the WBEM 1.0 packages before upgrading to the Solaris 8 operating environment. The Solaris WBEM Services 2.0 do not start after you upgrade the Solaris 7 operating environment with WBEM 1.0 to the Solaris 8 operating environment. The Common Information Model (CIM) Object Manager fails to start. The following error message is displayed.
File not found: /opt/sadm/lib/wbem/cimom.jar |
Workaround: Use the pkgrm command to remove the WBEM 1.0 packages before upgrading to the Solaris 8 operating environment.
Use the pkginfo command to check if the WBEM 1.0 packages are installed by typing the following.:
% pkginfo | grep WBEM |
Become superuser.
Use the pkgrm command to remove all WBEM 1.0 packages by typing the following.
# pkgrm SUNWwbapi # pkgrm SUNWwbcor # pkgrm SUNWwbdev # pkgrm SUNWwbdoc # pkgrm SUNWwbm |
The upgrade log might state that the SUNWeeudt package was only partially installed.
Doing pkgadd of SUNWeeudt to /. ERROR: attribute verification of </a/usr/dt/appconfig/types/ru_RU.KOI8-R/datatypes.dt> failed pathname does not exist ... Installation of <SUNWeeudt> partially failed. pkgadd return code = 2 |
Workaround: Perform the following steps after the upgrade has been completed.
To remove the SUNWeeudt package, type the following.
# pkgrm SUNWeeudt |
To add the SUNWeeudtpackage, type the following.
# pkgadd SUNWeeudt |
The package customization screen for the Solaris 8 1 of 2 CD is not translated for French and German.
Workaround: Accept the default selections.
After upgrading from the Solaris 7 3/99, 5/99, 8/99, or 11/99 operating environment to the Solaris 8 10/01 operating environment, the following errors might appear in the upgrade logs.
Doing pkgadd of SUNWplow to /. pkgadd: ERROR: unable to create package object </a/usr/openwin/share/locale/de.ISO8859-15>. file type <s> expected <d> actual unable to remove existing directory at </a/usr/openwin/share/locale/de.ISO8859-15> .... Installation of <SUNWplow> partially failed. pkgadd return code = 2 Doing pkgadd of SUNWpldte to /. WARNING: /a/usr/dt/appconfig/types/de.ISO8859-15 may not overwrite a populated directory. ...... pkgadd: ERROR: /a/usr/dt/appconfig/types/de.ISO8859-15 could not be installed. ....... Installation of <SUNWpldte> partially failed. pkgadd return code = 2 |
This warning occurs because the patch switches the affected directories in the upgrade logs from symbolic links to directories. The upgrade process then attempts to install an updated version of the package that does not include the change. These errors do not affect the operating environment on your system.
Workaround: Ignore these error messages.
The Solaris interactive installation dialog box has not been localized except for the title. The section that has not been localized begins with the following text.
You'll be using the initial option ..... |
{0} is occasionally displayed in French and Italian where a CD title normally appears.
Installing the operating environment by using the two languages that are specified causes parts of the installation process to be displayed in English. In addition, all the localization packages are not installed. The following message is displayed.
XView warning: "de" kann nicht als Sprachumgebungs-Kategorie Ausgabesprache (gesetzt über Umgebungsvariable(n)) verwendet werden, wenn Standardspracheauf"de_AT.ISO8859-15" gesetzt ist (Server Package) XView warning: Requested input method style not supported. (Server package) |
Workaround: Install the Solaris operating environment by using the German or French ISO8859-1 locales.
The German Web Start Kiosk proxy information dialog box has the OK and Cancel buttons labeled as Undefined. The button on the left should be OK and the button on the right should be Cancel.