Windows Knowledge Base

[Clariion]Clariion SP Error Code Explained - Part One- Informational codes

The following lists the status codes that return in the Event Code field within an Unsolicited Sense Data block. The  describe events on a CRU basis, and they fall within 3 categories:

- Informational codes    (0x6##) - Require no operator action. They are valuable to support engineering in  helping to establish history.
- Soft codes (also knows as Thresholded codes    (0x8##)) -Are    normal and require no human action unless they  occur frequently.
- Error codes    (0x9##) - Typically require action by a support engineer.

INFORMATIONAL CODES

0x601, SP Powerup:
The SP is powered up and ready for IO.This field also shows the revision of microcode (Licensed  Internal Code) and the amount of SP memory in Mbytes, in hex.  For example, (SP Powerup, Rev  0x0080A01 0x00000020) means code revision 8.10.01 and 32    Mbytes of memory.

0x602, CRU Enabled:
The unit which    this drive is a member of, is ready for normal host I/O.

0x603, CRU Rebuild Started:
The background  rebuild    process    has begun rebuilding the    data on    this drive.

0x604, CRU Rebuild Complete:
The background rebuild process  has completed rebuilding the    data on    this drive.

0x606, Unit Shutdown for Trespass:
The unit which this drive is a member of has been shutdown by this SP at the request of the peer    SP, due to    a Trespass operation.

0x607, Unit Shutdown for Change Bind:
The LUN this module belongs to has been shut down by the    SP in order to change its operating parameters.  This shutdown is needed only when the SP is operating in Target Addressing Mode.

0x608, CRU Ready: A drive has successfully completed its power up procedure and is physically ready for use.

0x609, Format Started: The given FRU is being    formatted as required to operate as a Sauna disk.

0x610, Format Failed: The Format operation started by Sauna on the given FRU was not successful. This situation    should result    in the FRU being declared dead.

0x613, CRU Equalization Started: The SP    has started a Rebuild/Equalize operation.

0x614, CRU Equalize Completed: The SP    has completed a    Rebuild/Equalize operation.

0x615, CRU Equalize Aborted: The SP    has aborted a Rebuild/Equalize operation.

0x621, Background Verify    Started: A background check on the correctness of parity information has begun on the unit of which this drives    is a member.

0x622, Background Verify    Complete: The background    verify process has completed.

0x623, Fan Pack Disable/Door Open: On a storage system that has a    fan door (20- and 10-slot), the fans were disabled because the fan door was opened.  The storage system will shut down if the fans are not operational within 2     minutes.

0x624, Fan Pack Enable/Door Close: On a storage system that has a    fan door (20- and 10-slot), the fans were enabled after the open    fan door was closed.

0x630, Fan Installed: A fan module has been installed.

0x631, VSC Installed: A VSC (Power Supply) has been installed.

0x632, AC Installed: An AC Box has been installed.

0x633, Fan Speed Increased: The controller    has increased the speed    of a fan.

0x634, Fan Speed Decreased: The Fan speed has been    returned to normal.

0x635, Inconsistent Check Information: The SP    has detected an    inconsistency in the sector based check codes. An 800 code    with more explicit information usually follows this code (for example, 852 Hard Read    Checksum Error).

0x636, BBU Removed: The Battery Back-up Unit in this system has been removed.

0x637, BBU Recharging: The Battery Back-up Unit in this system is recharging.

0x638, BBU Enabled: The Battery Back-up Unit in this system has been enabled for use.

0x639, System Cache Enabled: This system has enabled the on-board cache. Caching operations will take place, as    defined    for the caching environment.

0x641, Rebuild Aborted: A background rebuild operation    has aborted prior to completing the entire disk.

0x642, Background Verify Aborted: A background verify operation has been    terminated due to    an abnormal event, such    as the failure of one of    the disks in the LUN.

0x643, SP Initializing: This SP has just detected its peer SP following a period    of time    that the peer was not present.

0x644, Peer SP Inserted: This SP has been informed by its peer SP that the peer has completed its    powerup    initialization sequence.

0x645, CRU Bound: A CRU was bound into a    LUN. The extended status is the LUN unit number. This is logged once for each CRU at    the completion of a bind operation.

0x650, CRU Signature Error: The given FRU's current physical position in the matrix    of disks does not match    its expected position (which is set    at time    the when FRU was bound into a LUN).

0x654, Cache Dumping: The controller    is dumping the cache data into the protected space on the    disk.

0x657, Cache Dump Completed: The controller    has completed the dump of the cache data.

0x658, Cache Enabled By User: The controller    is in the process of enabling the cache for use on host data.

0x659, Cache Disabled By User: The controller    is disabling the cache due to some condition or command.

0x660, AC Power Failure: AC power failed.

0x661, BBU Sniffing Enabled: This system is    no allowed to shutdown the BBU in order to test the BBU.

0x662, BBU Sniffing Disabled: BBU shutdown testing is now disabled on this system.

0x663, BBU Sniff Initiating: The BBU on this system    is beginning a shutdown test cycle.

0x664, BBU Sniff Cache Dump: The Cache data    on this    system is being    dumped to prepare for the BBU shutdown test cycle.

0x665, Configured for Single SP: The storage system has    just been configured for non-mirrored caching operation.

0x666, Configured for Dual SP: The storage system has    just been configured for mirrored caching operation.

0x667, Cache Recovering: This SP, which    is operating in    non-mirrored caching mode, is recovering the contents of the Write Cache following a reboot.

0x668, Cache Recovered: This SP, which    is operating in    non-mirrored caching mode, has successfully    completed  recovering the    contents of the    Write Cache following a reboot.

0x66A, Soft Vault Load Failure: The SP    could not load the saved contents of the Write Cache from disk.    However, there were no units with saved data,    so the Write Cache does    not need to be loaded. This situation can occur after you reconfigure SP memory.

0x66B, Single Bit Error Detected: The SP    has detected a recoverable single bit error.

0x66C, Fan Fault    Detected: The SP    has detected a single fan fault.

0x66D, Peer SP timed out: The Host SP has timed out waiting for the peer    SP to reply to a host request.

0x670, Meanings vary (see below): If the    system is not a    7-slot system, code 670h is Memory    Dump, which means that the Storage Processor has written a copy of its data space    to disk after a microcode    panic event.  The information written to    disks may help storage- system    developers analyze the cause of    the error. If the    system is a 7-slot system, code    670h is PCMCIA    (write-cache memory) card was removed while the storage system was    powered    up.  The storage system    flushed    the write cache    to disk    and disabled storage-system write caching.

0x671, PCMCIA Card Inserted: The PCMCIA (write-cache memory) card was inserted while the storage system was powered up. Storage-system    write caching cannot be    enabled until storage-system power is turned off and then on again.

0x672, PCMCIA Card Write Enabled: The PCMCIA (write-cache memory) card was write enabled.

0x673, PCMCIA Card Cleared by user request: PCMCIA    (write-cache memory) card was cleared by user request (may be done by removing the card battery or by an engineering mode command).

0x680, Invalid Data Sector Read: The hardware found a bad checksum on a    data sector.

0x681, Invalid Parity Sector Read: The hardware found a bad checksum on a    parity sector.

0x682, Invalid Sector Read: The hardware found a bad checksum on a    sector. There is not enough information to tell whether the sector holds data or parity information.

0x683, Data Sector Reconstructed: The hardware reconstructed a data sector that had a checksum of write stamp error.

0x684, Parity Sector Reconstructed: The hardware reconstructed a parity sector that had a checksum    of write stamp error.

0x685, Hard Error: The hardware detected an error    other than a parity or write stamp    error.

0x686, Command Complete: A command completed after a soft error    was corrected.

0x687, Stripe Reconstructed: On a read from    a RAID-1 mirrored pair,    a corrupted sector    was reconstructed.

0x688, Command Dropped: An optional command was dropped.

0x689, Sector Reconstructed: On a read from    a RAID-1 mirrored pair,    a corrupted sector    was reconstructed.

0x68A, Uncorrectable Parity Sector: A hard    error on a parity sector could not be corrected.

0x68B, Uncorrectable Data Sector: A hard    error on a data    sector could not be    corrected.

0x68C, Hard Read    Checksum Error: A hard    checksum error was detected on a data transfer from the host.

0x68D, Soft Read    Checksum Error: A soft    checksum error was detected on a data transfer from the host.

0x68E, Inconsistent Stripe: Inconsistent write or time stamps were    detected in a RAID    group.

0x68F, Inconsistent Time    Stamps: Inconsistent time stamps were detected    in a RAID group on a verify.

0x690, Drive Failed: A single drive   was shut down.

0x691, Checksum Error on    Device Read: A checksum error was detected on a read from an individual disk.  There was no    data transfer involved.

0x692, Incoherent Stripe: Data and parity were not consistent in    a RAID group.

0x693, Uncorrectable Stripe: Inconsistent write or time stamp could    not be corrected in a    RAID group.

0x694, Parity Invalidated: Parity    has been invalidated in    a RAID group.

0x695, Uncorrectable Sector: An uncorrectable sector was detected on a RAID-1 mirrored pair.

0x696, Mirror Sector Invalidated: A sector on a RAID-1 mirrored pair was    invalidated on a rebuild.

0x6C0, Backend Fibre Loop Failure: This SP's back-end fibre loop is off line due to an NPORT primitive.

0x6C1, Backend Fibre Loop Failure: This SP's back-end fibre loop is off line due to loop initialization primitive.

0x6C2, Backend Fibre Loop Failure: The SP    determined that    the fibre loop is hung.

0x6C3, Backend Fibre Loop Discovery ok: The SP    determined that    the fibre loop is operational following the discovery phase.

0x6C4, Backend Fibre Loop Error: A loop    node detected a    failure    condition.

0x6C5, Backend Fibre Loop Error: The SP    did not    discover a node    on its first try and will try again.  A    drive did not login as expected.

0x6C6, Backend Fibre Loop Error: The SP    did not    discover a node    on its first second try. A    drive did not login as expected.

0x6C7, Fibre Channel Unknown Event: This message indicates    an undefined error condition.

0x6C9, Backend Fibre Loop Error: An unknown event was detected on the fibre loop.

0x6CA, Front End    Fibre Loop Bad: The Fibre Channel front end has gone off line due to the    receipt    of an unexpected loop event.

0x6CB, Front End    Fibre Initiator    Gone: The SP    attempted to communicate with an initiator which has ceased responding.

0x6CC, Front End    Fibre Link Down: The Fibre Front End is    down.

0x6CD, Front End    Fibre Link Up: The Fibre Front End is    up.

0x6D0, Backend Fibre Loop Event: The SP    has initiated a    loop failover.

0x6D1, Backend Fibre Loop Event: Loop failover administratively    denied.

0x6D2, Backend Fibre Loop Event: Peer SP is no longer using this SP's loop.

0x6D3, Backend Fibre Loop Event: This SP is no longer using remove loop.

0x6D4, Backend Fibre Loop Event: The peer SP has completed failover to this SP's loop.

0x6D5, Backend Fibre Loop Event: This SP has completed failover    to remote loop.

0x6E3, Fibre Channel Initiator Gone: The SP    tried to communicate with an initiator that is no longer responding.

0x6E0, Frontend Fibre Loop Event: A front end hub port has been closed.

0x6E1, Frontend Fibre Loop Event: A front end hub port has been opened.

0x6E2, Frontend Fibre Loop Event: The SP's fibre    loop failed to initialize.

0x6E4, Fibre Channel Loop Down: A loop    down was detected. This    is a normal occurrence followed by    a loop up during loop initialization.

0x6E5, Fibre Channel Loop Up: The fibre loop    is up and ready    for communication.

0x6E6, Fibre Channel Loop Timeout: An internal timeout has occurred in the fibre channel interface.  The SP will continue taking action    to bring the link completely up.

0x6E7, Fibre Channel Lip Timeout: The fibre channel interface timed out during loop initialization.  The SP will continue taking action    to bring the link completely up.

0x6E8, Fibre Channel Link Up Timeout: The fibre channel interface timed out waiting for the link to come up. The SP will continue taking action    to bring the link completely up.

0x6E9, Frontend Fibre Loop Event: Front end fibre loop error message threshold exceeded.