HP P2000 HP P2000 G3 MSA System Event Description Reference Guide - Page 42

Condition, Recommended action

Page 42 highlights

Disk error conditions and recommended actions Table 1 Disk error conditions and recommended actions Condition Recommended action Event 8 reports that the RAID controller can no longer detect the disk. Reseat the disk. If this does not resolve the problem, replace the disk. Event 8 reports a media error for the disk. Replace the disk. Event 8 reports a SMART error for the disk. Replace the disk. Event 8 reports a hardware error for the disk. Replace the disk. Event 8 reports an Illegal Request sense code for a Replace the disk. command the disk should support. Event 8 reports that the disk was intentionally failed No action required. by RAID-6 logic. At the time a disk failed, the dynamic spares No action required; the system automatically uses feature was enabled and a properly sized disk was that disk to reconstruct the vdisk. available to use as a spare. At the time a disk failed, the dynamic spares Replace the disk so the system can automatically feature was enabled but no properly sized disk was use the new disk to reconstruct the vdisk. 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. Replace the disk and use SMU to assign the new disk as a spare for the vdisk so the system can automatically use that disk to reconstruct the vdisk. 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 LEFTOVR. 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. See the topic about clearing disk metadata in the SMU reference guide. If the status of the vdisk that originally had the failed disk status is FATAL FAIL, one or more disks have failed in a RAID-0 vdisk; two or more disks have failed in a RAID-1, 3, or 5 vdisk; or three or more disks have failed in a RAID-6 vdisk. All data in the vdisk is lost. Use the CLI trust command 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 Wait for the vdisk to complete its operation. disk indicates that the vdisk is being rebuilt. 42

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48

42
Disk error conditions and recommended actions
Table 1
Disk error conditions and recommended actions
Condition
Recommended action
Event 8 reports that the RAID controller can no
longer detect the disk.
Reseat the disk. If this does not resolve the problem,
replace the disk.
Event 8 reports a media error for the disk.
Replace the disk.
Event 8 reports a SMART error for the disk.
Replace the disk.
Event 8 reports a hardware error for the disk.
Replace the disk.
Event 8 reports an Illegal Request sense code for a
command the disk should support.
Replace the disk.
Event 8 reports that the disk was intentionally failed
by RAID-6 logic.
No action required.
At the time a disk failed, the dynamic spares
feature was enabled and a properly sized disk was
available to use as a spare.
No action required; the system automatically uses
that disk to reconstruct the vdisk.
At the time a disk failed, the dynamic spares
feature was enabled but no properly sized disk was
available to use as a spare.
Replace the disk so the system can automatically
use the new disk to reconstruct the vdisk.
At the time a disk failed, the dynamic spares
feature was disabled and no dedicated spare or
properly sized global spare was available.
Replace the disk and use SMU to assign the new
disk as a spare for the vdisk so the system can
automatically use that disk to reconstruct the vdisk.
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 LEFTOVR.
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.
See the topic about clearing disk metadata in the
SMU reference guide.
If the status of the vdisk that originally had the
failed disk status is FATAL FAIL, one or more disks
have failed in a RAID-0 vdisk; two or more disks
have failed in a RAID-1, 3, or 5 vdisk; or three or
more disks have failed in a RAID-6 vdisk.
All data in the vdisk is lost. Use the CLI
trust
command 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.