Installation Bugs

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

Locales Problem After Upgrading a System With Non-Global Zones Installed (6494427)

If you are upgrading to the Solaris 10 11/06 release and your system contains non-global zones, the locales setting is incorrect. The locales are unset after an upgrade. No error message is displayed.

Workaround: Perform the following steps:

1. Before the upgrade, make a copy of the /var/sadm/system/admin/data/install_locales file before the upgrade.

2. After the upgrade, copy the same file to the upgraded install_locales file.

Zones With an fs Resource Defined With a Type of lofs Cannot Be Upgraded to Solaris 10 11/06 (6454140)

If all non-global zones that are configured with lofs fs resources are mounting directories that exist in the miniroot, the system can be upgraded from an earlier Solaris 10 release to the Solaris 10 11/06 release using standard upgrade. For example, a lofs mounted /opt directory presents no issues for upgrade.

However, if any of the non-global zones are configured with a non-standard lofs mount, such as a lofs mounted /usr/local directory, the following error message is displayed:

The zones upgrade failed and the system needs to be restored
 from backup.  More details can be found in the file
 /var/sadm/install_data/upgrade_log on the upgrade root file
 system.

Although this error message states that the system must be restored from backup, the system is actually fine, and it can be upgraded successfully using the workaround.

Workaround:

1. Reboot the system with the installed OS.

2. Reconfigure the zones, removing the fs resources that are defined with a type of lofs.

3. After removing these resources, upgrade the system to Solaris 10 11/06.

4. Following the upgrade, reconfigure the zones again to restore the additional fs resources that were removed.

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

x86: Install Hangs on Systems With 512 Mbyte of Memory (6423854)

Installations can run out of memory and hang on 512-Mbyte systems under the following conditions:

• You install using a network installation image of the OS.

• The Solaris installation program is in a windowing environment:

  • The graphical user interface (GUI).

  • The -text option or “3. Solaris Interactive Text (Desktop session)” in the menu below.

When the system exhausts available memory, the GUI installation process slows and eventually fails. The text does not display in a windowing environment.

Workaround:

To avoid this problem, select a non-windowing environment during the initial installation startup. During startup from the installation media the following menu is displayed:

-----------
 1.     Solaris Interactive (default)
 2.     Custom JumpStart
 3.     Solaris Interactive Text (Desktop session)
 4.     Solaris Interactive Text (Console session)
 5.     Apply driver updates
 6.     Single user shell
 Enter the number of your choice.
 -----------

At this point, choose “4. Solaris Interactive Text (Console session)”. This non-windowing environment will initiate a text-only installation, without using memory-intense processes.

x86: SVM Upgrade Fails From Solaris 9 9/05 OS to Solaris 10 11/06 or to Solaris Express (6397251)

If you upgrade a Solaris Volume Manager (SVM) on x86 platforms, the upgrade fails. The failure occurs if the SVM volume is configured on the root (/) file system and you upgrade from the Solaris 9 9/05 OS to the Solaris 10 11/06 OS or to a Solaris Express release.

The following error message is displayed:

Processing profile

ERROR: The specified root and/or boot was not found or was not upgradeable
Solaris installation program exited.

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:

• Regular system log messages indicates a path issue, such as offline or online.

• Cfgadm -al command. This command shows the failed condition for the tape device.

• I/O to a tape device has ceased.

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.

x86: Custom JumpStart Profile Test Fails With Locale Keyword (6340509)

When you test your JumpStart profile using the pfinstall -D command, the dry run test fails under the following conditions:

• The profile contains the locale keyword.

• You are testing a release that contains GRUB software. Starting with the Solaris 10 11/06 release, the GRUB boot loader facilitates booting different operating systems installed on your system with the GRUB menu.

With the introduction of GRUB software, the miniroot is compressed. The GRUB software can no longer find the list of locales from the compressed miniroot. Aminiroot is the smallest possible Solaris root (/) file system and is found on the Solaris installation media.

The following error message is displayed:

Could not select locale

Workaround:

The script values are as follows:

• MEDIA_DIR=/cdrom/cdrom0/s0

• MINIROOT_DIR=$MEDIA_DIR/Solaris_10/Tools/Boot

• MINIROOT_ARCHIVE=$MEDIA_DIR/boot/x86.miniroot

• TEMP_FILE_NAME=/tmp/test

Perform the following steps:

1. Uncompress the miniroot archive.

   # /usr/bin/gzcat $MINIROOT_ARCHIVE > $TEMP_FILE_NAME

2. Create the miniroot device using the lofiadm command.

   # LOFI_DEVICE=/usr/sbin/lofiadm -a $TEMP_FILE_NAME
   # echo $LOFI_DEVICE/dev/lofi/1

3. Mount the miniroot with lofi under the miniroot directory.

   # /usr/sbin/mount -F ufs $LOFI_DEVICE $MINIROOT_DIR

