Solaris 10 7/07 HW Release Notes

Installation Bugs

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

Symbolic Links to etc/default/kbd and etc/default/nfs Files are Missing (6547635)

The Linux Partition Does Not Display on the GRUB Menu After Installing the Solaris OS (6508647)

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:

  1. Boot the Solaris OS.

  2. Edit the menu.lst file at /boot/grub/menu.lst. For more information, see the System Administration Guide: Basic Administration.

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

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:

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.

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


Note –

This problem might also occur during a Solaris installation of other software products that are included in this Solaris OS release.


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.

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.