Sun Server X4-8
 
Sun Server X4-2L
 
Sun Blade X3-2B
 
Sun Fire X4170 M2 Server
 
Sun Server X4-4
 
Sun Blade X6270 M2 Server Module
 
Oracle Server X5-2
 
Sun Fire X4800 Server
 
Sun Server X2-8
 
Netra Server X3-2
 
Netra Blade X3-2B
 
Sun Netra X6270 M2 Server Module
 
Sun Blade X4-2B Server Module
 
Sun Fire X4270 M2 Server
 
Sun Server X4-2
 
Netra Server X5-2
 
Sun Fire X4470 Server
 
Sun Server X3-2
 
Sun Netra X4270 Server
 
Sun Netra X4250 Server
 
Sun Server X2-4
 
Sun Server X3-2L
 
Sun Fire X4275 Server
 
Oracle Server X5-2L
 

PLA-Support>Sun Systems>x86>Server>SN-x64: MISC-SERVER
 

In this Document

Symptoms

Cause

Solution

References

Applies to:

Symptoms

Unrecoverable read errors that follow idle conditions with a burst of I/O activity may occur on certain disk drives.

Cause

This error condition occurs on certain 300GB, 600GB, 900GB, 1.2TB model disk drives in a variety of Oracle products.  The following X86 System models contain disk drives that may be affected:

Sun Fire X4275
Sun Fire X4170 M2
Sun Fire X4270 M2
Sun Fire X4470
Sun Fire X4800
Sun Server X2-4 / Sun Fire X4470 M2
Sun Server X2-8 / Sun Fire X4800 M2
Sun Server X3-2 / Sun Fire X4170 M3
Sun Server X3-2L / Sun Fire X4270 M3
Sun Server X4-2
Sun Server X4-2L
Sun Server X4-4
Sun Server X4-8
Oracle Server X5-2
Oracle Server X5-2L

Netra X4250
Netra X4270
Sun Netra X6270 M2 Server Module
Netra Server X3-2 / Sun Netra X4270 M3 Server
Netra Blade X3-2B / Sun Netra X6270 M3
Netra Server X5-2

Sun Blade X6270 M2 Server Module
Sun Blade X3-2B / Sun Blade X6270 M3 Server Module
Sun Blade X4-2B Server Module

How to Identify the Disk Model installed:

To determine whether or not your system has disks affected by this issue, use one of the following methods to identify what model and firmware version each disk in your system is:

A. For systems that are able to power down and visually inspect, the disk model and original firmware version appears on the label on the top of the disk.

B. For systems with Oracle Hardware Management Pack (HMP) installed:

For a list of systems and operating systems supported by HMP, review the support matrix at http://oracle.com/goto/ohmp.

As privileged user, run the "fwupdate list disk" command:

C. For systems with Oracle System Assistant (OSA) installed:

OSA is a graphical setup tool embedded on an optional USB drive in the internal USB slot on some X86 server models, and accessed by selecting OSA as the boot device and booting into the tool.

Navigate in the OSA user interface to “System Information” and then click on the “System Inventory” tab to the latest release which includes the updated firmware (The firmware release versions for the disk drives can be checked in the update's README provided). If the OSA is updated it will need a reboot to take effect.

Navigate to the “Update firmware” option and then select “Check for Firmware Updates” in the main window. After all the devices are probed select “View Details”. A list of components that OSA can update are listed and if there is a newer firmware version available you will be able to select the device by selecting the checkbox on the left side of the list.

D. For systems running Solaris x86 with a non-RAID HBA:

Review the “Product” and “Revision” field for each disk listed.

E. For systems running Linux with a non-RAID HBA:

Use one of the following methods:

A. With 'lsscsi' command which is part of the 'lsscsi' package:

B. With 'smartctl' command which is part of the 'smartmontools' package:

Repeat the "smartctl -i" inquiry for each SCSI "/dev/sd#" listed in the scan output.

Note - smartctl output can vary based on Linux version if the above does not provide the model and firmware information try using: "smartctl -i /dev/sda | grep -E 'Model|Firmware' "

C. If neither 'lsscsi' or 'smartctl' are available, and their packages cannot be installed, then the following will give the list of devices that were present at boot time:

Note however, this will not show any disks that may have been replaced via hot-plug since the last boot. If you know of disks replaced recently, their information may be available in the syslog messages which can be used to compare to the 'dmesg' output gathered previously:

 If log rotation is in use and there are no indications in '/var/log/messages' then repeat with '/var/log/messages.*'.

F. For systems running with a RAID HBA:

Note: For systems with 12Gb Aspen HBA(7085211) use the syntax below, where the command is "storcli" or “storcli64” in place of "MegaCli64".

a) Install the MegaRAID software for Linux or Solaris or Windows from http://www.avagotech.com/support/oem/oracle.

b) The software will install under /opt/MegaRAID directory on Linux and Solaris.
Note: The exact path to the command under this directory may differ for Linux or Solaris or Windows, and MegaCli or storcli.

c) Find out the “Inquiry Data” and current “Device Firmware Level” for your drive by using this command:

You will get output for each physical drive attached to the RAID HBA.  Look for the "Device Firmware Level" and "Inquiry Data" lines.

Affected Disk Models Per Server Type:

After identifying the model and firmware version of the disks in your system, compare that to the following list of affected disk models for your server type. Servers that shipped the same affected disk models are listed on the same table.

Sun Fire X4275:

Sun Fire X4170 M2, Sun Fire X4470, Sun Blade X6270 M2 Server Module and Sun Netra X6270 M2 Server Module:

Sun Fire X4270 M2:

