The following bugs might occur during or after the installation of Solaris 10 OS.
Some Asian locales like, th_TH.ISO8859-11, th_TH.TIS620, ko_KR.EUC, ko_KR.UTF-8, zh_TW.EUC, zh_CN.EUC, zh_CN.GBK, and zh_CN.UTF-8 cannot be used while installing with Custom JumpStart. While setting locales in the sysidcfg file using the system_locale keyword, the following error message is displayed:
xx_xx.xxxxx is not a valid system locale
The JumpStart installation is stopped and Interactive installation starts.
Workaround: Use shorter locale names such as th_TH, ko, ko.UTF-8, zh_TW, zh, zh.GBK, and zh.UTF-8, instead of longer locale names,
Upgrading to the Solaris 10 5/08 release when running the co-packaged Solaris 8 Migration Assistant software fails. No error message is displayed. The system panics when a Solaris 8 branded zone is booted.
Workaround: Install the Solaris 8 Migration Assistant patch #128548-02 or later. This patch is recommended for all kernels. The patch #128548-02 or later should also be installed before installing Solaris 10 8/07 release Kernel patch 127111-05 or later. Revision #128548-04 or later is required for UltraSparc IV based systems running Solaris 8 Migration Assistant. The most recent revision of patch #128548 is recommended in all cases.
Solaris 10 8/07 release Kernel patch 127111-05 or later
While upgrading Solaris Trusted Extensions from the Solaris 10 11/06 or Solaris 10 8/07 release to the current Solaris 10 5/08 release, the prodreg entry for Solaris Trusted extensions is not removed. No error message is displayed.
Workaround: After upgrading Solaris Trusted Extensions to the current release, remove the prodreg entry manually as follows:
# prodreg unregister -f -r -u "Solaris Trusted Extensions" -i 1
After you install the Solaris OS, the Reboot Now button does not work.
Workaround: Perform the following steps:
Open a terminal window.
Type the following commands:
# touch /tmp/.instsuccess # pkill -9 java
The system now reboots and does not require CDs.
During a Solaris upgrade, if you select Detailed Analysis to see the patches that will be removed, the panel that displays the patches is not scrollable. The complete list of patches to be removed cannot be viewed.
Workaround: Run the analyze_patches scripts manually:
# cd <cdrom>/Solaris_10/Misc # ./analyze_patches -R rootdir -N netdir -D databasedir
The command options are as follows:
rootdir is the root of the installed system. The default root directory is /.
netdir is the path to the root of the OS image to be installed. /cdrom/cdrom0 is the default path. netdir is the path to the directory that contains the Solaris_10_606 directory. You must use this option if you are running the patch_analyzer from an NFS mount point.
If the script is called from a directory other than the /Misc directory in the OS image, the program cannot find the database it uses for patch analysis. Use the -D option to supply the path to the database. Without this database, which is located in the Solaris_10_606/Misc/database directory on the OS image, the script will not run correctly.
On a SPARC system, when using a CD (CD1) to upgrade your system by using Live Upgrade, the luupgrade command fails. The following error message is displayed.
# luupgrade -u -n s10u4_ABE -s /cdrom/cdrom0/s0 -j /var/tmp/profile 179536 blocks miniroot filesystem is <lofs> Mounting miniroot at </cdrom/cdrom0/s0/Solaris_10/Tools/Boot> mount: /tmp/miniroot.3694: Device busy ERROR: Cannot mount miniroot at </cdrom/cdrom0/s0/Solaris_10/Tools/Boot>.
Workaround: Choose one of the following workarounds.
Workaround 1: Use the DVD physical media to do luupgrade.
Workaround 2: If the system does not have a DVD drive, then use setup_install_server from CD1 to create an image locally for the upgrade to use. Run the following commands:
# cd /cdrom/cdrom0/s0/Solaris_10/Tools # ./setup_install_server <local_location> # luupgrade -u -n s10u4_ABE -s <local_location>
The Solaris OS might panic with a null pointer dereference if the driver.conf file has been modified using the parent attribute. The following error message is displayed:
System panic: BAD TRAP: type=31 rp=2a101d31200 addr=8 mmu_fsr=0 occurred in module "pcie" due to a NULL pointer dereference
Workaround: Before you install the Solaris 10 8/07 or Solaris 10 5/08 OS on a PCI Express (PCIe) based SPARC system, check if you have modified the driver.conf files as described below:
Change to the /kernel/drv directory.
Check if the parent attribute is set in the driver.conf file. If the parent attribute has been set and the last node in the parent has the word pci in it, comment out that line. Ensure that you comment out the entire property. For example:
# name="ACME,simple" parent="/pci@7c0/pci@0/pci@9" # unit-address="3,1" debug-mode=12; name="ACME,example" parent="pseudo" instance=1; name="ACME,scsi" parent="/pci@7c0/pci@0/pci@9/scsi" unit-address="3,1" debug-mode=12;
Repeat step 2 for the driver.conf files in the following directories:
Install the Solaris 10 8/07 or Solaris 10 5/08 OS.
Install patch 127747-01.
Change to the directories listed in steps 1 and 3. Uncomment all the lines that were commented out in step 2 in the driver.conf files.
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:
Boot the Solaris OS.
Edit the menu.lst file at /boot/grub/menu.lst. For more information, see the System Administration Guide: Basic Administration.
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.
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.
If you install the Solaris 10 8/07 or Solaris 10 5/08 OS 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.
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 5/08 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.
Shut down the system, then turn on the power again.
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.
Open a terminal window.
Log in as superuser.
Create or modify access to the .instsuccess file.
# touch /tmp/.instsuccess
Stop the Java process.
# pkill -9 java
The system reboots without prompting for the CD media.
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.
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 5/08 Installation Guide: Basic Installations.
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.
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.
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.