User's Manual

When a system in a cluster attempts to rebuild a failed disk but the rebuild fails, then another system takes over the rebuild. In this situation, you may notice
that the rebuilt disk continues to be marked as failed on both systems even after the second system has rebuilt successfully. To resolve this problem, perform
a rescan on both systems after the rebuild completes successfully.
Receive a "Bad Block" Alert with "Replacement," "Sense," or "Medium" Error
The following alerts or events are generated when a portion of a physical disk is damaged:
l "2146"
l "2147"
l "2148"
l "2149"
l "2150"
This damage is discovered when the controller performs an operation that requires scanning the disk. Examples of operations that may result in these alerts
are as follows:
l Consistency check
l Rebuild
l Virtual disk format
l I/O
If you receive an alerts 2146 through 2150 as the result of doing a rebuild or while the virtual disk is in a degraded state, then data cannot be recovered from
the damaged disk without restoring from backup. If you receive alerts 2146 through 2150 under circumstances other than a rebuild, then data recovery may
be possible. The following describes each of these situations.
Alerts 2146 through 2150 Received during a Rebuild or while a Virtual Disk is Degraded
Do the following if you receive alerts 2146 through 2150 during a rebuild or while the virtual disk is in a degraded state:
1. Replace the damaged physical disk.
2. Create a new virtual disk and allow the virtual disk to completely resynchronize. While the resynchronization is in progress, the status of the virtual disk
will be Resynching.
3. Restore data to the virtual disk from backup.
Alerts 2146 through 2150 Received while Performing I/O, Consistency Check, Format, or Other Operation
If you receive alerts 2146 through 2150 while performing an operation other than a rebuild, you should replace the damaged disk immediately to avoid data
loss.
Do the following:
1. Back up the degraded virtual disk to a fresh (unused) tape.
2. Replace the damaged disk.
3. Do a rebuild.
Read and Write Operations Experience Problems
If the system is hanging, timing out, or experiencing other problems with read and write operations, then there may be a problem with the controller cables or
a device. For more information, see "Cables Attached Correctly" and "Isolate Hardware Problems."