<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>







<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>Message background and recovery options</title>
<base target="_top">
<link rel="stylesheet" href="basicpg.css">
</head>
<body text="#000000" bgcolor="#FFFFFF" link="#0000FF" vlink="#333399" alink="#0000FF">
<h1>One or more logical devices contain a bad stripe: controller [number], logical device
  [number] </h1>
<h2>Explanation:</h2>

<p> 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 device stripe.
  An entry in the BST indicates that the data contained in a stripe has been lost.
<p>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 degraded
  logical device. A single stripe unit failure is correctable and recoverable but
  two or more failures within the same redundant RAID stripe are not. </p>
<p>For example, in a degraded RAID-5 pool, in which one of the drives in the
   pool is <a href="gddd.htm">failed</a>, 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 pool.</p>
<p>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 device is unusable. </p>
<p><strong><b><img src="images/note.gif" width="15" height="17"></b> Note:</strong>
  It is not possible to correlate the bad stripe with a specific file in the operating
  system.</p>

<h2>Action:</h2>

<ul>
  <li>
    <p>Check the HP Storage Manager event logs to identify the affected logical
      drive(s). </p>
  </li>
  <li>
    <p>Because the data has been lost, the only way to recover from this condition
      is to do the following:</p>
    <blockquote>
      <p>1. Delete the pool.</p>
      <p>2. Recreate the pool and its logical devices.</p>
      <p>3. Restore the data from backup media. </p>
    </blockquote>
  </li>
  <li> The alternative is to take the entire logical device failed, thus resulting
    in the loss of all data contained on that logical device.<br>
  </li>
  <li>To minimize the risk of lost data, be sure to schedule frequent periodic
    backups.</li>
</ul>

<div align="center">
  <hr>
  <a href="gportal.htm">Glossary</a> | <a href="menutoc.htm">Contents</a></div>

<p align="right">&nbsp;</p>
<p align="right">x-0086-HSM-00-06-EN </p>

</body>




</html>
