Technical data

5–24 Event Reporting: Templates and Codes
021A0064 Disk Bad Block Replacement attempt completed for a write of controller
metadata to a location outside the user data area of the disk. Note that
due to the way Bad Block Replacement is performed on SCSI disk drives,
information on the actual replacement blocks is not available to the
controller and is therefore not included in the event report.
41
021B0064 Disk Bad Block Replacement attempt completed for a read of controller
metadata from a location outside the user data area of the disk. Note
that due to the way Bad Block Replacement is performed on SCSI disk
drives, information on the actual replacement blocks is not available to
the controller and is therefore not included in the event report.
41
021D0064 Unable to lock the other controller’s cache in a write-cache failover
attempt. Either a latent error could not be cleared on the cache or the
other controller did not release its cache. Note that in this instance the
Memory Address, Byte Count, FX Chip register, Memory Controller
register, and Diagnostic register fields are undefined.
14
021E0064 The device specified in the Device Locator field has been added to the
RAIDset associated with the logical unit.The RAIDset is now in
Reconstructing state.
51
02280064 The device specified in the Device Locator field has been added to the
Mirrorset associated with the logical unit. The new Mirrorset member is
now in Copying state.
51
022C0064 The device specified in the Device Locator has transitioned from Copying
or Normalizing state to Normal state.
51
022E0064 The device specified in the Device Locator field has been converted to a
Mirrorset associated with the logical unit.
51
022F0064 The mirrored device specified in the Device Locator field has been
converted to a single device associated with the logical unit.
51
Table 5–1 Instance Codes (Continued)
Instance Code Description Template