4. Test the profile.

   # /usr/sbin/install.d/pfinstall -D -c $MEDIA_DIR $path-to-jumpstart_profile

5. After the pfinstall testing is completed, unmount the lofi device.

   # umount $LOFI_DEVICE

6. Delete the lofi device.

   # lofiadm -d $TEMP_FILE_NAME

x86: Invalid /sbin/dhcpinfo Error During Installation (6332044)

If you install the Solaris 10 11/06 release on an x86 based system, the following error message is displayed.

/sbin/dhcpinfo: primary interface requested but no primary interface is set

The error does not affect the installation, and the installation succeeds.

Workaround: Ignore the error message.

x86: Installation From CD Media Appears to Hang After Reboot Selection (6270371)

A problem might occur when you are using the Solaris installation program and are using CD media. After the installation of the Solaris software from the Solaris 10 11/06 Software CD - 4, the following prompt is displayed:

Press Reboot now to continue.

If you press Reboot, the system might not respond. The installation is successful. However, the error prevents the installation program from exiting normally. Consequently, the typical postinstallation cleanup and system reboot cannot occur.

An error message similar to the following example is logged in /tmp/disk0_install.log file:

Exception in thread "Thread-70" java.lang.IndexOutOfBoundsException:
Index: 6, Size: 5
     at java.util.ArrayList.add(ArrayList.java:369)
     at
com.sun.wizards.core.WizardTreeManager.
actualExitButtonPressed(WizardTreeManager.java:1499)
     at
com.sun.wizards.core.WizardTreeManager.
exitButtonPressed(WizardTreeManager.java:1486)
     at
com.sun.wizards.core.AutonextController.
run(AutonextController.java:736)
     at
java.lang.Thread.run(Thread.java:595)

Workaround: Choose one of the following workarounds.

• Workaround 1: Follow these steps.

  1. Shut down the system, then turn on the power again.

  2. After the system starts up, insert the appropriate CD at the prompt. Although the CD is inserted, no additional software is installed on the system. In a moment, the system reboots normally.

• Workaround 2: Follow these steps.

  1. Open a terminal window.

  2. Log in as superuser.

  3. Create or modify access to the .instsuccess file.

     # touch /tmp/.instsuccess

  4. Stop the Java process.

     # pkill -9 java

     The system reboots without prompting for the CD media.

x86: kdmconfig Program Runs Twice After Initial Installation (6209092)

During the first system reboot after an initial Solaris 10 OS installation, the kdmconfig program might run twice. During this initial startup, each time the program starts, you are prompted to select an X server. This situation occurs on x86 based systems that have not been configured to use the X server. An example of such a system is a “headless” system that is not using a graphics display.

Workaround: Each time the program starts and prompts for an X server, press F3_Exit. A short delay might occur before the startup process resumes. After this initial startup is completed, the problem no longer occurs if the system is subsequently rebooted.

x86: System Fails to Boot After Custom JumpStart Installation (6205478)

If you use the Custom JumpStart installation method to install on an x86 based system, and explicitly configure slice 2 as the overlap slice in the profile, an error occurs. The system does not reboot successfully after the installation is completed. The following error message is displayed:

Cannot find Solaris partition

This failure occurs because the overlap slice 2 (c0t0d0s2, for example) is set to begin at cylinder 1 rather than cylinder 0.

Workaround: In the Custom JumpStart profile, remove the filesys keyword entry that configures slice 2 as the overlap slice. For example, you would remove a keyword entry that is similar to the following entry.

filesys c0t0d0s2 all overlap

After you remove the entry, perform the Custom JumpStart installation.

x86: GUI Interactive Installation From DVD Fails if boot-device Variable Is Not Set (5065465)

If you install Solaris from the Solaris 10 Operating System DVD, the interactive GUI installation might fail. This failure occurs if the boot-device configuration variable is not set on the system.

To determine if the boot-device configuration variable is set, type the following command.

# prtconf -pv | grep boot-device

If the output of this command is boot-device: with no associated device, you cannot use the interactive GUI installation program to install from the Solaris 10 Operating System DVD.

Workaround: Use the interactive text installer to install Solaris 10 software. When the installation program asks you to select a type of installation, select option 3, Solaris Interactive Text (Desktop Session).

For more information about installing from the Solaris 10 Operating System DVD, see Solaris 10 11/06 Installation Guide: Basic Installations.

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

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.

x86: USB Keyboards Might Freeze During Install on Some Dell Precision Workstations (4888849)

During installation, USB keyboards on some Dell Precision Workstations might freeze or become partially inoperative, thereby preventing installation.

Workaround: Perform one of the following workarounds:

• Switch the USB emulation mode in the firmware.

• Switch to a PS/2 keyboard.

• Reboot and try again.

Alternatively, update the system's BIOS to resolve the problem.

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.