HP StorageWorks 2300 Modular Smart Array reference guide (500911-001, January 2009)

98 Event code reference
As referred to in Table 14, the following table lists disk- error conditions and recommended actions.
354 Informational SAS topology has changed on a host port.
For example, the SAS cable connecting a
controller host port to a host has been
disconnected.
355 Warning The faceplate's debug button was found to
be stuck in the On position during boot up.
412 Warning One disk in the specified RAID-6 vdisk failed.
The vdisk is operational with Degraded
health and status FTDN (fault tolerant with a
down disk).
Replace the down disk with a spare so the
system can start reconstructing the vdisk.
443 Warning A firmware version mismatch has been
detected in an MSA70 drive enclosure. The
enclosure should be updated to the latest
supported version of firmware as soon as
possible.
In the drive enclosure all FRUs (I/O module,
fan, power supply, midplane, backplane,
and 7-segment LED) must be at a combined
proper firmware recipe. The two I/O
modules must be at equal firmware versions.
Any replaced MSA70 FRUs might have older
firmware that does not match an internally
defined recipe. Update the drive enclosure to
the latest firmware version to ensure all FRUs
are at the proper firmware level.
Table 15 Disk error conditions and recommended actions
Status Recommended action
The status of the vdisk that originally had the failed disk
status is Good. A global or vdisk (dedicated) spare has
been successfully integrated into the vdisk and the
replacement disk can be assigned as either a global
spare or a vdisk spare.
Use SMU to assign the new disk as either a global spare
or a vdisk spare.
The status of the disk just installed is LEFTOVER. All of the member disks in a vdisk contain metadata in
the first sectors. The storage system uses the metadata to
identify vdisk members after restarting or replacing
enclosures.
Use SMU to clear the metadata if you have a disk that
was previously a member of a vdisk. After you clear the
metadata, you can use the disk in a vdisk or as a spare.
If the status of the vdisk that originally had the failed disk
status is FATAL FAIL, two or more disks have failed.
All data in the vdisk is lost. Use the SMU Trust Vdisk
function to attempt to bring the vdisk back online.
The status of the vdisk that originally had the failed disk
status is DRV ABSENT or INCOMPLETE. These status
indicators only occur when the enclosure is initially
powered up. DRV ABSENT indicates that one disk is
bad. INCOMPLETE indicates that two or more disks are
bad.
Make sure the enclosures and associated data host were
powered on in this order: first the drive enclosures, then
the controller enclosure, then the data host. If the
power-on sequence was correct, locate and replace the
additional failed disks.
The status of the vdisk that originally had the failed disk
indicates that the vdisk is being rebuilt.
Wait for the vdisk to complete its operation.
The status of the vdisk that originally had the failed disk
is DRV FAILED.
If this status occurs after you replace a defective disk with
a known good disk, the enclosure midplane might have
experienced a failure. Replace the enclosure.
Table 14 Event code descriptions and recommended actions (continued)
Event
code
Event type Description Recommended action