test

Solaris 8 (Intel Platform Edition) 1/01 Release Notes Update

Chapter 1 Installation Issues

This chapter describes problems that relate to the installation of the Solaris 8 1/01 operating environment.

The following installation bug descriptions have been added to this chapter since this document was published on the Solaris 8 1/01 Documentation CD and in the Installation Kiosk on the Solaris 8 1/01 Installation CD.

Note -

The name of this product is Solaris 8 1/01, but code and path or package path names may use Solaris 2.8 or SunOSTM 5.8. Always follow the code or path as it is written.

Note -

The Solaris 8 (Intel Platform Edition) Hardware Compatibility List is updated continuously. The latest version of the Hardware Compatibility List is available at http://soldc.sun.com/support/drivers/hcl.

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.

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

Solaris Web Start 3.0 Installation Partition Issue

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.

Caution - Caution -

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.

Note -

The Solaris Web Start 3.0 installation utility creates the x86 boot partition, removing 10-Mbytes from the Solaris fdisk partition. This prevents any existing fdisk partitions from being altered.

This partition should not be created 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 "Upgrade Issues".

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 1/01 Installation CD to install the Solaris 8 1/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.

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:

Do Not Install a Large Partition on Systems That Already Have symhisl, mega, or cpqncr Disk Controller Drivers Installed

If you attempt to install a large partition (one that extends beyond the 8-Gbyte boundary) on a disk that uses any of the controllers listed next, 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 may fail.

Even if you successfully reboot your system, it will fail later because of other changes related to boot devices or added packages. The disk controllers associated with these drivers are:

Workaround: Do not install a large partition that extends beyond the first 8 Gbytes of a disk on systems that have disk controllers driven by the symhisl, mega, or cpqncr drivers.

Update the DPT PM2144UW Controller BIOS to the Latest Revision Before Upgrading to the Solaris 8 Operating Environment

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:

  1. Run the prtconf -D.

  2. If the name dpt is displayed, run the card's configuration utility to obtain information about the model and BIOS revision.

  3. Upgrade DPT PM2144UW controllers by flashing the BIOS or by installing the latest BIOS EPROM 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.

Do Not Upgrade Hewlett-Packard (HP) Vectra XU Series Systems With BIOS Version GG.06.13

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 will no longer boot. Only a blank black screen with a flashing underbar 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 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.

Direct Memory Access (DMA) Is Disabled on PCI-IDE Systems

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 .

Installation Bugs You Need to Know About Before Installing Solaris 8 Software

64 MB System Hangs When Connecting to Network (4394591)

After installation using the Solaris 8 Installation CD in text mode on a 64 MB IA system, you might receive the following error message:


WARNING: Timed out waiting for NIS

Installation has succeeded, but two system files are not initialized correctly. The affected files are: /etc/inet/hosts and /etc/inet/netmasks. The system has run out of swap space during system configuration.

IA systems with greater amounts of memory, or IA systems installed using the Installation CD in graphics mode will not experience this problem.

Workaround: This problem can be avoided prior to installation by choosing one of the following:

If the problem has already occurred, you must correct the system after installation:

  1. From the system console, boot the system in single user mode:


    b -s

  2. Edit the file /etc/inet/hosts by adding the missing line system's_ip_address host_name .

  3. Edit the file /etc/inet/netmasks by adding the missing line system's_network_number netmask .

Installation Bugs That Occur During a Solaris Web Start 3.0 Installation

cpio Error Messages Occur When Booting From IA Boot Partition (4327051)

If you use the Solaris 8 1/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 1/01 Installation CD cannot change the ownership of the files 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.

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

ddi: net: x86 Network Boot Only Works on First Network Interface of a Given Type (1146863)

Booting over the network must be done on the primary network interface of IA-based systems.

Identifying the primary network interface is a matter of trial and error, but the first or last network device 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 may or may not change, depending on the type of changes 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.)

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

Warning: 1 sector(s) in last cylinder unallocated
The warning occurs when the size of the file system being created does not map exactly to the space on the disk 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.

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 JumpStartTM installation does not prompt you to install the Solaris 8 Software 2 of 2 CD.

Workaround: Choose one of the following workarounds:

Upgrade Issues

Cannot Use Solaris Installation CD to Upgrade Intel Systems to the Solaris 8 Operating Environment

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.

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:

Installation Bugs That Occur During an Upgrade

Caution - Caution -

Be sure to read bug description ID 4121281 before you start upgrading your IA (Intel architecture) based system to the Solaris 8 operating environment.

Upgrading Diskless Client Servers and Clients (4363078)

If your system currently supports diskless clients installed with the AdminSuite 2.3 Diskless Client tool, you must first delete all existing diskless clients prior to installing the Solaris 8 1/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 1/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.

Upgrading the JavaSpaces Datastore to Prevent WBEM Data Loss (4365035)

If you are upgrading from the Solaris 8 (Solaris WBEM Services 2.0), Solaris 8 6/00 (WBEM Services 2.1), or Solaris 8 10/00 (WBEM Services 2.2) operating environments to the Solaris 8 1/01 operating environment (Solaris WBEM Services 2.3), you must convert any proprietary custom Managed Object Format (MOF) data to the new Reliable Log repository format used with Solaris WBEM Services 2.3. Failure to convert the data will result 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 1/01 operating environment, follow these steps to save the JavaSpaces software.

  1. Become superuser.

  2. Save the JavaSpaces software.

    cp /usr/sadm/lib/wbem/outrigger.jar /usr/sadm/lib/wbem/outrigger.jar.tmp

  3. Check and record the version of the JDKTM software 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.

Note -

After upgrading to the Solaris 8 1/01 operating environment, you must convert the WBEM data. For specific instructions, see Solaris 8 Installation Supplement.

DiskSuite May Cause Data Loss (4121281)

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 meta device configurations. Bourne shell scripts that automate the procedure are available for the Solaris 7 and 8 operating environments.

Relocated CDE From the Solaris 2.5.1 Operating Environment Orphaned by an Upgrade to the Solaris 8 Operating Envi ronment (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

Localization Bugs

Custom Screen in French and German Is Not Localized (4368056)

The package customization screen for the Solaris 8 1 of 2 CD is not translated for French and German.

Workaround: Accept the default selections.

Invalid Language Option K018-R (4342970)

K018-R is an invalid language. It appears in the Language Selection Screen when installing from the Solaris 8 1 of 2 CD. If chosen, installation is not affected and will run in English.

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 1/01 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.