Troubleshooting with RAID Manager

To identify the cause of errors that occur when you run RAID Manager commands, refer to the log displayed in the RAID Manager window or the RAID Manager operation log file.

1. Find the error code in the log displayed in the RAID Manager window or the RAID Manager operation log file. The RAID Manager log file’s default location is /HORCM/log*/curlog/horcmlog_HOST/horcm.log, where the asterisk (*) is the instance number and HOST is the host name.

   The following figure shows an example of a log displayed in the RAID Manager window.

   An error code string in the RAID Manager operation log file looks like the following example:

   11:06:03-37897-10413- SSB = 0xB901,4A96

2. Locate the SSB1 and SSB2 codes. In the examples above, the error codes appear to the right of "SSB =".

   • The last four digits to the left of the comma (,) are the SSB1 code (B9E1).
   • The last four digits to the right of the comma (,) are the SSB2 code (B901).

3. Locate the description of the SSB1/SSB2 error code combination in the table in RAID Manager SSB2 codes. For error codes not described in this table, call the Hitachi Solution Support Center.

Parent Topic

• RAID Manager command reference for Thin Image

Child Topics

• RAID Manager SSB2 codes

  This table lists the SSB2 codes when SSB1 is 2E31, B901, B9A8, B9A9, B9AD, or B9AE, the related RAID Manager command, and the cause of the error.

• Notes on using Thin Image primary volumes as TrueCopy, ShadowImage, or Universal Replicator pair volumes

  The raidcom modify snapshot -snapshot_data create or raidcom modify snapshot -snapshot_data clone RAID Manager command might return the error code EX_EWSTOT (timeout) and terminate abnormally when the status of a pair in a Thin Image consistency group cannot be changed.