Chapter 1 Installation Issues

This chapter describes problems relating to the installation of the Solaris 8 10/00 operating environment.

The name of this product is Solaris 8 10/00, but code and path or package path names may use Solaris 2.8 or SunOS^TM 5.8. Always follow the code or path as it is written.

In the HTML version of the Solaris 8 Advanced Installation Guide on the Solaris 8 Documentation CD, pages were dropped. To read the complete Solaris 8 Advanced Installation Guide, refer to:

• The PDF version on the Solaris 8 Documentation CD

• The AnswerBook2 version on the Solaris 8 Documentation CD

• http://docs.sun.com

System Identification Bugs

System Identification Tools Fail to Verify Name Server (4265363)

If you are configuring the name service (NIS+, NIS or DNS) on a system and the name server(s) exist on another subnet and the router does not broadcast its route, then the system identification tools fail to verify the name server.

If you choose DNS as the name service, the installation program prompts you to accept the unverified data and continue. If you choose NIS+ or NIS as the name service, the system identification cannot continue without verification and the name service cannot be configured during installation.

Workaround: Choose one of the following workarounds.

1. If you are installing using a graphical interface, open a terminal window and type the following command to add a router:

   # route add default <ip_address_of_router>

2. If you are installing using a command line interface, choose nameservice = none. After the installation is complete, create the /etc/defaultrouter file and run sys-unconfig.

Solaris Web Start 3.0 Bugs You Need to Know About Before Using the Solaris 8 Installation CD

Cannot Specify an Alternate Network Interface to Use During System Identification on Network Gateway Systems (4302896)

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/00 Installation CD to install the Solaris 8 10/00 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/00 Software 1 of 2 CD to launch an Interactive Installation of the Solaris 8 10/00 operating environment. Specify that the system is networked, and then select the alternate network interface to use for system identification from the list provided.

Issues You Need to Know About Before Installing Solaris 8 Software

Locale Installation Mechanism Change

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 installed depended on the software cluster 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 have more freedom to customize the configuration of your system when you install the Solaris 8 operating environment more than was possible 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.

Installation Bugs That Occur During an Interactive Installation From Solaris 8 1 of 2 CD

Installation Progress Bar May Be Inaccurate (1266156)

The Installing Solaris Software - Progress bar sometimes indicates that an installation is complete when it is still in progress. The installation program may 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 

Warnings May Occur When a File System Is Created (4189127)

One of the following warning messages may 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.  

Warning: 1 sector(s) in last cylinder unallocated  

Workaround: Ignore the warning message.

Custom JumpStart Does Not Prompt for the Solaris 8 Software 2 of 2 CD (4304912)

After installing the Solaris 8 Software 1 of 2 CD, a custom JumpStart^TM 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:

  1. After the custom JumpStart completes the installation of the Solaris 8 Software 1 of 2 CD, reboot the system.

  2. Log in to the system.

  3. Insert the Solaris 8 Software 2 of 2 CD.

  4. Execute the installer command and follow the instructions on the screen to install the remaining software.

  5. Insert the Solaris 8 Languages CD.

  6. Execute the installer command and follow the instructions on the screen to install any languages.

Upgrade Issues

Priority Paging Is Not Needed With the New Solaris 8 Caching Architecture

The Solaris 8 operating environment introduces a new file system caching architecture, which subsumes the Solaris 7 Priority Paging functionality. You should not set the system variable priority_paging in the Solaris 8 operating environment, and you should 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 makes observing system memory characteristics simpler. However, several of the statistics report significantly different values. You should consider these differences when analyzing memory behavior or setting performance monitoring thresholds. The most notable differences are:

• The number of page reclaims is higher, which you should consider normal operation during heavy file system activity.

• 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.

Installation Bugs That Occur During an Upgrade

Relocated CDE From the Solaris 2.5.1 Operating Environment Orphaned by an Upgrade to the Solaris 8 Operating Environment (4260819)

This problem affects systems running 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 may fail because the reallocation mechanism does not account for the extra space 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 a number of messages indicating that 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.

Upgrading the Solaris 7 Operating Environment With Web-Based Enterprise Management (WBEM) 1.0 to the Solaris 8 Operating Environment Causes WBEM 2.0 Not to Work (4274920)

If you installed WBEM 1.0 from the Solaris Easy Access Server (SEAS) 3.0 CD on a system running 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 upgrading 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.

1. Use the pkginfo command to check if the WBEM 1.0 packages are installed by typing:

   % pkginfo | grep WBEM

2. Become superuser.

3. Use the pkgrm command to remove all WBEM 1.0 packages by typing:

   # pkgrm SUNWwbapi # pkgrm SUNWwbcor # pkgrm SUNWwbdev # pkgrm SUNWwbdoc # pkgrm SUNWwbm

SUNWeeudt Partially Fails to Install During an Upgrade (4304305)

The upgrade log may 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.

1. Remove the SUNWeeudt package by typing:

   # pkgrm SUNWeeudt

2. Add the SUNWeeudt package by typing:

   # pkgadd SUNWeeudt

64-bit Packages Are Unnecessarily Installed During Upgrade From Solaris 2.6 or Solaris 7 Operating Environment (4323398)

When you upgrade to the Solaris 8 10/00 operating environment from the Solaris 2.6 or Solaris 7 operating environment and do not select 64-bit support as an upgrade option, the following 64-bit packages are unnecessarily installed:

• SUNWceuox

• SUNWeeoux

• SUNWneoux

• SUNWseoux

• SUNWweoux

Workaround: After you complete the upgrade, remove these 64-bit packages using the pkgrm command:

# pkgrm SUNWceuox SUNWeeuox SUNWneuox SUNWseuox SUNWweuox 

64-Bit Solaris Issues

Sun UltraSPARC System (sun4u) May Need Boot Flash PROM Update

If your system is already running 64-bit ready firmware, then the flash PROM update is not required.

If you want to run the 64-bit Solaris operating environment on an UltraSPARC^TM system, you may need to update its flash PROM firmware. The Solaris 8 installation programs have a choice for adding 64-bit support. This 64-bit support is selected by default when you install on Sun UltraSPARC systems. A 64-bit system only boots in the 64-bit mode by default if it has a CPU speed of 200 Mhz or greater.

If you choose to run the 32-bit Solaris operating environment on any Sun^TM or UltraSPARC system, the flash PROM update is not needed.

The following table lists the UltraSPARC (sun4u) systems that are affected and the minimum firmware versions needed. System type is the equivalent of the output of the uname -i command. You can tell what firmware version you are running by using the prtconf -V command.

If a system is not listed in the previous table, it does not need a flash PROM update.

For instructions on performing the flash PROM update using the Solaris CD, refer to the Solaris 8 on Sun Hardware Collection. If you do not have this manual, you can obtain it at http://docs.sun.com.

Localization Bugs

Turkish Locale Does Not Install From Solaris 8 1 of 2 CD (4359095)

The Turkish locale does not install when using Solaris 8 1 of 2 CD. The following error message appears:

couldn't set locale correctly

Workaround: Install through the C language and add Turkish Support.

Error Messages May Occur During European Upgrade (4230247, 4225787)

After upgrading from the Solaris 7 3/99, 5/99, 8/99 or 11/99 operating environments to the Solaris 8 10/00 operating environment, the following errors may 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 listed 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.

Swedish Locale: Dialog Boxes Displayed During Installation Are Not Localized (4300655)

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 .....

French and Italian Installation Wizards May Display {0} Instead of the CD Title (4302549)

{0} is occasionally displayed in French and Italian where a CD title normally appears.

Motif suninstall Fails in de_AT.ISO8859-15 and fr_BE.ISO8859-15 Locales (4305420)

Installing the operating environment by using the two languages specified causes parts of the installation process to be displayed in English. In addition, not all localization packages are 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 using the German or French ISO8859-1 locales.

German Locale: Add and Cancel Buttons in the Proxy Kiosk Screen Are Labeled as Undefined (4306260)

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.