Installation Bugs

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

Java Error Messages Are Displayed After a Solaris 10 OS Installation (6218158)

When the system reboots after a Solaris 10 OS installation is completed, Java error messages similar to the following example might be generated. These messages might either be displayed on the console or recorded in the /var/adm/messages file.

java[16552]: [ID 874347 user.error] libpkcs11:
open /var/run/kcfd_door: No such file or directory
java[16552]: [ID 523743 user.error] libpkcs11:
/usr/lib/security/pkcs11_softtoken.so
unexpected failure in ELF signature verification.
System may have been tampered with.
Cannot continue parsing /etc/crypto/pkcs11.conf
java[16580]: [ID 874347 user.error] libpkcs11:
open /var/run/kcfd_door: No such file or directory
java[16580]: [ID 523743 user.error] libpkcs11:
/usr/lib/security/pkcs11_softtoken.so
unexpected failure in ELF signature verification.
System may have been tampered with.
Cannot continue parsing /etc/crypto/pkcs11.conf

Workaround: None. Ignore the error messages.

Solaris 10 Installation Disc Ejects When You Install the Solaris Flash Archive (6215847)

During installation, the system might eject the disc and the installation might fail. This error might occur if you boot from a Solaris 10 installation disc. The installation disc can either be the Solaris 10 Operating System DVD or the Solaris 10 Software - 1 CD. After you boot the system, you attempt to install a Solaris Flash archive from the network.

The problem occurs under the following two sets of circumstances.

• While running the Solaris GUI installation program from the DVD or CD installation disc, you specify an invalid Solaris Flash archive for your system. For example, specifying a path to an x86 archive while installing on a SPARC based system would cause the error. After the disc ejects, messages similar to the following errors might be displayed in the console window.

  /sbin/install-solaris: rm: cannot execute
  /sbin/install-solaris: date: cannot execute
  /sbin/install-solaris: gettext: cannot execute.

• You run the Solaris text installer in a console session from the Solaris 10 installation disc and successfully install a Solaris Flash archive from the network. After the disc ejects, messages similar to the following errors might be displayed in the console window.

  /sbin/setup-launcher[310]: 1356 Killed
  /sbin/setup-launcher[315]: 1357 Killed

Workaround 1: If the error was caused by an invalid archive, complete one of the following steps, depending on the error triggers.

• Restart the installation with the GUI installation program. Then specify a path to a valid archive.

• Install the archive by using the text-based installer in a desktop windowing session:

  • For SPARC based systems, type boot cdrom -text at the ok prompt.

  • For x86 based systems, at the prompt to choose an installation type, select 3 Solaris Interactive Text (Desktop session).

Workaround 2: If the error occurred after you used the text-based installer in a console session, choose one of the following options:

• Use the installer in a desktop windowing session instead:

  • For SPARC based systems, type boot cdrom -text at the ok prompt.

  • For x86 based systems, at the prompt to choose an installation type, select 3 Solaris Interactive Text (Desktop session).

• Perform the following steps after the system ejects the installation disc.

  1. Reinsert the DVD or CD in the machine.

     • If the system responds to the disc insertion, allow the system to complete the installation.

     • If the system does not respond to the installation disc, go to Step 2.

  2. Manually reboot the system.

  3. If prompted, reboot the system.

     The installation is complete.

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.

Installation Logs Might Be Incomplete or Inaccurate (5087588)

If you install the Solaris 10 software, the install_log file in /var/sadm/system/logs and /var/sadm/install/logs might be incomplete. These logs might not include information about packages that were successfully added to the system, and they might not record errors encountered when adding packages. Consequently, you cannot use the install_log file as a resource to troubleshoot installation or application issues.

Workaround: If an application does not run correctly, do not check the install_log file to determine if the application packages were installed. Follow these steps.

1. Check the Solaris Product Registry to determine which packages the application uses.

   # prodreg

2. Use the pkginfo command to determine if any of these packages are partially installed.

   # pkginfo -p package-name

3. For each package that is reported in the output of the previous command, remove the package.

   # pkgrm options package-name

4. Reinstall each package.

   # pkgadd options package-name

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

/dev and /devices/pseudo Permissions Set Incorrectly After Installation (4720192, 6215918)

