# One or more logical drives contain a bad stripe: controller [number], logical drive [number]

## Explanation:

The Bad Stripe Table (BST) provides a means of recovering most data on a logical drive after multiple hardware errors prevent access to a logical drive stripe. An entry in the BST indicates that the data contained in a stripe has been lost.

While many conditions can produce a Bad Stripe Table entry, the most common cause is an error accessing one of the stripe units within a stripe of a critical logical drive. A single stripe unit failure is correctable and recoverable but two or more failures within the same redundant RAID stripe are not.

For example, in a critical RAID-5 array, in which one of the drives in the array is defunct, a stripe will be marked bad with an entry in the BST if a non-recoverable media error occurs when accessing one of the other drives of the array.

Once an entry is logged in the BST, the controller will return an error code to the driver whenever the host system tries to access a Logical Block Address (LBA) within the affected stripe. This is one immediate indication that some part of the logical drive is unusable.

Note: It is not possible to correlate the bad stripe with a specific file in the operating system.

## Action:

- Check the ServeRAID Manager event logs to identify the affected logical drive(s).

- Because the data has been lost, the only way to recover from this condition is to do the following:

  > 1. Delete the array.

  > 2. Recreate the array and its logical drives.

  > 3. Restore the data from backup media.

- The alternative is to take the entire logical drive offline, thus resulting in the loss of all data contained on that logical drive.
- To minimize the risk of lost data, be sure to schedule frequent periodic backups.

Glossary | Contents

x-0086-SRM-00-06-EN