This section contains installation bugs that you should be aware of before installing the Solaris 9 9/05 HW software.
This flash retrieval fails only for DVD GUI interactive flash installations if the password contains the special characters "@" ("at" sign) and " ' " (single quote). There is no problem with any of the other special characters.
Workaround:Choose a new password without the "@" or " ' " special characters.
SVM mirror creation fails or sometimes the installer hangs in the middle of installation. If installation is successful, a panic results after reboot. The following error messages are displayed:
Creation of SVM Metadb -- Hangs |
— or —
Panic after reboot |
Workaround:Create SVM volumes after the installation is complete.
The installation of SunSM Net Connect 3.1 from the Extra Value directory fails on Sun FireTM V1280 servers. The Sun Net Connect installation program incorrectly evaluates the capabilities of the Sun Fire V1280 server as a field-replaceable unit (FRU). Consequently, the installation fails and all installed Sun Net Connect packages are removed. The following error message is recorded in the installation logs:
Error: pkgadd failed for SUNWfrunc |
Workaround: Download the most recent version of the SRS Net Connect service from https://srsnetconnect3.sun.com.
If you use the Intel Preboot Execution Environment (PXE) to perform a network installation on a system with an Adaptec Ultra-160 SCSI interface, the installation hangs. An error similar to the following message might be displayed:
Error: Unable to Find Device Driver The device driver, cadp160.bef, is missing. |
In the previous example, the cadp160.bef driver is not found on the system. The name of the affected driver might differ on your system.
This error occurs if the system BIOS sets the Adaptec Ultra-160 interface to use the same interrupt request (IRQ) as the system network interface card (NIC).
Workaround: Choose one of the following workarounds.
To install over the network, remove the Adaptec Ultra-160 SCSI interface, and perform an installation over the network with PXE.
Install from the Solaris 9 9/04 DVD or CDs .
On a Sun LX50 system, the X server might be unable to open a PS/2 mouse device. The error might occur either during installation or when the system reboots. When the problem occurs, the following error message is displayed:
ddxSUNWmouse: Error opening mouse device '/dev/kdmouse; /dev/kdmouse: No such device or address |
Consequently, the Solaris installation program can proceed only in command-line interface mode. After installation, the problem might persist during Solaris runtime.
Workaround: On the Y-cable that connects to the server's PS/2 connector, switch the connections between the PS/2 keyboard and mouse.
If the PS/2 mouse remains unrecognized after a system reboot, press the LX50 server's Reset button. Alternatively, use the reconfigure option (b -r) when the following boot prompt appears:
Select (b)oot or (i)nterpreter: |
The re-preinstall command fails to install custom JumpStart software. The failure occurs because the fsck command cannot update the UFS log for file systems that have read-only permissions.
For example, you type the following command:
# /usr/sbin/install.d/re-preinstall cXt XdXsX
After the system is rebooted, the following error message is displayed:
fsck of device failed, re-preinstall needs to be re-run. syncing file systems... done Program terminated |
Workaround: Choose one of the following options. You must be superuser to perform either workaround.
Option 1: If you are using a writable network installation image, proceed with the following steps:
On the server that contains the installation image, edit the /usr/sbin/install.d/rcS.stub file to remove or comment out the following lines:
# # Make sure the root FS is clean # # /etc/fsck -F ufs -o p ${RootfsRaw} >/dev/null # if [ $? -ne 0 ]; then # echo "fsck of ${RootfsRaw} failed, re-preinstall needs to be re-run." # /usr/sbin/halt # if |
On the system where you are installing the JumpStart software, boot the network installation image in single-user mode:
ok boot net -s
Run the re-preinstall command as usual.
# /usr/sbin/install.d/re-preinstall cXt XdXsX
Option 2: If you are booting directly from the CD-ROM or DVD-ROM, proceed with the following steps:
Boot the CD or DVD.
Exit the installer.
Run the re-preinstall command.
Mount the device that you created in step 3.
For example, if in step 3 you typed re-preinstall c0t0d0s0, mount this file system as follows:
# mount /dev/dsk/c0t0d0s0 /mnt
On the mounted file system, edit the sbin/rcS script to remove or comment out the same lines as in the first workaround.
Unmount the file system.
# umount /mnt
Reboot the system to continue installing the JumpStart software.
If your system is running the Solaris 2.6 or the Solaris 7 software, Volume Management incorrectly mounts the Solaris 9 9/05 HW 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 9/05 HW 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 |