Skip Navigation Links
Exit Print View
| SPARC T4-4 Server ### Product Notes

Search Scope:

- This Document
- Entire Library

## Firmware Issues

This section describes issues related to system firmware.

### `create-raid10-volume` Command Fails to Create a RAID 10 Volume on a Sun Storage 6 Gb SAS PCIe HBA (Bug ID 15635981)

Note - This issue was originally listed as CR 6943131.

Note - This issue is fixed in LSI Firmware 1.0.55.

The Sun Storage 6 Gb SAS PCIe HBA supports RAID types 0, 1, and 10. However, the Oracle OpenBoot `create-raid10-volume` command fails when attempting to create a RAID 10 volume. There is no Oracle OpenBoot command that allows you to create a RAID 10 volume.

Workaround:A RAID 1E volume is an enhanced RAID 1 volume that includes mirroring and striping.

Use the Oracle OpenBoot `create-raid1e-volume` command to create a RAID 1E volume.

### Timestamp for an ILOM Fault/Critical Event Might Be Off by One Hour (Bug ID 15802097)

Note - This issue was originally listed as CR 6943957.

Note - This issue is fixed in System Firmware 8.3.0.

The timestamp reported in an email generated in an Oracle ILOM Fault/critical event might be one hour later than the timestamp recorded in the event log.

Recovery Action: Check the timestamp recorded in the event log. If the timestamp does not match the timestamp reported in the email, use the event log time.

### Missing Interrupt Causes USB Hub Hot-plug Thread to Hang, Resulting In Process Hangs (Bug ID 15655752)

Note - This issue was originally listed as CR 6968801.

When running Oracle VTS on T4 series platforms, it is possible (although rare) for a Oracle VTS test to hang. If this happens, it might cause other processes and commands to hang, including `fmadm` and `prtconf`. The hung processes cannot be killed.

Workaround: Reboot the server. If the problem repeats, contact your authorized service provider. Avoid running Oracle VTS in production environments.

### Message From `cpustat` Refers to Processor Documentation Incorrectly (Bug ID 15717099, Bug ID 15717100, Bug ID 15749141)

Note - This issue was originally listed as CR 7046898.

Note - This issue is fixed in Oracle Solaris 11.

A message displayed by the `cpustat` command says:

    See the “SPARC T4 User's Manual” for descriptions of these events.
    Documentation for Sun processors can be found at:
    http://www.sun.com/processors/manuals

This document and web site listed in this message do not exist.

### `reboot disk` Command Occasionally Fails When `disk` Argument Picks Up Extra Characters (Bug ID 15816272, Bug ID 15719738)

Note - This issue was originally listed as CR 7050975.

Note - This issue is fixed in Oracle Solaris 11.1

When running the `reboot` disk command, extraneous characters are occasionally added to the disk argument before it reaches the OpenBoot PROM (OBP). These extra character result in a failure to boot.

Recovery Action: Repeat the boot request.

### Blue LED On Drive Does Not Light When the Drive Is Ready to Remove (Bug ID 15737491)

Note - This issue was originally listed as CR 7082700.

When you attempt to unconfigure a drive for removal, the drive's blue LED that indicates the drive is ready for removal might not light. This happens after you place a drive in a slot in place of a drive that had a different WWID.

Workaround: If you inserted a drive after booting the server, realize that the blue LED will not perform this function until the server has booted again.

### Cold Reset Adds One Day to System Time (CR 15764743, Bug ID 15765255, Bug ID 15765770)

Note - This issue was originally listed as CR 7127740.

Note - This issue is fixed in System Firmware version 8.2.0.a.

After a cold reset, the server might add one day to the Oracle Solaris OS date andtime. This possible date change will only occur on the first cold reset after the first day of a leap year (for example, January 1, 2012). Once you set the correct date using the Oracle Solaris OS `date`(1) command, the corrected date and time will persist across future resets.

Note - This extra day error condition returns if the clock offset stored in the SP is cleared for any reason. For example, the clock offset is lost if you replace the battery, if you reset Oracle ILOM, or if you perform a system firmware update without saving and then restoring the system configuration data.

A cold reset occurs when you halt the OS and restart the service processor (SP). For example, you can use one of the following Oracle Solaris OS commands to halt the OS:

    # shutdown -g0 -i0 -y

    # uadmin 1 6

    # init 5

    # poweroff

Then, at the ILOM prompt, use the following commands to reset the host:

    -> stop /SYS
    . . .
    -> start /SYS

Refer to the service manual, the administration guide, and the Oracle Solaris OS documentation for more information.

Workaround: After the first cold reset of the system, verify that the system date and time are correct. If the date has been impacted by this issue, use the Oracle Solaris OS `date`(1) command to set the correct date and time.

For example, to set the date and time to be February 26, 9:00am, 2012, type:

    # date 022609002012

Refer to the `date`(1) man page and the Oracle Solaris OS documentation for more information.

Copyright © 2011, 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices |