Table 28. Event descriptions and recommended actions (continued)
Number
Severity
Description/Recommended actions
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.
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.
209
Error
A scrub-disk job logged with event 208 has completed and found one or more media errors,
SMART events, or hard (non-media) errors. If this disk is used in a non-fault-tolerant disk group,
data may have been lost.
Recommended actions:
●
Replace the disk with one of the same type (SSD, enterprise SAS, or midline SAS) and the
same or greater capacity. For continued optimum I/O performance, the replacement disk
should have performance that is the same as or better than the one it is replacing.
Warning
A scrub-disk job logged with event 208 has been aborted by a user, or has reassigned a disk
block. These bad-block replacements are reported as "other errors". If this disk is used in a
non-fault-tolerant disk group, data may have been lost.
Recommended actions:
92
Events and event messages
