HP P2000 G3 MSA Reference Manual page 32

Hide thumbs Also See for P2000 G3 MSA:
Table of Contents

Advertisement

206
Info.
Vdisk scrub has started.
The scrub checks disks in the vdisk for the following types of errors:
Data parity errors for a RAID 3, 5, 6, or 50 vdisk
Mirror verify errors for a RAID 1 or RAID 10 vdisk
Media errors for all RAID levels including RAID 0 and non-RAID vdisk
When errors are detected, they are automatically corrected.
When the scrub is complete, event 207 is logged.
Recommended actions
No action is required.
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-redundant 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-redundant 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 redundant 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-redundant 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 redundant 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.
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-redundant RAID levels (RAID 0 and non-RAID), media errors may indicate loss of data.
Recommended actions
• No action is required.
32
Event descriptions

Advertisement

Table of Contents
loading

Table of Contents