HP MSA 1040 HP MSA Events Description Reference Guide (762785-001, March 2014) - Page 30

If a disk fails, data may be at risk.

Get HP MSA 1040 PDF manuals and user guides View all HP MSA 1040 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 30 highlights

207 Error Vdisk scrub completed and found an excessive number of errors in the indicated vdisk. This event is logged as Error severity when more than 100 parity or mirror mismatches are found and corrected during a scrub or when 1 to 99 parity or mirror mismatches are found and corrected during each of 10 separate scrubs of the same vdisk. For non-fault-tolerant RAID levels (RAID 0 and non-RAID), media errors may indicate loss of data. Recommended actions • Resolve any non-disk hardware problems, such as a cooling problem or a faulty controller module, expansion module, or power supply. • Check whether any disks in the vdisk have logged SMART events or unrecoverable read errors. • If so, and the vdisk is a non-fault-tolerant RAID level (RAID 0 or non-RAID), copy the data to a different vdisk and replace the faulty disks. • If so, and the vdisk is a fault-tolerant RAID level, replace the faulty disks. Before replacing a disk, confirm that a reconstruction is not currently running on the vdisk. It is also recommended to make a full backup of all the data on the vdisk before replacing disks. If more than one disk in the vdisk has errors, replace the disks one at a time and allow reconstruction to complete after each disk is replaced. Warning Vdisk scrub did not complete because of an internally detected condition such as a failed disk. If a disk fails, data may be at risk. Recommended actions • Resolve any non-disk hardware problems, such as a cooling problem or a faulty controller module, expansion module, or power supply. • Check whether any disks in the vdisk have logged SMART events or unrecoverable read errors. • If so, and the vdisk is a non-fault-tolerant RAID level (RAID 0 or non-RAID), copy the data to a different vdisk and replace the faulty disks. • If so, and the vdisk is a fault-tolerant RAID level, replace the faulty disks. Before replacing a disk, confirm that a reconstruction is not currently running on the vdisk. It is also recommended to make a full backup of all the data in the vdisk before replacing disks. If more than one disk in the vdisk has errors, replace the disks one at a time and allow reconstruction to complete after each disk is replaced. Info. Vdisk scrub completed or was aborted by a user. This event is logged as Informational severity when fewer than 100 parity or mirror mismatches are found and corrected during a scrub. For non-fault-tolerant RAID levels (RAID 0 and non-RAID), media errors may indicate loss of data. Recommended actions • No action is required. 208 Info. A scrub-disk job has started for the indicated disk. The result will be logged with event 209. Recommended actions • No action is required. 30 Event descriptions

  • 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
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
30
Event descriptions
207
Error
Vdisk scrub completed and found an excessive number of errors in the indicated vdisk.
This event is logged as Error severity when more than 100 parity or mirror mismatches are found and
corrected during a scrub or when 1 to 99 parity or mirror mismatches are found and corrected during
each of 10 separate scrubs of the same vdisk.
For non-fault-tolerant RAID levels (RAID 0 and non-RAID), media errors may indicate loss of data.
Recommended actions
•
Resolve any non-disk hardware problems, such as a cooling problem or a faulty controller module,
expansion module, or power supply.
•
Check whether any disks in the vdisk have logged SMART events or unrecoverable read errors.
•
If so, and the vdisk is a non-fault-tolerant RAID level (RAID 0 or non-RAID), copy the data to a
different vdisk and replace the faulty disks.
•
If so, and the vdisk is a fault-tolerant RAID level, replace the faulty disks. Before replacing a disk,
confirm that a reconstruction is not currently running on the vdisk. It is also recommended to make
a full backup of all the data on the vdisk before replacing disks. If more than one disk in the vdisk
has errors, replace the disks one at a time and allow reconstruction to complete after each disk is
replaced.
Warning
Vdisk scrub did not complete because of an internally detected condition such as a failed disk.
If a disk fails, data may be at risk.
Recommended actions
•
Resolve any non-disk hardware problems, such as a cooling problem or a faulty controller module,
expansion module, or power supply.
•
Check whether any disks in the vdisk have logged SMART events or unrecoverable read errors.
•
If so, and the vdisk is a non-fault-tolerant RAID level (RAID 0 or non-RAID), copy the data to a
different vdisk and replace the faulty disks.
•
If so, and the vdisk is a fault-tolerant RAID level, replace the faulty disks. Before replacing a disk,
confirm that a reconstruction is not currently running on the vdisk. It is also recommended to make
a full backup of all the data in the vdisk before replacing disks. If more than one disk in the vdisk
has errors, replace the disks one at a time and allow reconstruction to complete after each disk is
replaced.
Info.
Vdisk scrub completed or was aborted by a user.
This event is logged as Informational severity when fewer than 100 parity or mirror mismatches are found
and corrected during a scrub.
For non-fault-tolerant RAID levels (RAID 0 and non-RAID), media errors may indicate loss of data.
Recommended actions
•
No action is required.
208
Info.
A scrub-disk job has started for the indicated disk. The result will be logged with event 209.
Recommended actions
•
No action is required.