This chapter describes problems that relate to the installation of the Solaris 9 4/04 Operating System.
For late-breaking Solaris installation issues that were not identified in time to be included in these release notes, refer to the Solaris 9 4/04 Release Notes at http://docs.sun.com/db/doc/817-3804.
The following installation bug descriptions have been added to this chapter since the Solaris 9 4/04 Beta Release Notes was published on http://docs.sun.com.
The following are installation issues you need to be aware of before installing the Solaris 9 4/04 software.
Installing the Solaris 9 software on systems with certain types of ATA hard disk drives results in a system hang. The system hangs when you attempt a soft reboot after the installation has completed.
This problem occurs in systems with ATA hard disk drives that implement the revert to default conditions feature of ATA/ATAPI-6 T13 specification, with respect to the Ultra DMA mode.
Such disk drives revert from Ultra DMA mode to Multiword DMA mode after the software reset, unless the behavior is disabled. The behavior is disabled by using the SET FEATURES / Disable reverting to power-on to defaults command.
The way the problem manifests itself depends upon the BIOS and the type of ATA hard drive that is in the system. This problem might manifest itself in one of the following ways:
If the Ultra DMA mode is enabled in BIOS, and ATA hard disk drives can operate in the Ultra DMA mode, a soft reboot of the system after installation might cause the system to hang in BIOS. No error messages are displayed.
If the Ultra DMA mode is disabled in BIOS, and ATA hard disk drives can operate in Ultra DMA mode, a soft reboot of the system after installation might cause the system to hang. Messages that are similar to the following warnings are displayed:
WARNING: /pci@0,0/pci-ide@1f,1/ide@0 (ata0): timeout: abort request, target=0 lun=0 WARNING: /pci@0,0/pci-ide@1f,1/ide@0 (ata0): timeout: abort device, target=0 lun=0 WARNING: /pci@0,0/pci-ide@1f,1/ide@0 (ata0): timeout: reset target, target=0 lun=0 WARNING: /pci@0,0/pci-ide@1f,1/ide@0 (ata0): timeout: reset bus, target=0 lun=0 |
Workaround: To correct the problem, complete the following steps:
If the system hangs when booted, power cycle the system by turning the power off and then on again. The system should then boot normally.
After the system is booted, log in to the system and become superuser.
Use a text editor to edit the /platform/i86pc/kernel/drv/ata.conf file.
Add the following line:
ata-revert-to-defaults=0; |
The next system reboot should proceed without a hang.
If the Solaris Web Start 3.0 program on the Solaris 9 4/04 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.
The Solaris Web Start 3.0 program requires two fdisk partitions to perform an installation.
Solaris fdisk partition
This partition is the typical Solaris fdisk partition.
x86 boot fdisk partition
This partition is a 10–Mbyte fdisk partition that enables x86-based systems to boot the miniroot that is placed on the newly created swap slice. The swap slice is located on the Solaris fdisk partition.
The installation program on the Solaris 9 4/04 Installation CD creates the x86 boot partition, removing 10 Mbytes from the Solaris fdisk partition. This removal prevents any existing fdisk partitions from being altered.
This partition should not be created manually.
This requirement also prevents you from using the Solaris 9 4/04 Installation CD to upgrade from the Solaris 2.6 or Solaris 7 releases to the Solaris 9 4/04 software. For more information, refer to Upgrade Issues.
In the Solaris 9 4/04 release, the Solaris Web Start and suninstall installation programs use, by default, a new boot-disk partition layout to accommodate the Service partition on Sun LX50 systems. This installation program enables you to preserve an existing Service partition.
The new default includes the following partitions:
First partition – Service partition (the existing size on the system).
Second partition – x86 boot partition (approximately 11 Mbytes).
Third partition – Solaris partition (the remaining space on the boot disk).
If you want to use this default layout, select Default when the Solaris Web Start or suninstall program asks you to choose a boot-disk layout.
If you install the Solaris 9 4/04 (x86 Platform Edition) software on a system that does not currently include a Service partition, the Solaris Web Start and suninstall programs do not create a new Service partition by default. If you want to create a Service partition on your system, see x86: Service Partition Not Created by Default on Systems With No Existing Service Partition.
You can also choose to manually edit the disk partition layout by using the fdisk utility. You might want to manually edit the boot-disk partitions under the following conditions:
You want to preserve an existing Sun Linux partition on the system.
You need to create a Solaris partition, but want to preserve other existing partitions on the disk.
If your system contains an upgradable version of the Solaris software, but does not contain an x86 boot partition, you might not be able to upgrade by using the Solaris Installation CD. To upgrade a system with no x86 boot partition to the Solaris 9 4/04 release, use the suninstall installation program on the Solaris 9 4/04 Software 1 of 2 CD.
If you use the default Solaris JumpStartTM profile on the Solaris 9 4/04 media to install multiple locales on a system with a small disk, the installation might fail. This problem might occur under the following conditions:
You use the Solaris JumpStart profile that is the default to install any locale other than the C locale on a system with a 2.1-Gbyte disk.
You use the Solaris JumpStart profile that is the default to install two or more locales on a system with a 4-Gbyte disk.
If you install the Solaris 9 4/04 software on a system that does not currently include a Service partition, the installation program might not create a Service partition by default. If you are including a Service partition on the same disk as the Solaris partition, you must re-create the Service partition before you install the software.
If you installed the Solaris 8 2/02 software on a Sun LX50 system, the installation program might not have preserved the Service partition. If you did not manually edit the fdisk boot-partition layout to preserve the Service partition, the installation program deleted the Service partition during the installation.
If you did not specifically preserve the Service partition when you installed the Solaris 8 2/02 software, you cannot re-create the Service partition and upgrade to the Solaris 9 4/04 release. You must perform an initial installation of the software.
Workaround: If you are including a Service partition on the disk that contains the Solaris partition, choose one of the following:
To use the Solaris Web Start installation program to install from the Solaris 9 4/04 Installation CD, follow these steps:
Delete the contents of the disk.
Before you install, create the Service partition by using the Sun LX50 Diagnostics CD.
For information on how to create the Service partition, see the Sun LX50 Server User's Manual and the Sun LX50 Knowledge Base at http://cobalt-knowledge.sun.com.
Insert the Solaris 9 4/04 Installation CD in the CD-ROM drive.
Begin the installation.
When the installation program detects the Service partition, the following message is displayed:
The default layout for the bootdisk is one x86 Boot partition and a Solaris partition on the remaining space. The Service fdisk partition, if one exists, is also preserved by default. Select one of the following to continue: 1) Use the default layout 2) Run fdisk to manually edit the disk 3) Exit Please make a selection: [?] |
Type 1 to use the default layout.
The installation program preserves the Service partition and creates the x86 boot partition and the Solaris partition.
The Solaris Web Start installation program creates the x86 boot partition by removing 10 Mbytes from the Solaris fdisk partition. This utility prevents any existing fdisk partitions from being altered. Do not create this partition manually.
Complete the installation.
To install from a network installation image or from the Solaris 9 4/04 DVD over the network, follow these steps:
Delete the contents of the disk.
Before you install, create the Service partition by using the Sun LX50 Diagnostics CD.
For information on how to create the Service partition, see the Sun LX50 Server User's Manual and the Sun LX50 Knowledge Base at http://cobalt-knowledge.sun.com.
Boot the system from the network.
The Customize fdisk Partitions screen is displayed.
To load the default boot-disk partition layout, click Default.
The installation program preserves the Service partition and creates the x86 boot partition and the Solaris partition.
For more information on booting from the network, see the Solaris 9 4/04 Installation Guide.
To use the suninstall program to install from the Solaris 9 4/04 Software 1 of 2 CD or from a network installation image on a boot server, follow these steps:
Delete the contents of the disk.
Before you install, create the Service partition by using the Sun LX50 Diagnostics CD.
For information on how to create the Service partition, see the Sun LX50 Server User's Manual and the Sun LX50 Knowledge Base at http://cobalt-knowledge.sun.com.
Boot the system.
The installation program prompts you to choose a method for creating the Solaris partition.
Select the Use rest of disk for Solaris partition option.
The installation program preserves the Service partition and creates the Solaris partition.
Complete the installation.
For more information on booting from the network, see the Solaris 9 4/04 Installation Guide.
The Solaris 9 Device Configuration Assistant is not delivered as a boot diskette in the Solaris 9 4/04 release. To boot the Device Configuration Assistant, choose one of the following options:
If your system's BIOS supports CD booting from a CD, boot from the Solaris 9 4/04 (x86 Platform Edition) Installation CD, the Solaris 9 4/04 Software (x86 Platform Edition) 1 of 2 CD, or the Solaris 9 4/04 Software (x86 Platform Edition) DVD.
If your system does not support booting from a CD, you can copy the boot-diskette image to a diskette. The boot-diskette image is available on the Solaris 9 4/04 Software (x86 Platform Edition) 2 of 2 CD.
If your system supports Preboot Execution Environment (PXE) booting and an install image is available on the network, boot from the network.
Enable the system to use PXE by using the system's BIOS setup tool or the network adapter's configuration setup tool.
For more information, see the Solaris 9 4/04 Installation Guide.
The Solaris 9 4/04 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 9 4/04 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.
The following are installation bugs that you should be aware of before installing the Solaris 9 4/04 software.
To install the Solaris 9 4/04 software on specific Sun Fire and NetraTM servers, you must first update the firmware on the server. If you do not update the firmware before you install the Solaris 9 4/04 software, the server panics. This problem affects the following servers:
Sun Fire 3800 server
Sun Fire 4800 server
Sun Fire 4810 server
Sun Fire 6800 server
Sun Fire V1280 server
Netra 1280 server
If this problem occurs, the following error message is displayed:
panic[cpu0]/thread=140a000: BAD TRAP: type=34 rp=147e9e0 addr=5586ee326973add3 mmu_fsr=0 |
The ok prompt is displayed.
Workaround: Update the firmware by applying the appropriate firmware patch.
For Sun Fire 3800, 4800, 4810, or 6800 servers, apply one of the following patches:
Patch ID 112883-05 (5.14.4 firmware update)
Patch ID 112884-01 (5.15.0 firmware update)
For Sun Fire V1280 or Netra 1280 servers, apply patch ID 113751-03 (5.13.0013 firmware update).
Firmware update patches are available by going to the SunsolveSM web site at http://sunsolve.sun.com. Be sure to download and apply the most current version of the patch.
If your system has a Toshiba SD-M1401 DVD-ROM drive with firmware revision 1007, the system cannot boot from the Solaris 9 4/04 DVD.
Workaround: Apply patch 111649–03, or a later version, to update the Toshiba SD-M1401 DVD-ROM drive's firmware. You can download patch 111649–03 or a later version by going to the SunSolve web site at http://sunsolve.sun.com.
If your system is running the Solaris 2.6 or the Solaris 7 software, Volume Management incorrectly mounts the Solaris 9 4/04 DVD. The DVD can be mounted, but the data is inaccessible. As a result, you cannot set up an install server, perform a Live Upgrade, or access any data on the media.
Workaround: Choose one of the following workarounds:
Apply the patches that are appropriate for your system.
Release |
Patch ID |
---|---|
Solaris 2.6 |
107618-03 |
Solaris 7 |
107259-03 |
Solaris 2.6 |
107619-03 |
Solaris 7 |
107260-03 |
Mount the Solaris 9 4/04 DVD manually. Do not use Volume Management to mount the DVD. Follow these steps:
Become superuser.
Stop Volume Management.
# /etc/init.d/volmgt stop |
Mount the DVD manually.
# mkdir /mnt1 # mount -F hsfs -o ro /dev/dsk/c0t6d0s0 /mnt1 |
Verify that the DVD is mounted. Then verify that the data is accessible.
# cd /mnt1 # ls |
The system returns the following information if the DVD is correctly mounted.
Copyright Solaris_9 |
The following installation bugs apply to the Solaris 9 4/04 release.
If the Solaris Web Start program is installing packages into an alternate root, and then fails or is manually aborted, the installer might not remove packages that were already installed. In addition, the installer reports that the partially installed product was uninstalled successfully.
The Solaris Web Start program installs packages by invoking the pkgadd command. If the installer program is installing software into an alternate root, the program passes the alternate root to the pkgadd command by using the -R argument.
Installation logs might indicate that some packages were successfully installed and that some packages to be uninstalled were not found.
Workaround: After rebooting the system, manually remove the packages by using the pkgrm command.
If you install the Solaris 9 4/04 software by using the Solaris Web Start installation program, some of the information and exit panels for the Sun SM 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.
This problem might also manifest itself during a Solaris Web Start installation of other software products that are included in this Solaris OS release.
Workaround: Follow these steps:
Bypass the SRS Net Connect installation by clicking the Cancel button when the empty installation panel is displayed.
After the installation of the Solaris 9 4/04 software has completed, manually install the SRS Net Connect software from the Solaris DVD or Software 2 of 2 CD.
Installing the SRS Net Connect software after the initial Solaris 9 4/04 software installation has completed will ensure that all panels are displayed properly.
If you use the Preboot Execution Environment (PXE) to install the Solaris software with a 3Com 3C905C network card, the system might hang and fail to boot.
Workaround: Use the 3Com Managed Boot Agent (MBA) version 4.11 with the 3Com 3C905C network card. Or, use a different type of network card.
If you install or upgrade to the Solaris 9 4/04 release on a system with multiple network interfaces, the system recognizes all system interfaces as usable. Interfaces that are not connected to the network, or that are not intended for use, appear in the output of the ifconfig -a command. Additionally, interfaces with identical Ethernet addresses might be assigned identical IP addresses. The following error message is displayed:
ifconfig: setifflags: SIOCSLIFFLAGS: qfe3: Cannot assign requested address |
This problem also occurs on systems that have the local-mac-address
PROM variable set to false. The problem occurs because
all interfaces are configured with the same IP address.
Workaround: Choose one of the following workarounds:
To plumb only the configured interface, reboot the system after the initial boot.
To assign a different IP address to each network interface, set the local-mac-address
PROM variable to true in one of
the following ways:
At the ok prompt, type the following command:
ok setenv local-mac-address? true |
In a terminal window, type the following command as superuser:
# eeprom local-mac-address?=true |
The following bug occurs during installation of the Solaris 9 4/04 Software 1 of 2 CD.
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.
The following are installation issues that occur during an upgrade to the Solaris 9 4/04 release.
Correct operation of Solaris Live Upgrade requires that a limited set of patch revisions be installed for a given OS version.
Before installing or running Live Upgrade, you are required to install a limited set of patch revisions. Make sure you have the most recently updated patch list by consulting http://sunsolve.sun.com. For additional information, search for the info Doc 72099 on the SunSolve web site.
If you are running the Solaris 2.6, Solaris 7, or Solaris 8 release, you might not be able to run the Solaris Live Upgrade installer. These releases do not contain the set of patches that is needed to run the JavaTM 2 runtime environment.
The typical failure that results is a Java exception error. The following are messages that might be displayed:
InvocationTargetException in ArchiveReader constructornull java.lang.reflect.InvocationTargetException at install.instantiateArchiveReader(Compiled Code) at install.<init>(Compiled Code) at install.main(Compiled Code) |
To run the Solaris Live Upgrade installer and install the packages, you must have the Java 2 runtime environment recommended patch cluster.
Workaround: Complete the following workaround:
Install the Solaris Live Upgrade packages by using the pkgadd command.
For step-by-step instructions, refer to Chapter 35, Using Solaris Live Upgrade to Create a Boot Environment (Tasks), in Solaris 9 4/04 Installation Guide.
Install the Java 2 runtime environment recommended patch cluster. The patch cluster is available on http://sunsolve.sun.com. Then, you can use the Solaris Live Upgrade installer to install the packages.
If your Solaris 8 system is connected to storage area networks (SANs), check with your support engineer before you upgrade to the Solaris 9 4/04 release. Solaris 8 systems that have the SUNWsan package installed might require special procedures to upgrade to the Solaris 9 4/04 release. To find out if the SUNWsan package is installed on the system, type the following command in a terminal window:
# pkginfo SUNWsan |
If the SUNWsan package is installed, the following information is displayed:
system SUNWsan SAN Foundation Kit |
You cannot use the Solaris 9 4/04 (x86 Platform Edition) Installation CD to upgrade x86-based systems from the Solaris 2.6 or the Solaris 7 software to the Solaris 9 4/04 release. The upgrade cannot be performed because of the x86 boot-partition requirement.
Workaround: On x86-based systems, use the Solaris 9 4/04 Software (x86 Platform Edition) 1 of 2 CD to upgrade from the Solaris 2.6 or the Solaris 7 software to the Solaris 9 4/04 release.
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 9 4/04 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 9 4/04 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 9 4/04 Software 1 of 2 CD into your CD-ROM drive. Type the following in a terminal window:
# cd /cdrom/sol_9_404_sparcia/s0/Solaris_9/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.
The following installation bugs occur during an upgrade to the Solaris 9 4/04 release.
If you are installing a Solaris Flash archive, a file appears to be new and causes the update to fail. The Solaris Flash software verifies that the files on the clone system are an exact duplicate of the master system. The reboot_processing script is not deleted at reboot. As a result, this file is recognized by the Flash software as a new file.
The following error message is displayed:
New files detected: /etc/init.d/flash_reboot_processing |
Workaround: To avoid encountering this problem, choose from one of the following workarounds:
Delete the flash_reboot_processing file before you install the Solaris Flash archive on the clone system.
When installing the differential archive, you can use the custom JumpStart forced_deployment keyword to force the installation. The new files that are detected on the clone are deleted during the installation, and the installation completes.
When installing the differential archive, you can use the custom JumpStart no_content_check keyword in the profile to turn off file checking. The software performs no file checking, no files are deleted, and the installation completes.
You can exclude the file when you create the differential archive. During the archive creation, this file is added to a file filter. The file is then ignored during the archive installation. Follow these steps:
Boot the master system.
To exclude the /etc/init.d/flash_reboot_processing file during the archive creation, type the following command:
# flarcreate -n archive-name -A unchanged-master-image-dir-x \ /etc/init.d/flash-reboot-processing path/filename |
During the creation of a differential archive, you can use the -M option to switch off file checking. No file manifest is created. As a result, the files on the clone system are not checked. Follow these steps:
Boot the master system.
To use the -M option to switch off file checking, type the following command:
# flarcreate -n archive-name -A unchanged_master_image_dir -M path/filename |
archive-name – Is the name you give the archive.
-A option – Is the unchanged-master-image-dir, which creates a differential archive by comparing a new system image with the image that is specified by the unchanged-master-image-dir argument.
path – Is the path to the directory in which you want to save the archive file. If you do not specify a path, the flarcreate command saves the archive file in the current directory.
filename – Is the name of the archive file.
For more information, see the Solaris 9 4/04 Installation Guide.
When using the Solaris Live Upgrade luupgrade(1M) command with the -i option to complete an upgrade of an inactive boot environment, the text that the installers display might be unreadable in some languages. The text is corrupted when the installers request fonts that do not exist on the older release that is on the current boot environment.
Workaround: Choose one of the following workarounds:
Use a combined network installation image to do the installation.
Enable the C locale by setting the environment variable on your system.
When you upgrade from the Solaris 8 software to the Solaris 9 or the Solaris 9 4/04 release, a problem is encountered when the SUNWjxcft package is removed. The following error message is recorded in the upgrade_log file:
Removing package SUNWjxcft: Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TTbitmaps/fonts.upr Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TTbitmaps/fonts.scale Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TTbitmaps/fonts.alias Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TT/fonts.upr Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TT/fonts.scale Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TT/fonts.alias Removal of <SUNWjxcft> was successful |
Workaround: Ignore the error message.
If you upgrade to the Solaris 9 4/04 release on a system that is running a third-party Secure Shell, such as OpenSSH from the /etc/init.d/sshd daemon, the upgrade disables the existing Secure Shell daemon. During an upgrade, the Solaris 9 4/04 software overwrites the contents of /etc/init.d/sshd.
Workaround: Choose one of the following workarounds:
If you do not want the Secure Shell protocol server program on your system, do not install the SUNWsshdr and SUNWsshdu packages during the upgrade.
If you do not want the Secure Shell protocol server or client programs on your system, do not install the Secure Shell Cluster (SUNWCssh) during the upgrade.
If the /export directory is near full capacity when you upgrade to the Solaris 9 4/04 release, space requirements for /export are miscalculated. The upgrade then fails. This problem commonly occurs if a diskless client is installed. Another instance of when the problem occurs is when third-party software is installed in the /export directory. The following message is displayed:
WARNING: Insufficient space for the upgrade. |
Workaround: Before you upgrade, choose one of the following workarounds:
Rename the /export directory temporarily, until the upgrade is completed.
Temporarily comment out the /export line in the /etc/vfstab file until the upgrade is completed.
If /export is a separate file system, then unmount /export before you perform the upgrade.
If your system currently supports diskless clients that were installed with the Solstice AdminSuiteTM 2.3 Diskless Client tool, you must perform the following two steps:
Delete all existing diskless clients that are the same Solaris version and architecture as the server.
Install or upgrade to the Solaris 9 4/04 release.
For specific instructions, see the System Administration Guide: Basic Administration.
If you attempt to install the Solaris 9 4/04 software over existing diskless clients, the following error message might be displayed:
The Solaris Version (Solaris version-number) on slice <xxxxxxxx> cannot be upgraded. There is an unknown problem with the software configuration installed on this disk. |
In this error message, version-number refers to the Solaris version that is currently running on your system. <xxxxxxxx> refers to the slice that is running this version of the Solaris software.
The following installation bug occurs after you upgrade to the Solaris 9 4/04 release.
The WBEM Repository Common Information Model (CIM) database can be corrupted under the following conditions:
You apply a revision of patch 112945 for a Solaris 9 release to a system that is running the Solaris 9 software.
You then remove the patch that was applied to the system.
If the WBEM Repository is corrupted, the following error message is displayed in the Solaris Management Console Log Viewer:
CIM_ERR_FAILED: /usr/sadm/lib/wbem/../../../../var/sadm/wbem/logr/ preReg/PATCH113829install/Solaris_Application.mof,18,ERR_SEM, ERR_EXC_SET_CLASS,CIM_ERR_FAILED:Other Exception: java.io.StreamCorruptedException: invalid stream header |
Workaround: Choose one of the following workarounds:
Follow these steps to prevent the WBEM Repository from being corrupted:
Become superuser.
Before you apply the patch, back up the WBEM Repository.
# cp -r /var/sadm/wbem/logr path/logr |
where path is the path to the backup WBEM Repository.
If the WBEM Repository is corrupted after you back out the patch, stop the WBEM server.
# /etc/init.d/init.wbem stop |
Restore the backup WBEM Repository.
# cp -rf path/logr /var/sadm/wbem/logr |
Restart the WBEM server.
# /etc/init.d/init.wbem start |
Follow these steps to create a new WBEM Repository:
This workaround does not restore the WBEM data if the WBEM Repository is corrupted. Any data that was added to the repository during the installation is lost.
Become superuser.
Stop the WBEM server.
# /etc/init.d/init.wbem stop |
Remove the files from the /logr directory.
# rm /var/sadm/wbem/logr/* |
Remove the /notFirstTime directory.
# rmdir notFirstTime |
Start the WBEM server.
# /etc/init.d/init.wbem start |
Compile any proprietary Managed Object Format (MOF) files manually.
# /usr/sadm/bin/mofcomp MOF-filename |
The following 64–bit issue applies to the Solaris 9 4/04 release.
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 software on an UltraSPARCTM system, you might need to update the system's flash PROM firmware. The Solaris 9 4/04 installation programs enable you to add 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 software on any SunTM or UltraSPARC system, the flash PROM update is not needed.
The following table lists the UltraSPARC (Sun4UTM) systems that are affected and the minimum firmware versions that are needed. System type is the equivalent of the output of the uname -i command. You can determine which firmware version that 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-1-Engine |
3.10.0 |
SUNW,Ultra-1 |
3.11.1 |
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 on how to perform the flash PROM update by using the Solaris CD, refer to the Solaris 9 on Sun Hardware Collection. You can obtain the manual at http://docs.sun.com.
The follwoing Documentation CD issue applies to the Solaris 9 4/04 release.
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.
No patches exist at the time of this release for Solaris 2.6 servers.
Workaround: For instructions on how to install these patches, see the Solaris Documentation Important Information file on the documentation media, Solaris 9 4/04 Documentation CD 1 of 2, 2 of 2, or DVD. This file is located in the following directory:
mount-point/README/locale/install_locale.html |
For example, the English file on the Solaris 9 4/04 Documentation CD 1 of 2 is located in the following directory:
sol_9_doc_1of2/README/C/install_C.html |
The following Documentation CD installation bugs apply to the Solaris 9 4/04 release.
If you run the Solaris 9 4/04 Documentation CD uninstaller in Uninstall All mode, the uninstaller removes only those documentation packages that are installed by default.
Workaround: Run the uninstaller in Uninstall Partial mode. Select the specific packages that you want to uninstall.
If you use the Solaris 9 4/04 Documentation CD installer program with the nodisplay option, the verify panel might not page correctly.
Workaround: Do not specify the nodisplay option with the Solaris 9 4/04 Documentation CD installer program. Use the graphical user interface (GUI) mode to install the Solaris 9 4/04 Documentation CD.
The following is a Localization issue that occurs during installation of the Solaris 9 4/04 software.
When you select a locale for your installation, additional related locales might also be installed. This change in behavior occurs in the Solaris 9 4/04 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.
The following Localization bugs occur during installation of the Solaris 9 4/04 software.
If you use Solaris Live Upgrade with multiple CDs to install the Solaris 9 4/04 release, the Languages CD installs all languages by default.
After the installation, if you log in to the system in a locale that is different than the locale you selected during installation, garbled characters might be displayed. After you log in to any of these locales, the English locale is displayed.
Workaround: During installation, select the custom install option. Uncheck any languages that you do not want to install during the Languages CD installation.
Upgrading to the Solaris 9 4/04 release, on a system running the Solaris 8 software with the Solaris 8 Language Supplement CD installed, results in several invalid packages. Thai, Russian, Polish, and Catalan locale packages remain on the system. These locale packages have an ARCH=sparcall value and are not removed during the upgrade to the Solaris 9 4/04 release.
Workaround: Before you upgrade to the Solaris 9 4/04 release, use the Solaris Product Registry application to remove the Solaris 8 Languages Supplement CD packages.