When you install the Solaris 10 OS, the /devices/pseudo namespace permissions might be set incorrectly. The system might not be able to access some system devices. Similar namespace-permission errors occur if you installed the Solaris 10 OS on a clone system with a Solaris Flash archive.

If you run the pkgchk -n command on the SUNWcsd package after the installation, a message similar to the following output is displayed.

# pkgchk -n SUNWcsd
ERROR: /devices/pseudo/cvc@0:cvc
 pathname does not exist
 unable to create character-special device
ERROR: /devices/pseudo/cvcredir@0:cvcredir
 pathname does not exist
 unable to create character-special device

If you installed the Solaris 10 OS on a clone system with a Solaris Flash archive, the previous command produces errors similar to the following output.

# pkgchk -n SUNWcsd
ERROR: /dev
      group name sys expected <(null)> actual
ERROR: /devices/pseudo/clone@0:eri
      permissions <0666> expected <0600> actual
ERROR: /devices/pseudo/clone@0:ibd
      permissions <0666> expected <0600> actual
ERROR: /devices/pseudo/cvc@0:cvc
     pathname does not exist
ERROR: /devices/pseudo/cvcredir@0:cvcredir
      pathname does not exist

For Solaris Flash installations, errors similar to the previous output are also displayed for the SUNWcsr package.

Workaround: Choose one of the following workarounds.

Workaround 1: Run the pkgchk -nf command on the SUNWcsd Core Solaris Devices package. This workaround applies if you installed Solaris 10 OS from CD or DVD media, or from a network installation image.

# pkgchk -nf SUNWcsd

Workaround 2: This workaround applies to clone systems on which you want to install the Solaris 10 OS by using a Solaris Flash archive. Perform the following steps before you install the archive:

1. On the master system, create a /etc/flash/reboot directory:

   # mkdir -p /etc/flash/reboot #

2. On the master system, create the following script in a text editor.

   #! /usr/bin/sh 
   # echo " Doing pkgchk -nf SUNWcsd" 
   pkgchk -nf SUNWcsd 
   echo " Doing pkgchk -nf SUNWcsr" 
   pkgchk -nf SUNWcsr 
   exit 0

3. Save the script with the file name pkgchk.cleanup in the /etc/flash/reboot directory.

4. Ensure that the pkgchk.cleanup script is executable.

   # cd /etc/flash/reboot
   # chmod a+x pkgchk.cleanup

5. Create the Solaris Flash archive.

6. Install the archive on the clone system.

However, if you have already installed the Solaris 10 OS with a Solaris Flash archive, then perform the following steps to resolve the error.

1. Run the pkgchk -nf command on the SUNWcsd Core Solaris Devices package.

   # pkgchk -nf SUNWcsd

2. Run the pkgchk -nf command on the SUNWcsr Core Solaris (Root) package on the clone system.

   # pkgchk -nf SUNWcsr

SPARC: Error Messages Might Be Seen When Installing Solaris By Using a Network Image (4704046)

You can install Solaris by using a network image. If that image is created by combining the Solaris 10 Software CDs, the following error messages might be seen:

Error message:    Jun 18 10:51:53 b26b statd[149]: [ID 514559 
daemon.error] svc_tp_create: Could not register prog 100024 vers 1 on udp 
Jun 18 10:51:53 b26b statd[149]: [ID 514559 daemon.error] svc_tp_create: 
Could not register prog 100024 vers 1 on tcp 
Jun 18 10:51:53 b26b statd[149]: [ID 514559 daemon.error] svc_tp_create: 
Could not register prog 100024 vers 1 on ticlts 
Jun 18 10:51:53 b26b statd[149]: [ID 514559 daemon.error] svc_tp_create: 
Could not register prog 100024 vers 1 on ticotsord 
Jun 18 10:51:53 b26b statd[149]: [ID 514559 daemon.error] svc_tp_create: 
Could not register prog 100024 vers 1 on ticots 
Jun 18 10:51:53 b26b statd[149]: [ID 447212 daemon.error] statd: 
unable to create (SM_PROG, SM_VERS) for netpath.

Workaround: None. Ignore the message. After the system boots, the Network File System (NFS) functions normally.

SPARC: Systems With Multiple Interfaces Recognize All Interfaces as Usable After Installation or Upgrade (4640568)

If you install or upgrade to the Solaris 10 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

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.