User guide

122 Event Logs
Drive & Array Event
Messages
Type [ID] Cause Action
A rebuild has started on
the drive w/SN (SAS: w/
WWN) <xxxxxx> (Slot
<nn> (Drive <number>).
Information
[0xB30 (2864)]
A rebuild has started. No action necessary.
A rebuild has
completed on (Array
<Name> Drive
<number>)
Information
[0xB31 (2865)]
A rebuild has
completed.
No action necessary.
A rebuild has re-
started on the drive
w/SN (SAS: w/WWN
<xxxxxx> (Slot <nn>
(Drive <number>).
Information
[0xB32 (2866)]
A rebuild has started. No action necessary.
Array <name> has
started initializing.
Information
[0xB33 (2867)]
Initialization has
started.
No action necessary.
Array <name> has
completed initializing.
Information
[0xB34 (2868)]
Initialization has
completed.
No action necessary.
The controller has
detected a data
underrun from the
drive w/SN (SAS:
w/WWN) (Slot <nn>,
Enclosure <nn>) for the
SCSI Op Code 0x<xx>.
This is caused by the
controller detecting a
bad CRC in a frame,
and usually indicates
a link problem, either
with cabling or an
enclosure.
Error
[0xB3B (2875)]
Bus error. Check cabling and
ensure that the disk
drive is properly seated
in its slot.
An unrecoverable drive
error has occurred as
a result of a command
being issued. This may
be due to a drive error
in a non-fault tolerant
array, such as RAID 0,
or when the array is
already in a degraded
mode. The controller
will pass the status
from the drive back
tothe host system, to
allow the host recovery
mechanisms to be
used. Details: Host
Loop <x>, Host Loop
ID <y>, Mapped LUN
Requested <z>,Op Code
<zz>, Sense Data <uu>.
Error
[0xB40 (2880)]
Typically due to a
non-recoverable media
error, hardware error,
or loop (bus) error.
No action necessary.