test

Solaris 10 7/07 HW Release Notes

Chapter 2 Installation Issues

This chapter describes problems that relate to the installation of the Solaris 10 Operating System.

Note –

Some of the issues and bugs in this chapter have been fixed in subsequent Solaris 10 releases. If you have upgraded your Solaris software, certain issues and bugs in this chapter might no longer apply. To see which bugs and issues no longer apply to your specific Solaris 10 software, refer to Appendix A, Table of Integrated Bug Fixes in the Solaris 10 Operating System.

General Information

This section provides general information such as behavior changes in Solaris 10 OS.

New Minimum Memory Requirement

Beginning with the Solaris 10 7/07 HW release, all x86 based systems must now have at least 256 Mbytes of RAM to run the Solaris software.

Support for Products Not Part of the Solaris OS

Although the Solaris 10 software has been tested for compatibility with previous releases, some third-party applications might not be fully ABI compliant. Contact the supplier of these applications directly for information about compatibility.

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:

Before You Begin

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.

Installation Change for the Solaris Companion DVD

When you are installing the Solaris OS, the Companion DVD is not available to be installed with the Solaris installation program. Use the pkgadd(1M) command to install the Solaris Companion DVD. For detailed installation instructions, see the README file on the Companion DVD.

Correct Solaris Data Encryption Supplement Required for Use of Longer Key Lengths on Solaris 10 Updates

When you install the Solaris 10 7/07 HW release and you wish to access longer key lengths for use with data encryption, you must use the Solaris Data Encryption Supplement packages that corresponds to Solaris 10. The supplement is delivered in the SUNWcry and SUNWcryr packages that are available for download from:

http://www.sun.com/download/

To bring these packages up to the same patch level as your current update, you will have to install the appropriate patch:

To determine your current patch level, use showrev -p.

Additional Procedures Required When Installing Patches for Solaris 10 7/07 HW Release

The following patches are applied to resolve problems that were reported in CR 6277164 and CR 6214222:

The sections that follow provide further steps that you must perform to completely resolve the reported problems.

Resolving Issues With the GNOME Display Manager (6277164)

Note –

Perform this procedure before you use the GNOME Display Manager (GDM) as your login program, or if you have already enabled GDM as your login program. Otherwise, you can skip this procedure.

When applying the patch, load new values into the GDM configuration files. Then restart the GDM application.

  1. To load the new values into the configuration file, choose one of the following options.

    • Copy the /etc/X11/gdm/factory-gdm.conf file to the /etc/X11/gdm/gdm.conf file.

      Perform this step if you have not made any modifications to the gdm.conf file. Then you can start the GDM application.

    • Manually merge the differences in the factory-gdm.conf file into the gdm.conf file.

      Perform this step if you have modified the gdm.conf file and want to retain your modifications.

      When merging files, copy the values for the following commands from the factory-gdm.conf file to the gdm.conf file. These commands enable you to obtain the best OS performance.

      • RebootCommand

      • HaltCommand

      • SuspendCommand

      • DefaultPath

      • RootPath

      • GraphicalTheme

  2. To restart GDM, perform the following steps:

    1. Become superuser.

    2. Issue the following command:


      # svcadm disable application/gdm2-login

    3. In the console that is now displayed, press Return to display a command prompt.

    4. To restart GDM, issue the following command:


      # svcadm enable application/gdm2-login

Sun Fire V250 Server Installation

The SUNWCXall software metacluster must be installed on a Sun Fire V250 Server.

NFS Version 4 Introduces New Prompt at First System Boot

Solaris 10 OS uses NFS Version 4 (NFSv4) as the default distributed file system mechanism. In NFSv4, file user and group attributes are exchanged as strings of the form “user@domain” and “group@domain,” respectively.

The domain portion of the string should be common between client and server. This information is automatically derived from the system's name service domain name. However, in certain cases, the derived domain might not match between client and server. This mismatch might typically occur in environments where either of the following circumstances is true:

If domain information between client and server does not match, NFSv4-accessed files might appear to be owned by “nobody.”

To ensure proper configuration, on the first system boot the system now prompts you for a domain to use for NFSv4. Answer “no” to this prompt if one of the following configurations describes your deployment:

Custom JumpStart and Advanced Installations

Environments that use the Custom JumpStartTM method to perform unattended system installations require minimal tuning to suppress the first boot prompts.

A sample script, set_nfs4_domain, is provided in the Solaris 10 distribution media and is located in the ${CDrom_mnt_pt}/Solaris_10/Misc/jumpstart_sample directory. A copy of this script should be modified to set the NFS4_DOMAIN variable to site-specific needs and be called from within JumpStart's finish script. The target system's NFSv4 domain is therefore preconfigured as part of the JumpStart finish phase, and thus suppresses any first boot prompts.

Follow these steps to perform unattended installations:

  1. Create a copy of the set_nfs4_domain script in the same directory as your JumpStart's finish.sh scripts.

  2. Edit the script and set the NFS4_DOMAIN variable to your specific needs.

  3. Edit your finish.sh script and append a call to set_nfs4_domain.

  4. Perform the JumpStart installations as usual.

For further details, refer to the sysidconfig(1M), sysidtool(1M), nfsmapid(1M), and nfs(4) man pages. See also the System Administration Guide: Network Services.

Default Size of /var File System Inadequate for Extra Value Products

The default size of the /var file system might be insufficient for the Extra Value products in the following situations:

You must manually specify a larger slice size for the /var file system.

Note –

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.

SPARC: Older Firmware Might Need Boot Flash PROM Update

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:

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 2–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 

Note –

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

See any edition of the Solaris 8 Sun Hardware Platform Guide at http://docs.sun.com for instructions to perform a flash PROM update.

Solaris Management Console 2.1 Software Is Not Compatible With Solaris Management Console 1.0, 1.0.1, or 1.0.2 Software

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:

Cannot Create a Solaris Flash Archive When Solaris Zones Are Installed (6246943)

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:

If you create a Solaris Flash archive in such an instance, the resulting archive might not install properly when the archive is deployed.

Workaround: None.

Installation Bugs

The following bugs might occur during or after the installation of Solaris 10 OS.

Symbolic Links to etc/default/kbd and etc/default/nfs Files are Missing (6547635)

The Linux Partition Does Not Display on the GRUB Menu After Installing the Solaris OS (6508647)

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:

  1. Boot the Solaris OS.

  2. Edit the menu.lst file at /boot/grub/menu.lst. For more information, see the System Administration Guide: Basic Administration.

SPARC: Installing a Solaris Flash Archive Causes Sun4v System to Hang (6411690)

If you use the flarcreate command to create a Solaris Flash archive and use the -L pax option, the installation of the archive hangs on a Sun4v system. The archive failure occurs during the retrieval of the archive. This failure affects the both the T1000 and T2000 models.

The following error message is displayed.


/pci@7c0/pci@0: Device 1c Nothing there
/pci@7c0/pci@0: Device 1d Nothing there
/pci@7c0/pci@0: Device 1e Nothing there
/pci@7c0/pci@0: Device 1f Nothing there
Probing I/O buses
Sun Fire T200, No Keyboard
Copyright 2006 Sun Microsystems, Inc.  All rights reserved.
OpenBoot 4.20.4, 8184 MB memory available, Serial #000000.
Ethernet address 0:13:3f:3d:b3:13, Host ID: 000db914.



Rebooting with command: boot
Boot device: disk  File and args:
Loading ufs-file-system package 1.4 04 Aug 1995 13:02:54.
FCode UFS Reader 1.12 00/07/17 15:48:16.
Loading: /platform/SUNW,Sun-Fire-T200/ufsboot
Loading: /platform/sun4v/ufsboot
ERROR: Last Trap: Memory Address not Aligned
[Exception handlers interrupted, please file a bug]
[type 'resume' to attempt a normal recovery]
{0} ok
         (This hangs and will never complete)

