Owners Manual

Table 27. Event descriptions and recommended actions (continued)
Number Severity Description/Recommended actions
● No action is required.
206 Info. Disk group scrub has started.
The scrub checks disks in the disk group for the following types of errors:
● Data parity errors for a RAID 3, 5, 6, or 50 disk group.
● Mirror verify errors for a RAID 1 or RAID 10 disk group.
● Media errors for all RAID levels including RAID 0 and non-RAID disk groups.
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 Disk group scrub completed and found an excessive number of errors in the indicated disk group.
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 disk group.
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 disk group have logged SMART events or unrecoverable read
errors.
○ If so, and the disk group is a non-fault-tolerant RAID level (RAID 0 or non-RAID), copy
the data to a different disk group and replace the faulty disks.
○ If so, and the disk group is a fault-tolerant RAID level, check the current state of the
disk group. If it is not FTOL then back up the data as data may be at risk. If it is FTOL
then replace the indicated disk. If more than one disk in the same disk group has logged
a SMART event, back up the data and replace each disk one at a time. In virtual storage
it may be possible to remove the affected disk group, which will drain its data to another
disk group, and then re-add the disk group.
Warning Disk group 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.
○ If so, and the disk group is a non-fault-tolerant RAID level (RAID 0 or non-RAID), copy
the data to a different disk group and replace the faulty disks.
○ If so, and the disk group is a fault-tolerant RAID level, check the current state of the
disk group. If it is not FTOL then back up the data as data may be at risk. If it is FTOL
then replace the indicated disk. If more than one disk in the same disk group has logged
a SMART event, back up the data and replace each disk one at a time. In virtual storage
it may be possible to remove the affected disk group, which will drain its data to another
disk group, and then re-add the disk group.
Info. Disk group 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.
Events and event messages 93