| Skip Navigation Links | |
| Exit Print View | |
|
Solaris 10 Release Notes |
1. Updates to Solaris 10 Release
New Minimum Memory Requirement
Changes in Upgrade Support for Solaris Releases
Solaris Live Upgrade and Solaris Zones
Patching Miniroot on x86 Machines
Correct Solaris Data Encryption Supplement Required for Installation of Solaris 10 1/06 Release
Additional Procedures Required When Installing Patches for Solaris 10 1/06 Release
Resolving Issues With the GNOME Display Manager (6277164)
Resolving Issues With AccessKeyMouseListeners (6214222)
x86: Cannot Configure Full-Screen Magnification on Systems With One Video Card
x86: Problems Configuring USB Mouse Device as Extension Device for Use With GNOME On-Screen Keyboard
StarOffice Patch Application Requires Additional Steps
SPARC: Upgrade Hangs on Sun Blade 1500 Workstations (6363365)
x86: Failure of BIOS Device Utility Prevents Installation or Upgrade From Being Completed (6362108)
Locale Problem Occurs After You Upgrade a System That Contains Zones (6361672)
Postinstallation Problems With Whole Root Zone, Diskless Client, and Solaris Live Upgrade (6358227)
x86: Adding Driver Updates Might Cause Failure of Network Configuration (6353146)
Using mkfs Command to Create File System Might Fail on Very Large Disks (6352813)
Generic LAN Driver Version 3 Fails to Set Field Length of Logical Link Control Frames (6350869)
x86: Problem With Choosing a Terminal Type When Installing Solaris 10 1/06 Software (6350819)
Adding Regions Fails With the localeadm Command (6350486)
x86: Systems With Multiple CPUs Might Hang During Installation or System Boot (6348316)
SPARC: Problems With dbx Debugger While Processing 64-bit Objects (6347707)
x86: Bulgarian Locale Uses Russian Character Map (6346843)
File System Creation Might Fail on Small Slices (6346510)
Undetected Write Errors in NFSv4 Client With Full File System (6346204)
Launch Menu Cannot Be Opened With Ctrl-Esc (6340714)
x86: Problems With dtlogin When Using UTF-8 Locales (6334517)
Unloading the e1000g Ethernet Driver Might Cause a System Panic (6333461)
x86: Invalid /sbin/dhcpinfo Error During Installation (6332044)
SPARC: Problems Configuring Preferences With the GNOME On-Screen Keyboard (6329929)
SPARC: Loadkeys Warnings Appear When System Is Booted From Solaris OS DVD (6329642)
Serbian Locale Uses Russian Character Map (6314583)
SPARC: Error Messages Displayed During Dynamic Reconfiguration (6312424)
SUNWceuow Package Improperly Upgraded if Symbolic Links to Solaris OS Are Changed (6303564)
x86: GNOME Applications Fail With dtremote (6278039)
Full-Screen Magnification and Keyboard Accessibility Features Not Working (6273030)
x86: Installation From CD Media Appears to Hang After Reboot Selection (6270371)
Error Messages Displayed by pkgchk After You Remove Patches for Zones (6267966)
Outdated List of Allowed Applications for Solaris OS (6267922)
Upgrade Option Unavailable if the Root (/) File System Is a RAID-1 Volume (Mirror) (6263122)
Cannot Create a Solaris Flash Archive When Solaris Zones Are Installed (6246943)
Solaris Live Upgrade luupgrade Command Missing the Progress Bar (6239850)
CD Quality, Lossless Mode Fails at Start of Recording (6227666)
Desktop Icons Invisible on Second Desktop System (6211279)
Intermittent Errors Might Occur With the Use of DataDigests (5108515)
Devices Not Immediately Available in Fabric Zones in a Storage Area Network (5077933)
5. End-of-Software Support Statements
A. Table of Integrated Bugs in the Solaris 10 Operating System
The following bugs and issues apply to Solaris 10 1/06 software.
Beginning with the Solaris 10 1/06 release, all x86 based systems must now have at least 256 Mbytes of RAM to run the Solaris software.
Starting with the Solaris 10 1/06 release, you can upgrade the Solaris OS only from the following releases:
Solaris 8 OS
Solaris 9 OS
Solaris 10 OS
To upgrade releases previous to the Solaris 8 software to the Solaris 10 1/06 software, upgrade to any of the releases in the preceding list first. Then upgrade to the Solaris 10 1/06 release.
Using Solaris Live Upgrade in conjunction with Solaris zones is not supported. If you have installed non-global zones on a Solaris 10 system, you cannot upgrade to the Solaris 10 1/06 release by using Solaris Live Upgrade.
If you use the luupgrade command, the following error message is displayed:
Unable to upgrade boot environment.
Workaround: To upgrade such a system, use either the Solaris interactive installation program or the custom JumpStart program. These programs apply to your Solaris 10 OS all the patches and new packages that represent the differences between your current OS and the Solaris 10 1/06 software. The programs also apply the packages and patches to all the non-global zones.
Both programs have limitations. For example, you cannot customize your upgrade by installing additional software products or additional locale packages, or by modifying the disk layout. For details about these limitations, see the Upgrading the Solaris OS When Non-Global Zones Are Installed in Solaris 10 Installation Guide: Custom JumpStart and Advanced Installations.
The procedures for using patchadd with the -C destination specifier to patch a miniroot on an x86 machine have changed. You must now unpack the miniroot, apply patches, then repack the miniroot.
See the following for the detailed steps:
When you install the Solaris 10 1/06 release, you must use the Solaris Data Encryption Supplement that corresponds to the release. The supplement is delivered in the SUNWcry and SUNWcryr packages. If you do not have the correct supplement version, upgrade the supplement by installing the appropriate patch:
Patch ID 118562-05 or a later revision for SPARC based systems
Patch ID 118563-04 or a later revision for x86 based systems
To determine your current supplement version, use showrev -p.
The following patches are applied to resolve problems that were reported in CR 6277164 and CR 6214222:
Patch ID 119366-05 for SPARC based systems
Patch ID 119367-05 for x86 based systems
The sections that follow provide further steps that you must perform to completely resolve the reported problems.
Note - Perform this procedure before you use the GNOME Display Manager (GDM) as your login program, or if you have already enabled GDM as your login program. Otherwise, you can skip this procedure.
When applying the patch, load new values into the GDM configuration files. Then restart the GDM application.
To load the new values into the configuration file, choose one of the following options.
Copy the /etc/X11/gdm/factory-gdm.conf file to the /etc/X11/gdm/gdm.conf file.
Perform this step if you have not made any modifications to the gdm.conf file. Then you can start the GDM application.
Manually merge the differences in the factory-gdm.conf file into the gdm.conf file.
Perform this step if you have modified the gdm.conf file and want to retain your modifications.
When merging files, copy the values for the following commands from the factory-gdm.conf file to the gdm.conf file. These commands enable you to obtain the best OS performance.
RebootCommand
HaltCommand
SuspendCommand
DefaultPath
RootPath
GraphicalTheme
To restart GDM, perform the following steps:
Become superuser.
Issue the following command:
# svcadm disable application/gdm2-login
In the console that is now displayed, press Return to display a command prompt.
To restart GDM, issue the following command:
# svcadm enable application/gdm2-login
To further resolve problems that are reported in CR 6214222, perform these steps when applying the patch.
Change to the /etc/X11/gdm/modules directory.
Copy the files from factory-AccessDwellMouseEvents to AccessDwellMouseEvents.
Copy the files from factory-AccessKeyMouseEvents to AccessKeyMouseEvents.
Restart GDM by following the steps that are provided in the previous section.
If your Solaris 10 system has a single physical video card, you cannot configure the system for full-screen magnification. For such a configuration, you must use a separate configuration file in which you define settings for a dummy driver. First, make sure that the Xserver is not running. Then perform the following steps:
Log in to a command-line session.
If you are using the GNOME Display Manager, follow these steps:
Log in to a session as superuser.
At the prompt, type svcadm disable application/gdm2-login .
Log in again as superuser.
If you are using dtlogin, follow these steps:
In the dtlogin window, click Options and select Command Line Login.
Log in as superuser.
Create a new xorg.conf file.
# /usr/X11/bin/Xorg -configure
The command creates the file xorg.conf.new in the root (/) directory.
Copy the new configuration file to the /etc/x11 directory and rename the file xorg.conf.
# cp /xorg.conf.new /etc/X11/xorg.conf
Modify the configurations in the file by using the following sample configurations:
Add a new monitor section.
Section "Monitor"
Identifier "monitor_dummy"
ModelName "dummy"
HorizSync 10-200
VertRefresh 20-90
EndSectionAdd a new device section.
Section "Device" BoardName "dummy" Driver "dummy" Identifier "device_dummy" VendorName "dummy" videoram 10000 EndSection
Note - You might need to adjust the videoram value, depending on the screen width, height, and color depth of your particular graphics card. The value in Kbytes must be large enough for the intended screen. For example, you can compute the value by using the formula width * height * bpp/8.
Add a new screen section.
Section "Screen"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1280x1024"
EndSubSection
Device "device_dummy"
Identifier "screen_dummy"
Monitor "monitor_dummy"
EndSection
Note - You might need to adjust the resolution value for your particular system setup.
Look for the following line under the ServerLayout section:
Screen 0 "Screen0" 0 0
Insert the following line below the line in the previous step:
Screen 1 "screen_dummy" RightOf "Screen0"
This new line defines Screen1, a second dummy screen that is notionally to the right of Screen0, the physical and primary screen.
Save the changes.
Reboot the system from the appropriate command-line session:
If you are using GDM, perform the following:
Type svcadm enable application/gdm2-login.
Reboot the system.
If you are using dtlogin, reboot the system and log in.
Start the Gnopernicus screen reader.
Change the Startup Mode to Magnifier.
Click Preferences, then select Magnifier.
Click Add/Modify.
Assign the following values for Magnifier preferences:
For Source: 0.1
For Zoomer Placement:
Left and Top: 0
Bottom and Right: maximum
Click Apply.
Because of the overlaying full-screen magnification zoomer, the Gnopernicus windows become invisible. However, full-screen magnification is now available.
You cannot set up a USB mouse device as an extension device with the GNOME On-Screen Keyboard (GOK). The configuration fails when you are setting up the USB mouse device while using a PS2 mouse device as the core pointer. To properly set up the USB mouse, follow these steps.
Log in as superuser.
While the USB mouse device is unplugged, type the following in a terminal window:
# ls -l /dev/usb/hid*
Connect the USB mouse and type the previous command again.
Record the path of the USB mouse that is displayed on the screen.
Log in to a command-line session.
If you are using the GNOME Display Manager, follow these steps:
Log in to a session as superuser.
At the prompt, type svcadm disable application/gdm2-login.
Log in again as superuser.
If you are using dtlogin, follow these steps:
In the dtlogin window, click Options and select Command Line Login.
Log in as superuser.
Create a new xorg.conf file.
# /usr/X11/bin/Xorg -configure
The command creates the file xorg.conf.new in the root (/) directory.
Copy the new configuration file to the /etc/x11 directory and rename the file xorg.conf.
# cp /xorg.conf.new /etc/X11/xorg.conf
Modify the configurations in the file:
In the ServerLayout section, add an input device for Mouse1 after the line InputDevice "Mouse0" "CorePointer". See the following example:
InputDevice "Mouse0" "CorePointer" InputDevice "Mouse1"
In the InputDevice section that contains the line Identifier "Mouse0", apply the following changes:
Change Option "Device" "/dev/mouse" to Option "Device" "/dev/kdmouse".
Change Option "Protocol" "auto" to Option "Protocol" "VUID".
Add the following new Option:
Option "StreamsModule" "vuid3ps2"
After you have applied the changes, the section should appear similar to the following example:
Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "VUID" Option "Device" "/dev/kdmouse" Option "StreamsModule" "vuid3ps2" EndSection
Create a new InputDevice section after the preceding InputDevice section:
Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Device" "/dev/usb/hid1"
EndSection
Note - /dev/usb/hid1 is an example path for the USB mouse. Use the path in Step 4 to replace /dev/usb/hid1.
Save the file and exit.
Reboot the system from the appropriate command-line session:
If you are using GDM, perform the following:
Type svcadm enable application/gdm2-login.
Reboot the system.
If you are using dtlogin, reboot the system.
Log in to the accessible UI user's account.
Enable Assistive Technology Support by clicking Launch Menu => Preferences => Accessibility => Assistive Technology Support.
Log out of the system then log in to the accessible UI user's account again.
Open a terminal window and type the following command:
% /usr/sfw/bin/gok --select-action=switch1
In the GOK window, click GOK and select Preferences.
If necessary, set up GOK to the accessible UI user's needs. Otherwise, to accept the current setup, click Apply then click OK in the GOK Preferences window.
Exit GOK and then restart it by clicking Launch Menu => Applications => Accessibility => On-Screen Keyboard. The following warning message might be displayed:
The device you are using to control GOK is also controlling the system pointer.
Click OK.
Exit GOK and then repeat steps 14-17.
The warning message is no longer displayed.
The following patches are applied to the Solaris OS to resolve StarOffice problems that were reported in CR 6234855 and CR 6262830:
For SPARC based systems
Patch ID 119412-06
Patch ID 119906-03
For x86 based systems:
Patch ID 119413-06
Patch ID 119907-03
To completely resolve the reported problems, perform the following steps after applying the patches. These steps enable you to use StarOffice 7 Product 5 software to open, for example, those OpenDocument files that were created in StarOffice 8 software.
Become superuser.
Issue the following command:
# update-mime-database /usr/share/mime
Log out of the system and then log in again.
Upgrading to the Solaris 10 1/06 software might hang if you are installing or upgrading from a DVD media. The problem affects certain Sun Blade 1500 workstations that are equipped with the JLMS DVD drive. The error occurs when you use any of the following installation methods:
Solaris interactive installation program
Solaris Live Upgrade
When the system hangs, no error messages are displayed.
Workaround: To upgrade such a system, use a network installation image.
On certain occasions, the utility for BIOS devices (/sbin/biosdev) might fail and prevent a successful installation or upgrade. The failure can occur under either of the following circumstances:
Patch ID 117435-02 was applied, but the system was not rebooted.
The system contains two or more identical disks that have identical fdisk partitions.
The following error message is displayed:
biosdev: Could not match any!!
Workaround: Make sure that you reboot the system after applying Patch ID 117435-02. Ensure that identical disks to be used in the installation or upgrade are configured with different fdisk-partition layouts.
The following example is based on a system that has two disks with identical fdisk-partition layouts. To change the layouts, perform the following steps.
Become superuser.
Start the disk maintenance utility.
# format
A list of available disks in the system is displayed.
To select the disk whose fdisk partition you want to change, type the disk's number.
From the list of Format options, select fdisk.
The disk's partition information and a list of fdisk options are displayed.
To change the disk's layout, choose one of the following:
To specify a different active partition, press 2.
To add another disk partition, press 1.
To delete an unused partition, press 3.
To save your changes and exit the fdisk menu, press 5.
To exit the disk maintenance utility, select Quit from the Format options.
Reboot the system.
After the system reboots, verify that the error message no longer appears. As superuser, type the following command:
# /sbin/biosdev
If the error message is still generated, repeat the procedure but select a different option in Step 5.
If the system contains other identical disks with identical fdisk-partition layouts, repeat Steps 1-9 on these disks. Otherwise, you can proceed with your Solaris installation or upgrade.
A locale problem occurs when you use the GUI-based installation program to upgrade a system that contains zones. After the installation, the LANG variable in the /etc/default/init file is set to null. If you issue any system command, the following error message is displayed:
couldn't set locale correctly
Workaround: As superuser, choose one of the following workarounds:
Workaround 1: If you have already upgraded the system, manually edit the /etc/default/init file to set the correct LANG and LC_* variables. Then reboot the system.
For more information and examples, see the locale(1) man page.
Workaround 2: Use the text-based installation program to upgrade the system. Perform either of the following steps that is appropriate to your system:
For SPARC systems, use the text flag with the boot command. For example, if you are using the CD media to install the software, issue the following command:
ok boot cdrom - text
For x86 systems, at the installation selection screen, select 3 Solaris Interactive Text (Desktop session).
For more information, see the Solaris 10 Installation Guides.
Postinstallation processes might encounter problems while the SUNWgnome-a11y-libs-share package is being added. The problems affect the following situations:
Using non-global zones and setting up a whole root zone
Using Solaris Live Upgrade to upgrade from the Solaris 8 or Solaris 9 release
Setting up a diskless client from the Solaris 10 1/06 release
If you are using non-global zones and have set up a whole root zone, the following error message is displayed:
# zoneadm -z wholerootzone install Installation of these packages generated warnings: <SUNWgnome-a11y-libs-share> The file </export/home/wholerootzone/root/var/sadm/system/logs/install_log> contains a log of the zone installation . #
The install_log reports the following error:
*** package <SUNWgnome-a11y-libs-share> installed with warnings: cp: cannot access ../../../../../share/jar/gnome-java-bridge.jar pkgadd: ERROR: postinstall script did not complete successfully Installation of <SUNWgnome-a11y-libs-share> on zone <wholerootzone> partially failed.
If you upgrade by using Solaris Live Upgrade from the Solaris 8 or Solaris 9 release, the upgrade_log reports the following error:
Doing pkgadd of SUNWgnome-a11y-libs-share to /. 15360 blocks /a/var/sadm/pkg/SUNWgnome-a11y-libs-share/install/postinstall: /sbin/zonename: not found Installation of <SUNWgnome-a11y-libs-share> was successful.
If you set up the diskless client service for the Solaris 10 1/06 release, the log file in /var/sadm/system/logs for your specific system reports the following error:
Doing pkgadd of SUNWgnome-a11y-libs-share to /export/Solaris_10. 15360 blocks /export/Solaris_10/var/sadm/pkg /SUNWgnome-a11y-libs-share/install/postinstall: /export/Solaris_10/usr/java/jre/lib: does not exist pkgadd: ERROR: postinstall script did not complete successfully Installation of <SUNWgnome-a11y-libs-share> failed. pkgadd return code = 1
Workaround: In all three situations, ignore the error messages.
Installation of the Solaris 10 OS might fail while you are adding Driver Updates (DU), which are also known as Install Time Updates (ITU). This error occurs if you are using the GUI to install the Solaris 10 software. The following message is displayed:
Unable to run cmd: /usr/sbin/sysidput
Workaround: Use either of the following workarounds.
Workaround 1: Configure the installation to use DHCP to gather network configuration information.
Workaround 2: Use a text-based installation method.
If you are performing the text-based installation in a desktop session, follow these steps.
After you have finished adding ITUs, type Ctrl-c instead of typing e.
Choose option 3.
If you specify a serial console to use during the installation, follow these steps.
After you have finished adding ITUs, type Ctrl-c instead of typing e.
Choose option 4.
The mkfs command might be unable to create a file system on disks with a certain disk geometry and whose sizes are greater than 8 Gbytes. The derived cylinder group size is too large for the 1-Kbyte fragment. The large size of the cylinder group means that the excess metadata cannot be accommodated in a block.
The following error message is displayed:
With 15625 sectors per cylinder, minimum cylinders per group is 16. This requires the fragment size to be changed from 1024 to 4096. Please re-run mkfs with corrected parameters.
Workaround: Use the newfs command instead. Or, assign a larger fragment size, such as 4096, when you use the mkfs command.
Problems might occur if you use the AT keyboard to start the following assistive technologies in the Sun Java Desktop System (Java DS). Default time settings might cause the use of key combinations to fail to start these technologies:
GNOME On-Screen Keyboard (GOK)
Magnifier
Speech
Workaround: Follow these steps to start these technologies by using the keyboard when you log in.
Open the /etc/X11/gdm/modules/AccessKeyMouseEvents file.
Navigate to the line that defines the default minimum and maximum time limits for keystrokes.
For example, for GOK, the line is the following:
Controlk 1 1000 10000 gok --login --access-method=directselection
Modify the line by performing the following:
Change the minimum and maximum time settings.
Ensure that you include the correct path for GOK, /usr/sfw/bin/gok.
After you have completed the changes, the sample line should appear as follows:
Controlk 1 10 100 /usr/sfw/bin/gok --login --access-method=directselection
The Generic LAN Driver Version 3 (GLDv3) incorrectly sets the field length of Logical Link Control (LLC) frames. Consequently, protocols such as AppleTalk that are dependent on LLC do not function correctly. No error message is displayed. The problem affects the following network interface controllers:
bge
e1000g
xge
Workaround: None.
When you use the Solaris interactive installation program, the Choose Terminal Type screen causes errors in the installation. The program immediately accepts the first character that you type and then proceeds with the installation. Consequently, you cannot choose an option that requires you to type more than one character. If you accidentally typed one character, which the installation program immediately accepts, the rest of the installation proceeds in error. No error message is displayed.
Workaround: Start the installation normally. At the screen that prompts you for the installation type, select the type before the timer expires in 30 seconds. Subsequent selection of the terminal type should work properly.
The function to add regions in the localeadm command no longer works if you create a new configuration file. The Language CD is not detected when you add the following regions:
Southern Europe
North America
Northern Europe
The following error message is displayed:
No langcd image has been found in /cdrom/sol_10_1005_x86_4/Solaris_10/Product No langcd image has been found in /cdrom/sol_10_1005_x86_4 /cdrom/sol_10_1005_x86_4 /cdrom/sol_10_1005_x86_4 /cdro m/sol_10_1005_x86_4 /cdrom/sol_10_1005_x86_4 Please enter the path to this image/disk, or enter 'q' to quit:
Workaround: When you are prompted to create a new configuration file, select No. Instead, use the configuration file that was installed in the system.
If you install the Solaris 10 1/06 software on systems with multiple CPUs, certain of those systems might hang. The error might occur in either of the following instances:
During installation while the message Configuring devices is displayed on the system console
During a system boot while Sun's copyright messages and the message Use is subject to license terms are displayed
Workaround: Perform the following steps from the GRand Unified Bootloader (GRUB) menu:
Type e to edit your selected Solaris entry.
Navigate to the line that begins with kernel.
Type e to switch to the GRUB edit mode.
Append -kd to the line.
Press Enter to accept the change.
Type b to boot with your selected Solaris entry.
At the kmdb prompt, type the following commands:
use_mp/W 0 :c
If you are performing a system boot, proceed to Step 10. Otherwise, install the Solaris 10 1/06 software.
At the end of the installation, reboot the system. If the system hangs again, repeat Steps 1-7.
When system boot is completed, become superuser.
Open the /etc/system file.
Add the following line:
set use_mp = 0
To accept the changes, reboot the system.
The dbx debugger terminates with a memory access failure while processing certain 64-bit executable files and libraries. However, the problem does not affect the normal use of these 64-bit objects. An error message similar to the following example is displayed:
dbx: internal error: signal SIGBUS (invalid address alignment)
Workaround: Use either the mdb debugger or the Solaris Dynamic Tracing facility instead. These alternatives can diagnose processes that use the 64-bit objects.
For keyboard input in Solaris software, the Bulgarian locale uses the Russian character map instead of the regular Bulgarian keyboard layout. Because the user cannot type Cyrillic characters by using the Bulgarian keyboard layout, the only alternative input method is to use the English character map.
Workaround: None.
Creating a UFS file system with the newfs command might fail under the following conditions:
The size of the slice is small, approximately less than 4 Mbytes.
The size of the disk exceeds 8 Gbytes.
The error is caused by the large-size requirement of the file system for metadata. The following warning message is displayed:
Warning: inode blocks/cyl group (295) >= data blocks (294) in last
cylinder group. This implies 4712 sector(s) cannot be allocated.
/dev/rdsk/c0t0d0s6: 0 sectors in 0 cylinders of 48 tracks, 128 sectors
0.0MB in 0 cyl groups (13 c/g, 39.00MB/g, 18624 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
#
Workaround: As superuser, perform one of the following workarounds:
Workaround 1: Specify the number of tracks when you use the newfs command. Follow these steps.
Use the format command to find out the number of tracks to assign. For example:
# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0t0d0 <SUN18G cyl 7506 alt 2 hd 19 sec 248>
/pci@1f,4000/scsi@3/sd@0,0
Specify disk (enter its number):
In the example, the number of tracks is 19.
Assign the number to the file system that you create with the newfs command. For example:
# newfs -v -t 19 /dev/dsk/c0t0d0s6
newfs: construct a new file system /dev/rdsk/c0t0d0s6: (y/n)? y
mkfs -F ufs /dev/rdsk/c0t0d0s6 4712 -1 19 8192 1024 16 10 167 2048
t 0 -1 8 128 n
mkfs: bad value for nsect: -1 must be between 1 and 32768
mkfs: nsect reset to default 32
Warning: 152 sector(s) in last cylinder unallocated
/dev/rdsk/c0t0d0s6: 4712 sectors in 8 cylinders of 19 tracks,
32 sectors
2.3MB in 1 cyl groups (16 c/g, 4.75MB/g, 2304 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32,
#Workaround 2: Specify the number of bytes per inode (nbpi) in the newfs command to reduce the inode density in the file system. For example:
# newfs -i 4096 /dev/dsk/c0t0d0s6
newfs: construct a new file system /dev/rdsk/c0t0d0s6: (y/n)? y
Warning: 1432 sector(s) in last cylinder unallocated
/dev/rdsk/c0t0d0s6: 4712 sectors in 1 cylinders of 48 tracks,
128 sectors
2.3MB in 1 cyl groups (16 c/g, 48.00MB/g, 11648 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32,
#An NFSv4 client whose file system is near full capacity mishandles error codes that are returned from the server. The client receives the correct (NFS4ERR_NOSPC) error code from the server. However, the client fails to transmit the (ENOSPC) error code to the application. The application does not receive the error notifications through the normal system functions such as write(), close(), or fsync(). Consequently, the application's continuous attempts to write or modify data can cause data loss or corruption.
The following error message is recorded in /var/adm/messages:
nfs: [ID 174370 kern.notice] NFS write error on host hostname : No space left on device. nfs: [ID 942943 kern.notice] File: userid=uid, groupid= gid nfs: [ID 983240 kern.notice] User: userid=uid, groupid= gid nfs: [ID 702911 kern.notice] (file handle: 86007000 2000000 a000000 6000000 32362e48 a000000 2000000 5c8fa257)
Workaround: Do not perform work on client systems whose file systems are near full capacity.
When you use Solaris Live Upgrade to create boot environments, one of the boot environments in the system hosts the GRand Unified Bootloader (GRUB) menu. This boot environment cannot be removed with the ludelete command.
If you attempt to remove the boot environment, the following error message is displayed:
ERROR: The boot environment name-of-boot-environment contains the GRUB menu. ERROR: You are not allowed to delete this BE. Unable to delete boot environment.
Workaround: Use either the lumake command or the luupgrade command to reuse this boot environment. Make the boot environment that contains the GRUB menu the last boot environment to be deleted.
Note - Solaris Live Upgrade does not allow the last boot environment to be deleted. Nor can the boot environment that contains the GRUB menu be deleted. Therefore, if the last boot environment also contains the GRUB menu, then you can delete all other boot environments if needed.
A problem occurs if you configure the Magnifier with two virtual or physical video devices in the following manner:
The Magnifier's source set is :0.1.
The Magnifier's target set is :0.0.
In this configuration, the key combination Ctrl-Esc cannot open the Launch menu on the magnified second desktop system.
Workaround: None.
An upgrade of a Solaris Live Upgrade boot environment fails when you are using CD or DVD media. The luupgrade command cannot find the installation media. Network installation images are unaffected by this problem.
The following error message is displayed:
ERROR: The media is not recognized installation media media_drive .
Workaround: Mount the media and begin your upgrade again. Perform the following steps:
Become superuser.
Stop the Volume Management daemon.
# pkill vold
Mount the CD or DVD manually.
Upgrade the boot environment again with the luupgrade command.
If you upgrade an x86 based system from Solaris 9 9/04 release to any release of the Solaris 10 software, the login program might not work. The problem occurs when you select any UTF-8 locale in the dtlogin GUI. When the error occurs, the GUI generates a core dump.
Workaround: Do not select any UTF-8 locale from the Language pull-down menu under Options.
In certain situations while you are unloading the e1000g Ethernet driver, some tx Direct Memory Access buffer handles (tx DMA) are not completely released. In such situations, the system panics. The following error message is displayed:
panic[cpu0]/thread=d63f4de0: assertion failed: !dma->dp_inuse, file: ../../i86pc/io/rootnex.c, line: 1903 d63f4b64 genunix:assfail+5c (feab4358, feab433c,) d63f4b8c rootnex:rootnex_dma_freehdl+8a (cefd7e48, cf287730,) d63f4bac genunix:ddi_dma_freehdl+1e (cf287730, cf287730,) d63f4bc8 genunix:ddi_dma_free_handle+16 (ca7e3000) d63f4be0 e1000g:e1000g_release_dma_resources+105 (c890d1c0) d63f4bf8 e1000g:e1000g_unattach+9d (cf287730, c890d1c0) d63f4c14 e1000g:e1000gdetach+56 (cf287730, 0) d63f4c54 genunix:devi_detach+86 (cf287730, 0) d63f4c74 genunix:detach_node+6d (cf287730, 2000) d63f4ca0 genunix:i_ndi_unconfig_node+10b (cf287730, 4, 2000) d63f4cd4 genunix:i_ddi_detachchild+36 (cf287730, 2000) d63f4d04 genunix:devi_detach_node+61 (cf287730, 2000) d63f4d3c genunix:unconfig_immediate_children+238 (cefd7728, 0, 2000, ) d63f4d74 genunix:devi_unconfig_common+f5 (cefd7728, 0, 2000, ) d63f4dc8 genunix:mt_config_thread+9b (d1a54008, 0) d63f4dd8 unix:thread_start+8 ()
Workaround: None.
If you install the Solaris 10 1/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.
If you use Solaris Live Upgrade to upgrade from the Solaris 8 2/02 release to the Solaris 10 1/06 release, the removal of the Agilent Fibre Channel HBA Driver Package (HPFC) fails. The following error message is recorded in the upgrade_log file.
Removing package HPFC: Modifying /a/kernel/drv/sd.conf cmdexec: ERROR: unable to open /a/var/sadm/pkg/HPFC/save/sed/kernel/drv/sd.conf pkgrm: ERROR: class action script did not complete successfully Removal of partially failed. pkgrm return code = 2 The upgrade succeeds, but two instances of the HPFC package are included on the system.
Workaround: Follow these steps.
Become superuser.
Remove both instances of the HPFC package.
# pkgrm HPFC # pkgrm HPFC.2
Insert the Solaris 10 1/06 OS DVD in the DVD-ROM drive.
Change directories to the directory that contains the HPFC package.
# cd /cdrom/Solaris_10/Product
Add the HPFC package to the system.
# pkgadd -d `pwd` HPFC
Software problems affect the use of extended devices such as a second mouse device or a USB head tracker with the GNOME On-Screen Keyboard (GOK). Consequently, the user preferences Dwell Selection and Direct Selection cannot be set by using GOK. Instead, you need to set these user preferences by using a physical keyboard and mouse device.
Workaround: After you have set the system to use an extended device, perform the following procedures in sequence.
First, set GOK to ensure that the core pointer is controlled by the primary mouse device. Other extended devices are then reserved for use by AT applications. Follow these steps when starting GOK for the first time:
Start GOK.
In the window where Sticky Keys have been activated, press Enter.
In the window that prompts you to use core pointer mode, use the arrow keys to highlight Cancel, then press Enter.
To set user preferences, click GOK and select Preferences.
Configure Dwell Selection or Direct Selection.
To configure Dwell Selection, follow these steps:
Click the Access Methods tab.
Choose Dwell Selection from the Method drop-down menu.
Click the Actions tab and perform the following:
Choose Dwell from the Name drop-down menu.
Check that Activate on Dwell is selected for Behavior.
Check that Other input device is selected for Event Source.
Click Apply.
In the Actions tab, perform the following:
Choose Mouse Pointer from the Name drop-down menu.
Check that Activate on Enter is selected for Behavior.
Click Apply, then click OK.
Exit the GOK window.
Log out and log in again.
To configure Direct Selection, follow these steps:
Click the Access Methods tab.
Choose Direct Selection from the Method drop-down menu.
From the Activate drop-down menu, choose Switch1 to use mouse button 1 on the second mouse.
Click Apply, then click OK.
Exit the GOK window.
Log out and log in again.
When you boot the system from the Solaris OS DVD to install the Solaris software, the following warning is displayed:
/sbin/install-discovery: /usr/bin/loadkeys: not found
Consequently, keyboard mappings for autodetected keyboards are not automatically loaded during the boot process.
Workaround: None. Ignore the warning message. You can continue to install the Solaris software on the system even without the keyboard mappings. After you have completed the installation, these mappings are automatically set when you reboot the system.
Sun Expert3D or Sun Elite3D cards in Sun Blade 1000 or Sun Blade 2000 workstations normally switch to low-power mode after an idle period. However, if these cards are set as the primary head in the Xserver, power management does not work. The affected cards remain at full power and no power savings are realized. No error message is displayed.
Workaround: None.
For keyboard input in the Solaris software, the Serbian locale uses the Russian character map instead of the regular Serbian keyboard layout. Because the user cannot type Cyrillic characters by using the Serbian keyboard layout, the only alternative input method is to use the English character map.
Workaround: None.
During dynamic reconfiguration (DR), error messages might be displayed. The messages are displayed if you perform DR while input and output operations are active on devices that are in the DR path. After the messages are displayed, the input and output operations are retried and eventually succeed. The following is a sample that is displayed:
Jul 28 12:23:19 qame10-a scsi: [ID 107833 kern.warning] WARNING: /ssm@0,0/pci@19,700000/SUNW,qlc@2,1/fp@0,0/ssd@w2100000c5056fa13,0 (ssd6): Jul 28 12:23:19 qame10-a transport rejected fatal error Jul 28 12:22:08 qame10-a scsi: [ID 107833 kern.warning] WARNING: /ssm@0,0/pci@19,700000/SUNW,qlc@2,1/fp@0,0/ssd@w2100000c5056f9a7,0 (ssd36): Jul 28 12:22:08 qame10-a SCSI transport failed: reason 'timeout': retrying command
Workaround: None. Ignore the error messages.
The SUNWceuow package might not be properly upgraded under the following circumstances:
In your system that is running the Solaris 10 OS, the SUNWceuow package is installed.
You upgrade the system to the Solaris 10 1/06 release.
This error occurs regardless of the upgrade method that you use.
The following report is contained in the /var/sadm/system/logs after you have finished upgrading:
# grep SUNWceuow up*log Doing pkgadd of SUNWceuow to /. Installation of <SUNWceuow> was successful.
However, if you check the accuracy of the installation of SUNWceuow by using the pkgchk command, the following error message is displayed.
# pkgchk SUNWceuow ERROR: /usr/openwin/lib/locale/cs_CZ.UTF-8/app-defaults/XTerm pathname does not exist
Workaround: After the OS has been upgraded, remove the SUNWceuow package, and then reinstall the package.
# pkgrm SUNWceuow # pkgadd SUNWceuow
The command luxadm -e forcelip to reinitialize a link on one server causes the logical unit number (LUN) to reset on all servers in the Storage Area Network (SAN). The following sample error message is displayed on the console of one or more servers in a zone within the same SAN environment.
Aug 16 13:34:07 ontario-a last message repeated 5 times Aug 16 13:34:07 ontario-a scsi_vhci: [ID 734749 kern.warning] WARNING: vhci_scsi_reset 0x0
Workaround: None. Ignore the error messages.
GNOME applications do not start if you log in remotely and enable accessibility in gnome-at-properties. If you attempt to start a GNOME application, the following error message is displayed:
** ERROR **: Accessibility app error: exception during registry activation from id: IDL:Bonobo/GeneralError:1.0 aborting...
Workaround: None. Do not enable accessibility when you log in by using dtremote.
To revert to the default desktop settings in which accessibility is disabled, close the GNOME session. Issue the following command:
% gnome-cleanup
On your Java Desktop System software, you cannot set up the following:
Full-screen magnification
Keyboard accessibility features
Workaround: Perform the following steps:
Open the /etc/X11/gdm/gdm.conf file.
Depending on your system's platform, perform the following:
On SPARC based systems:
Look for the line in the file that begins as follows:
command=/usr/openwin/bin/Xsun
Append the following modification to the line:
+kb +accessx -dev framebuffer1 -dev framebuffer2
For example:
+kb +accessx -dev /dev/fbs/pfb1 -dev /dev/fbs/pfb0
On x86 based systems:
Look for the line in the file that begins as follows:
command=/usr/X11R6/bin/Xorg
Append the following modification to the line:
+kb +accessx
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 1/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.
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.
The patchadd and patchrm commands work improperly in non-global zones with inherited file systems. Consequently, in those zones, the pkgchk command might generate error messages about packages under the following circumstances:
In the global zone, you apply patches for the Solaris 10 zone system by using the patchadd command.
You use the patchrm command to remove patches that you just recently applied.
In a non-global zone with inherited file systems, you check with the pkgchk command for information about a package in any of the removed patches.
The following sample message is displayed when the pkgchk command is used on SUNWcsu under the circumstances previously listed.
# pkgchk SUNWcsu
ERROR: /usr/lib/inet/certdb
modtime <04/26/05 10:55:26 PM> expected <01/23/05 01:48:24 AM> actual
file size <36012> expected <42152> actual
file cksum <37098> expected <19747> actual
ERROR: /usr/lib/inet/certlocal
modtime <04/26/05 10:55:26 PM> expected <01/23/05 01:48:24 AM> actual
file size <44348> expected <84636> actual
Workaround: None. The errors are harmless. Ignore the error messages.
In the Solaris software, you restrict application launching by setting to true the /desktop/gnome/lockdown/restrict_application_launching gonf key. This setting allows only certain applications to appear on the Launch menu where you can start these applications. The allowed applications are listed in the /desktop/gnome/lockdown/allowed_applications gonf key.
Currently, the list includes applications that are outdated and are no longer included in the Java Desktop System software. Moreover, the list also contains references to certain applications with incorrect directory locations. Consequently, if you restrict application launching, certain key applications such as Mozilla or StarOffice do not appear on the Launch menu.
Workaround: Perform the following steps.
Become superuser.
Remove the ~/.gconf/desktop/gnome/lockdown directory if the directory exists.
# rm -rf ~/.gconf/desktop/gnome/lockdown
Log out of the system and then log in again.
A problem occurs when you upgrade to the Solaris 10 1/06 software a system whose root (/) file system is a RAID-1 volume. This problem occurs when you perform the upgrade as follows:
You use CD media or an network installation image.
You use the Solaris interactive installation program or custom JumpStart.
One of the following problems occurs:
If you are using the Solaris interactive program, you are not given the option of upgrading in the panel Select upgrade or initial install.
If you use custom JumpStart to upgrade, the following error message is displayed:
ERROR: No upgradeable root file systems were found.
Workaround: Perform Workaround 1 first. Proceed to Workaround 2 only if the first workaround did not resolve the issue.
Workaround 1:: Remove the RAID configurations before performing the upgrade. Rebuild your RAID configuration after the upgrade is completed. To remove the RAID configurations, follow these steps.
Find the physical devices that are being used for the root partition's RAID-0 volumes or submirrors, as in the following example:
# df -k / Filesystem kbytes used avail capacity Mounted on /dev/md/dsk/d0 4459950 3089180 1326171 70% / # metastat -p d0 d0 -m d10 d11 1 d10 1 1 c1t0d0s0 d11 1 1 c1t1d0s0
Remove the mirror that is not being upgraded. In the example, if the disk to be upgraded is c1t0d0s0, you need to remove d11. Type the following:
# metadetach d0 d11
Revert to using the appropriate physical device to be upgraded. For the previous example, you issue the following command.
# metaroot c1t0d0s0
If necessary, verify that the /etc/vfstab has been updated with the required device.
# grep c1t0d0s0 /etc/vfstab /dev/dsk/c1t0d0s0 /dev/rdsk/c1t0d0s0 / ufs 1 no -
Shut down the system.
Boot the system from the DVD or CD media.
In the panel Select upgrade or initial install, you can now choose to upgrade. You can also select the device to upgrade from the list of devices in the panel. Typically, the list contains the devices that comprise the original root subvolume.
However, if the option to upgrade remains unavailable, then skip to the alternative workaround.
To proceed with the upgrade, select the device.
To rebuild your RAID configurations after the upgrade has been completed, follow these steps.
Redefine the boot device.
# metaroot d0
Reboot the system.
Add the subvolume.
# metattach d0 d11
Workaround 2: Use this workaround only if Workaround 1 was not successful. Do not perform this workaround without attempting the previous workaround first.
Reboot the system.
The system boots back to the existing Solaris release.
Delete the active metadevices that comprise the root partition by using the metaclear command.
# metaclear d0 d10 d11
Shut down the system.
Boot the system from the DVD or CD media.
Proceed with the installation by following the installation or upgrade options that appear on the screen.
After the upgrade is completed, reconfigure your metadevices by following the normal procedures.
The following example shows the steps to configure the root (/) metadevice, set up the system files for the metadevice, and reattach the subvolume.
# metainit d0 -m d10 # metaroot d0 # reboot # metainit d11 1 1 c1t1d0s0 # metattach d0 d11
Note - You reattach the old subvolume after the system boot is completed.
Starting with the current Solaris release, a Solaris Flash archive cannot be properly created when a non-global zone is installed. The Solaris Flash feature is not currently compatible with the Solaris containers (zones) feature.
Do not use the flar create command to create a Solaris Flash archive in these instances:
In any non-global zone
In the global zone if there are any non-global zones installed
If you create a Solaris Flash archive in such an instance, the resulting archive might not install properly when the archive is deployed.
Workaround: None.
The upgrade progress bar does not appear when you use the Solaris Live Upgrade software in the following manner:
You use the Solaris 10 1/06 CD media to upgrade the OS.
You upgrade a boot environment by using the luupgrade command with the following options:
-i to install from the CD media
-O “-nodisplay -noconsole” to run the installer on the second CD in text mode and without user interaction
You are upgrading to the Solaris 10 1/06 software from the following releases:
Solaris 8 release
Solaris 9 release
Solaris 10 release
For example, if you run the following command, the progress bar should be displayed after you see the following output:
Running installer on BE s10u1.
However, the bar fails to appear.
# luupgrade -i -n s10u1 -s /net/installsrv/export/s10u1 -O "-nodisplay -noconsole" Validating the contents of the media /net/installsvr/export/s10u1. The media is a standard Solaris media. The media contains a standard Solaris installer. The media contains Solaris 3 version 10. Mounting BE s10u1. Running installer on BE s10u1.
No error message is displayed.
Workaround: Use the prstat command. This command enables you to watch the progress while packages are being added during the installation.
If you use the Sound Recorder multimedia application in CD Quality, Lossless mode, the application fails when recording starts. The following error message is displayed:
The Application "gnome-sound-recorder" has quit unexpectedly.
Workaround: Perform the following steps.
Become superuser.
Issue the following command:
# GCONF_CONFIG_SOURCE=xml::/etc/gconf/gconf.xml.defaults /usr/bin/gconftool-2 --makefile-install-rule /etc/gconf/schemas/gnome-audio-profiles.schemas
In addition, existing users must perform the following steps.
If the gnome-audio-profiles-properties application is running, stop the application by closing the application window.
If the profile cdlossless exists in ~/.gconf/system/gstreamer/audio/profiles, remove the profile.
% rm ~/.gconf/system/gstreamer/audio/profiles/cdlossless
Log out of the system and then log in again.
A problem occurs if you configure the Magnifier with two virtual or physical video devices in the following manner:
The Magnifier's source set is :0.1.
The Magnifier's target set is :0.0.
In this configuration, no icons appear on the screen of the second desktop system.
Workaround: None.
Internet SCSI (iSCSI) targets might report cyclic redundancy check (CRC) errors if DataDigests are enabled. User applications that update input/output buffers after transmitting to the iSCSI initiator might cause a miscalculation of the CRC. When the target responds with a CRC error, the iSCSI Initiator retransmits the data with the correct DataDigest CRC. Data integrity is maintained. However, data transfer performance is affected. No error message is displayed.
Workaround: Do not use the DataDigest option.
When a fabric zone in a storage area network (SAN) is created dynamically, that zone's devices might be unavailable at the host side. If you use the command luxadm -e dump_map to display data for such devices or host bus adapters, an error message is displayed. See the following example:
# luxadm -e dump_map /dev/cfg/c5 Pos Port_ID Hard_Addr Port WWN Node WWN Type ERROR: Unable to retrieve target port details (QLogic Corp-2312-3)ERROR
Listing the status of all the attachment points yields information similar to the following example. In this example, the fabric devices include a tape drive, but no device is indicated in c5.
# cfgadm -al Ap_Id Type Receptacle Occupant Condition : : c5 fc-fabric connected unconfigured unknown usb0/1 unknown empty unconfigured ok : :
Workaround: After configuring the fabric-connected devices, reinitialize the link to the devices by using the luxadm -e forcelip command. For the previous example, you would type the following:
# luxadm -e forcelip /dev/cfg/c5
|