Workaround: Create the archive by using the cpio copy option. The cpio option is the default. See the following example:


# flarcreate -n test.flar.sun4v.cpio -c
/net/server/export1/rw/test.flar.sun4v.cpio

Solaris Not Sending a PRLI to Tape Device (6379955)

Solaris OS is not sending Process Login (PRLI) data to the tape device during a path recovery sequence.

No error message is displayed to the user, but the problem can be identified from:

Workaround:

To recover from this situation, use the luxadm forcelip command to the FC host bus adapter. For example:

luxadm -e forcelip /dev/cfg/c99

c99 is the specific controller that is being used to communicate with the tape transport.

SPARC: Solaris 10 OS Installation Program Might Not Display Special Case Panels Properly (5002175)

If you install the Solaris 10 software by using the Solaris installation program, some of the information and exit panels for the SunSM Remote Services (SRS) Net Connect software might not display properly.

The installation panel frame and Cancel button are displayed, but the installation panel content is missing.

Note –

This problem might also occur during a Solaris installation of other software products that are included in this Solaris OS release.

Workaround: Follow these steps:

  1. Bypass the SRS Net Connect installation by clicking the Cancel button when the empty installation panel is displayed.

  2. After the installation of the Solaris 10 software has completed, manually install the SRS Net Connect software from the Solaris 10 Operating System DVD or Solaris 10 Software - 2 CD.

Installing the SRS Net Connect software after the initial Solaris 10 software installation has completed ensures that all panels are displayed properly.

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

When a file system is created during installation, one of the following warning messages might be displayed:


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 you created does not equal 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.

Additional Installation Issues

This section describes issues that are related to the installation of the Solaris OS.

smosservice add Command Does Not Install Designated ARCH=all Packages (4871256)

The smosservice add command does not install any packages that are designated ARCH=all in the root (/) or /usr file systems. There is no error message indicating these packages were skipped. This problem exists in all Solaris OS versions, and applies to both SPARC® based and x86 based clients.

Note that the list of missing packages varies, depending on the Solaris release that you are running.

Workaround: Locate and install the missing ARCH=all packages.

For step-by-step instructions on locating and installing missing packages, see How to Locate and Install Missing ARCH=all Packages in System Administration Guide: Basic Administration.

StarOffice Patch Application Requires Additional Steps

The following patches are applied to the Solaris OS to resolve StarOfficeTM problems that were reported in CR 6234855 and CR 6262830:

To completely resolve the reported problems, perform the following steps after applying the patches. These steps enable you to use StarOffice 7 Product 5 software to open, for example, those OpenDocument files that were created in StarOffice 8 software.

  1. Become superuser.

  2. Issue the following command:


    # update-mime-database /usr/share/mime

  3. Log out of the system and then log in again.

StarOffice and StarSuite Software Cannot Coexist in the Same System

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.

  1. Insert the Solaris 10 Software - 3 CD or Solaris 10 Operating System DVD in the drive.

  2. Become superuser.

  3. Change to the Product directory, for example, /cdrom/cdrom0/Solaris_10/Product.

  4. Replace the software.

    • To replace StarOffice with StarSuite, use the following commands:


      # pkgrm SUNWsogm SUNWsom
# pkgadd -d . SUNWsoagm SUNWsoam

    • To replace StarSuite with StarOffice, use the following commands:


      # pkgrm SUNWsoagm SUNWsoam
# pkgadd -d . SUNWsogm SUNWsom

Cannot Install Documentation Packages With Names Longer Than Nine Characters on Documentation Servers Running Solaris 7 or Solaris 8 Software

Some localized documentation collections in PDF format have package names that are longer than nine characters. To install these PDF collections on servers that are running Solaris 7 or 8 software, you must first install two patches.

Workaround: For instructions on how to install these patches, see the Solaris Documentation Important Information file on Solaris 10 OS Documentation DVD. This file is located in the following directory:


mount-point/README/locale/install_
locale.html

Additional Related Locales Might Be Installed

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.