Sun Fire X4800:

Sun Server X2-4 (formerly Sun Fire X4470 M2), and Sun Blade X3-2B (formerly Sun Blade X6270 M3 Server Module):

Sun Server X2-8 (formerly Sun Fire X4800 M2):

Sun Server X3-2 (formerly Sun Fire X4170 M3), and Sun Server X3-2L (formerly Sun Fire X4270 M3):

Sun Server X4-2, Sun Server X4-2L, and Sun Blade X4-2B Server Module:

Sun Server X4-4:

Sun Server X4-8:

Oracle Server X5-2, Oracle Server X5-2L, and Netra Server X5-2:

Netra X4250:

Netra X4270:

Netra Server X3-2 (formerly Sun Netra X4270 M3 Server), and Netra Blade X3-2B (formerly Sun Netra X6270 M3):

Solution

A firmware update is required to mitigate the effect of the symptoms described above. Implement the new disk firmware as it improves the reliability of the drives.

A maintenance window should be planned as disk firmware upgrades require the system be idle.

For the following platforms, the firmware update is provided via a patch:

Sun Fire X4275
Sun Fire X4170 M2
Sun Fire X4270 M2
Sun Fire X4470
Sun Fire X4800
Sun Server X2-4 / Sun Fire X4470 M2
Sun Server X2-8 / Sun Fire X4800 M2

Netra X4250
Netra X4270
Sun Netra X6270 M2 Server Module

Sun Blade X6270 M2 Server Module

Refer to the individual patch README's for the firmware installation procedure.

To obtain the A4C0 firmware please see patch 149675-06.
To obtain the A720 firmware please see patch 150940-04.
To obtain the A820 (300GB) or A880 (600GB) firmware please see patch 148959-08.

For the following platforms, the firmware update provided can be installed using one of three methods as detailed below:

Sun Server X3-2 / Sun Fire X4170 M3
Sun Server X3-2L / Sun Fire X4270 M3
Sun Server X4-2
Sun Server X4-2L
Sun Server X4-4
Sun Server X4-8
Oracle Server X5-2
Oracle Server X5-2L

Netra Server X3-2 / Sun Netra X4270 M3 Server
Netra Blade X3-2B / Sun Netra X6270 M3
Netra Server X5-2

Sun Blade X3-2B / Sun Blade X6270 M3 Server Module
Sun Blade X4-2B Server Module

A. Oracle Hardware Management Pack (HMP) method:

1) Download and unzip the FIRMWARE or ALL pack from My Oracle Support "Patches & Updates" section, searching for your platform type and SW release version number.

The following minimum versions of platform software releases (PSR) contain the disk firmware to address this issue:

Sun Server X3-2 / Sun Fire X4170 M3 – SW1.4.4
Sun Server X3-2L / Sun Fire X4270 M3 – SW1.4.4
Sun Server X4-2 –  SW1.3.2
Sun Server X4-2L – SW1.3.2
Sun Server X4-4 – SW1.2.0
Sun Server X4-8 – SW1.2.0
Oracle Server X5-2 – SW1.3.0
Oracle Server X5-2L – SW1.3.0

Netra Server X3-2 / Sun Netra X4270 M3 Server – SW1.2.1
Netra Blade X3-2B / Sun Netra X6270 M3 – Pending Availability
Netra Server X5-2 – SW1.0.1

Sun Blade X3-2B / Sun Blade X6270 M3 – SW1.3.2
Sun Blade X4-2B – SW1.2.1

2) As 'root' user, use the following command to check the current disk model and firmware: 

3) As 'root' user, use the following command to update the disk firmware:

where filename.xml specifies the update available to HMP and is part of the firmware pack.

For Example:
Oracle Server X5-2L with 1.2TB 10K RPM Disk (7045850 H101212SESUN1.2T), the following will update all disks of this model to A720 as contained in the X5-2L Platform Software Release v1.3.0:

B. Oracle System Assistant (OSA) method:

OSA is a graphical setup tool embedded on an optional USB drive in the internal USB slot on some X86 server models, and accessed by selecting OSA as the boot device and booting into the tool.

Navigate in the OSA user interface to “Get Updates” and then “Update firmware”. The OSA updates to the latest platform software releases (PSR). The following minimum PSR updates are available that contain the disk firmware to address this issue:

Sun Server X3-2 / Sun Fire X4170 M3 – SW1.4.4
Sun Server X3-2L / Sun Fire X4270 M3 – SW1.4.4
Sun Server X4-2 –  SW1.3.2
Sun Server X4-2L – SW1.3.2
Sun Server X4-4 – SW1.2.0
Sun Server X4-8 – SW1.2.0
Oracle Server X5-2 – SW1.3.0
Oracle Server X5-2L – SW1.3.0

Netra Server X3-2 / Sun Netra X4270 M3 Server – SW1.2.1
Netra Blade X3-2B / Sun Netra X6270 M3 – Pending Availability
Netra Server X5-2 – SW1.0.1

Sun Blade X3-2B / Sun Blade X6270 M3 Server Module – SW1.3.2
Sun Blade X4-2B Server Module – SW1.2.1

C. Direct disk patch method:

HMP or OSA are the preferred methods for disk firmware update, however the patches can be applied manually if necessary.  Refer to the individual patch README's for the firmware installation procedure.

To obtain the A4C0 firmware please see patch 149675-06.
To obtain the A720 firmware please see patch 150940-04.
To obtain the A880 firmware please see patch 148959-08.

For platforms where the Platform Software Release version for HMP and OSA methods is pending availability, use the individual patch README's for the firmware installation procedure.

References

This solution has no attachment