Reference Guide

Table Of Contents
Cause and Action Cause: The bad block table is used for remapping bad disk blocks. This table fills, as bad disk blocks are
remapped. When the table is full, bad disk blocks can no longer be remapped, and disk errors can no
longer be corrected. At this point, data loss can occur. The bad block table is now 80% full.
Action: Back up your data. Replace the disk generating this alert and restore from back up.
Related Alert
Information
Clear Alert Number: None
Related Alert Number: 2307
Local Response Agent (LRA) Number: 2070
SNMP Trap
Numbers
903
Event ID 2307
Description Bad block table is full. Unable to log block %1.
Severity Critical / Failure / Error
Cause and Action Cause: The bad block table is used for remapping bad disk blocks. This table fills, as bad disk blocks are
remapped. When the table is full, bad disk blocks can no longer be remapped and disk errors can no longer
be corrected. At this point, data loss can occur. The %1 indicates a substitution variable. The text for this
substitution variable is displayed with the alert in the alert log and can vary depending on the situation.
Action: Replace the disk generating this alert. If necessary, restore your data from backup.
Related Alert
Information
Clear Alert Number: None
Related Alert Number: 2048
Local Response Agent (LRA) Number: 2071
SNMP Trap
Numbers
904
Event ID 2309
Description
A physical disk is incompatible.
Severity Warning / Non-critical
Cause and Action Cause: You have attempted to replace a disk with another disk that is using an incompatible technology.
For example, you may have replaced one side of a mirror with a SAS disk when the other side of the
mirror is using SATA technology.
Action: See the hardware documentation for information on replacing disks.
Related Alert
Information
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: 2070
SNMP Trap
Numbers
903
Event ID 2310
Description
A virtual disk is permanently degraded.
Severity Critical / Failure / Error
Cause and Action Cause: A redundant virtual disk has lost redundancy. This may occur when the virtual disk suffers the
failure of multiple physical disks. In this case, both the source physical disk and the target disk with
redundant data have failed. A rebuild is not possible because there is no redundancy.
Storage Management Message Reference 135