Sun StorageTek RAID Manager: How to Map Bad Block Errors to Physical Disks

Asset ID:	1-71-1932938.1
Update Date:	2018-02-01
Keywords:

Solution Type Technical Instruction Sure

Solution 1932938.1 : Sun StorageTek RAID Manager: How to Map Bad Block Errors to Physical Disks

Applies to:

Sun Storage J4400 Array - Version All Versions and later
Sun Storage J4500 Array - Version All Versions and later
Sun Storage 3Gb SAS RAID HBA, External - Version Not Applicable and later
Sun Storage J4200 Array - Version All Versions and later
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on SPARC (64-bit)

Goal

Sun StorageTek RAID Manager logs bad block errors to /var/adm/messages, but the physical disk is not identified. This article shows how to map bad block errors from Sun StorageTek RAID Manager to the correct physical drive. For example:

Sep 8 08:15:30 myhost Sun StorageTek RAID Manager Agent: [ID 298876 daemon.warning] [418] Bad Block discovered: controller 1 (22ecb20a).
Sep 8 08:28:07 myhost Sun StorageTek RAID Manager Agent: [ID 298876 daemon.warning] [418] Bad Block discovered: controller 1 (22ecb20a).
Sep 8 12:11:32 myhost Sun StorageTek RAID Manager Agent: [ID 298876 daemon.warning] [418] Bad Block discovered: controller 1 (22ecb20a).

Solution

Sun StorageTek RAID Manager generates log files automatically to assist in tracking system activity. The log files are created in the directory where Sun StorageTek RAID Manager is installed, usually in /opt/StorMan for Solaris.

To match the bad block error with the disk having the problem, check the RaidEvtA.log file or the RaidEvt.log file to determine the appropriate disk.

RaidEvtA.log contains the information reported in the Sun StorageTek RAID Manager event viewer for the local system.
RaidEvt.log contains the information reported in the Sun StorageTek RAID Manager event viewer for all local and remote systems.

Both files are included within the support archive. To collect a support archive using the Storman GUI:

Log in to the StorMan GUI,
Right click on the machine name in the left panel.
Select "Save Support Archive".

The result will be a support.zip file saved to the RAIDmanager machine.

Also, depending on the Explorer version, the support archive files may be collected by Oracle Explorer. Look for a directory named RAIDManager or prometheus in the top level of the Explorer data. Newer versions of Explorer can collect this data using the option explorer -w prometheus.

The RaidEvtA.log file shows the disk that was reporting the bad block. In this example, it indicates disk slot 1 on a Sun Storage J4200 connected to the external Sun Storage 3Gb SAS RAID HBA, here listed as controller 1.

September 8, 2014 8:15:30 AM EDT        WRN      418:A01C-S--L--        myhost   Bad Block discovered: controller 1 (22ecb20a).
September 8, 2014 8:15:29 AM EDT        ERR      401:A01C0S01L--        myhost   Failed drive: controller 1, enclosure 0, slot 1, S/N 0802T2Q91M        3LM2Q91M (Vendor: SEAGATE Model: ST330055SSUN300G).
September 8, 2014 8:15:30 AM EDT        ERR      303:A01C-S--L00        myhost   Logical device failed: controller 1, logical device 0 ("MirrorA").

Do you still have questions? You can use My Oracle Support Communities. Communities put you in touch with industry professionals like yourself. They are monitored by Oracle support engineers, so you can expect reliable and correct answers. Ask questions and see what others are asking about in the Disk Storage 2000, 3000, 6000 RAID Arrays & JBODs Community.

Attachments

This solution has no attachment