HP MSA 2040 Troubleshooting Manual page 13

Table 5 Disk error conditions and recommended actions (continued)
Symptom
Event 8 reports that RAID-6 logic
intentionally failed the disk.
Event 55 reports a SMART error for the
disk.
At the time, a disk failed, the dynamic
spares feature was enabled, and a
properly sized disk was available to use
as a spare.
At the time, a disk failed, the dynamic
spares feature was enabled but no
properly sized disk was available to use
as a spare.
At the time, a disk failed, the dynamic
spares feature was disabled and no
dedicated spare or properly sized global
spare was available.
The status of the Vdisk or disk group that
originally had the failed disk status is
Good. A global Vdisk or disk group
(dedicated) spare has been successfully
integrated into the Vdisk or disk group and
the replacement disk can be assigned as
either a global spare or a Vdisk or disk
group spare.
The status of the disk installed is
LEFTOVR
If the status of the Vdisk or disk group that
originally had the failed disk status is
OFFL (Offline) or QTOF (Quarantined
Offline), one or more disks have failed in
a RAID-0 Vdisk or disk group. Two or
more disks have failed in a RAID-1, 3, or
5 Vdisk or disk group. Three or more disks
have failed in a RAID-6 Vdisk or disk
group.
The status of the Vdisk or disk group that
originally had the failed disk indicates that
the Vdisk or disk group is being rebuilt.
The status of the Vdisk or disk group that
originally had the failed disk is CRIT
(Critical) or QTDN (Quarantined with a
down disk).
Recommended Action
Failed, and data recovery is needed, see
(page 26).
Replace the disk.
If all the volumes and Vdisks or disk groups are online and available,
then replace the disk. If the drive is marked as Leftover or Failed, and
data recovery is needed, see
No action required; the system automatically uses that disk to reconstruct
the Vdisk or disk group. Replace the failed disk when reconstruction has
completed.
The best option is to supply an appropriately sized spare so the system
can automatically use the new disk to reconstruct the Vdisk or disk group,
and replace the failed disk once reconstruction has completed. If that is
not possible, and all Vdisks or disk groups are online and your data is
available, then replace the failed disk with an appropriately sized disk.
Assign the replacement disk as a spare unless dynamic sparing is
enabled.
The best option is to supply an appropriately sized disk using the SMU
or CLI. Assign it as a dedicated Vdisk or disk group spare and let the
system automatically reconstruct the Vdisk or disk group, then replace
the failed disk once reconstruction is complete. If that is not possible,
and all Vdisks or disk groups are online and the data is available, then
replace the failed disk with an appropriately sized disk. Assign the
replacement disk as a spare.
Use SMU to assign the new disk as either a global spare or a Vdisk or
disk group spare.
All the member disks in a Vdisk or disk group contain metadata in the
first sectors. The storage system uses the metadata to identify Vdisk or
disk group members after restarting or replacing enclosures. This disk
was a member of a Vdisk or disk group on another system, and that Vdisk
or disk group does not exist on this system. Clear the drive metadata if
it is not required for a Vdisk or disk group from another array.
The data in the Vdisk or disk group is inaccessible and at risk. Attempt
to recover by reseating the last failed drives. If that does not resolve the
issue, and data recovery is needed, see
(page 26).
Wait for the Vdisk or disk group to complete its operation. Do not remove
any leftover drives until the rebuild is complete.
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.
"Using the Trust Command"
"Using the Trust Command" (page
"Using the Trust Command"
Disk Drives
26).
13