3dm2/help/en/Maintain_Units.7.17.html

233 lines
18 KiB
HTML
Raw Permalink Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xml:lang="en" lang="en" xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
<meta http-equiv="Content-Style-Type" content="text/css" />
<title>About Verification</title>
<link rel="StyleSheet" href="css/Maintain_Units.css" type="text/css" media="all" />
<link rel="StyleSheet" href="css/webworks.css" type="text/css" media="all" />
<script type="text/javascript" language="JavaScript1.2" src="scripts/expand.js"></script>
<script type="text/javascript" language="JavaScript1.2" src="scripts/seealso.js"></script>
<script type="text/javascript" language="JavaScript1.2">
<!--
var WebWorksRootPath = "";
// -->
</script>
<script type="text/javascript" language="JavaScript1.2">
<!--
var WebWorksSeeAlso = "xxx";
// -->
</script>
</head>
<body style="">
<table align="right">
<tr>
<td style="text-align: left;">
<a href="http://www.lsi.com/channel/products" target="_blank">
<img src="LSI-logo.jpg" border="0" />
</a>
</td>
</tr>
</table>
<div style="text-align: left;">
<p style="color: Navy; font-weight:bold">3DM2™ Online
Help</p>
<table cellspacing="0">
<tr>
<td>
<a href="toc.html">
<img src="images/toc.gif" alt="Table of Contents" border="0" />
</a>
</td>
<td>
<a href="Maintain_Units.7.16.html">
<img src="images/prev.gif" alt="Previous" border="0" />
</a>
</td>
<td>
<a href="Maintain_Units.7.18.html">
<img src="images/next.gif" alt="Next" border="0" />
</a>
</td>
<td>
<a href="ix.html">
<img src="images/index.gif" alt="Index" border="0" />
</a>
</td>
</tr>
</table>
</div>
<br clear="all" />
<br />
<div class="WebWorks_Breadcrumbs" style="text-align: left;">
<a class="WebWorks_Breadcrumb_Link" href="Maintain_Units.7.1.html#1080320">Maintaining Units</a> &gt; <a class="WebWorks_Breadcrumb_Link" href="Maintain_Units.7.15.html#1080320">Background Tasks</a> &gt; About Verification</div>
<hr align="left" />
<div>
<div class="Heading2"><a name="1080320">About Verification</a></div>
<div class="Body"><a name="1675406">This topic is organized into the following:</a></div>
<div class="Bullet-single_outer" style="margin-left: NaN;">
<table border="0" cellspacing="0" cellpadding="0" id="SummaryNotRequired_np1675410">
<tr style="vertical-align: baseline;">
<td>
<div class="Bullet-single_inner" style="width: 1.5em; white-space: nowrap;">
<img src="sqbullet.gif" alt="*" id="bullet1675410" border="0" width="8" height="8" />
</div>
</td>
<td width="100%">
<div class="Bullet-single_inner"><a href="#1675428" name="1675410">Overview of Verification</a></div>
</td>
</tr>
</table>
</div>
<div class="Bullet-single_outer" style="margin-left: NaN;">
<table border="0" cellspacing="0" cellpadding="0" id="SummaryNotRequired_np1675414">
<tr style="vertical-align: baseline;">
<td>
<div class="Bullet-single_inner" style="width: 1.5em; white-space: nowrap;">
<img src="sqbullet.gif" alt="*" id="bullet1675414" border="0" width="8" height="8" />
</div>
</td>
<td width="100%">
<div class="Bullet-single_inner"><a href="#1173696" name="1675414">What Verification Does</a></div>
</td>
</tr>
</table>
</div>
<div class="Bullet-single_outer" style="margin-left: NaN;">
<table border="0" cellspacing="0" cellpadding="0" id="SummaryNotRequired_np1675418">
<tr style="vertical-align: baseline;">
<td>
<div class="Bullet-single_inner" style="width: 1.5em; white-space: nowrap;">
<img src="sqbullet.gif" alt="*" id="bullet1675418" border="0" width="8" height="8" />
</div>
</td>
<td width="100%">
<div class="Bullet-single_inner"><a href="#1155198" name="1675418">Verification of Non-Redundant Units</a></div>
</td>
</tr>
</table>
</div>
<div class="Bullet-single_outer" style="margin-left: NaN;">
<table border="0" cellspacing="0" cellpadding="0" id="SummaryNotRequired_np1675422">
<tr style="vertical-align: baseline;">
<td>
<div class="Bullet-single_inner" style="width: 1.5em; white-space: nowrap;">
<img src="sqbullet.gif" alt="*" id="bullet1675422" border="0" width="8" height="8" />
</div>
</td>
<td width="100%">
<div class="Bullet-single_inner"><a href="#1155201" name="1675422">Verification of Redundant Units</a></div>
</td>
</tr>
</table>
</div>
<div class="Bullet-single_outer" style="margin-left: NaN;">
<table border="0" cellspacing="0" cellpadding="0" id="SummaryNotRequired_np1675426">
<tr style="vertical-align: baseline;">
<td>
<div class="Bullet-single_inner" style="width: 1.5em; white-space: nowrap;">
<img src="sqbullet.gif" alt="*" id="bullet1675426" border="0" width="8" height="8" />
</div>
</td>
<td width="100%">
<div class="Bullet-single_inner"><a href="#1155204" name="1675426">How Errors Are Handled</a></div>
</td>
</tr>
</table>
</div>
<div class="Heading3"><a name="1675428">Overview of Verification</a></div>
<div class="Body"><a name="1573062">The verify feature confirms the validity of redundant data on redundant units </a>and performs media scans on non-redundant units.</div>
<div class="Body"><a name="1329152">Regular weekly verification is a good idea, as it can provide early warning of </a>a disk drive problem or failure. This allows you to replace drives before they fail.</div>
<div class="Body"><a name="1517627">You can start a verify manually or regular verification can be done </a>automatically by enabling Auto-Verify. (See <a href="Maintain_Units.7.19.html#1522248">Starting a Verify Manually</a> and <a href="Maintain_Units.7.18.html#1261503">Using Auto Verification</a>.)</div>
<div class="Body"><a name="1185319">During verification, I/O continues normally, but with a slight performance </a>loss, depending on your verify rate setting. You can adjust how much verification will slow performance by setting a rate at which it occurs. (See <a href="Maintain_Units.7.24.html#1585765">Setting Background Task Rate</a>.) You can also postpone verification until a scheduled time. (See <a href="Maintain_Units.7.26.html#1112466">Scheduling Background Tasks</a>.)</div>
<div class="anchor">
<span class="Red"> </span><a name="1241304">&nbsp;</a></div>
<table id="1241308" class="NoteTable" style="margin-bottom: pt; margin-right: pt; margin-top: pt; padding-bottom: pt; padding-left: pt; padding-right: pt; padding-top: pt; text-align: left;" cellspacing="0">
<caption></caption>
<tr style="vertical-align: top;">
<td id="tc1241310" style="background-color: Transparent; border-bottom-color: White; border-bottom-style: solid; border-bottom-width: thin; border-left-color: White; border-left-style: solid; border-left-width: thin; border-right-color: White; border-right-style: solid; border-right-width: thin; border-top-color: White; border-top-style: solid; border-top-width: thin; padding-bottom: pt; padding-left: pt; padding-right: pt; padding-top: pt; vertical-align: top;">
<div class="NoteAnchor">
<img src="Note.gif" alt="*" id="bullet1241310" border="0" width="27" height="34" /><a name="1241310">&nbsp;</a></div>
</td>
<td id="tc1241312" style="background-color: Transparent; border-bottom-color: White; border-bottom-style: solid; border-bottom-width: thin; border-left-color: White; border-left-style: solid; border-left-width: thin; border-right-color: White; border-right-style: solid; border-right-width: thin; border-top-color: White; border-top-style: solid; border-top-width: thin; padding-bottom: pt; padding-left: pt; padding-right: pt; padding-top: pt; vertical-align: top;">
<div class="CellBody"><span class="NoteHeading"><a name="1241320">Note:</a></span> Not verifying the unit periodically can lead to an unstable unit and may cause data loss.</div>
<div class="CellBody"><a name="1241312">It is strongly recommended that you schedule a verify at least 1 time per week. You </a>can take advantage of the the Auto-Verify and Basic Verify Schedule to accomplish this.</div>
</td>
</tr>
</table>
<div class="Heading3"><a name="1173696">What Verification Does</a></div>
<div class="Body"><a name="1431947">For a RAID 1 or RAID 10 unit, a verify compares the data of one mirror with </a>the other. For RAID 5, RAID 6, and RAID 50, a verify calculates parity and compares it to what is written on the disk drive. For non-redundant units, it performs a media scan.</div>
<div class="Body"><a name="1155896">Verification checks each sector on a drive. This is important, because day-to-</a>day use of the media may leave many sectors on a drive unused or unchecked for long periods of time. This can result in errors occurring during user operation. Periodic verification of the media allows the disk drive firmware to take corrective actions on problem areas on the disk, minimizing the occurrence of uncorrectable read and write errors.</div>
<div class="Body"><a name="1573107">Verifies can be performed through either 3BM (BIOS) or through 3DM2. In </a>addition, they can be scheduled to run at preferred times, through 3DM2 or through the CLI, or can be run automatically during the Verify schedule window, if scheduling and the Auto-Verify feature are enabled.</div>
<div class="Body" style="color: #000000; font-style: normal; font-variant: normal; font-weight: normal; text-transform: none; vertical-align: baseline;"><a name="1622474">&nbsp;</a></div>
<table id="1622457" class="NoteTable" style="margin-bottom: pt; margin-right: pt; margin-top: pt; padding-bottom: pt; padding-left: pt; padding-right: pt; padding-top: pt; text-align: left;" cellspacing="0">
<caption></caption>
<tr style="vertical-align: top;">
<td id="tc1622459" style="background-color: Transparent; border-bottom-color: White; border-bottom-style: solid; border-bottom-width: thin; border-left-color: White; border-left-style: solid; border-left-width: thin; border-right-color: White; border-right-style: solid; border-right-width: thin; border-top-color: White; border-top-style: solid; border-top-width: thin; padding-bottom: pt; padding-left: pt; padding-right: pt; padding-top: pt; vertical-align: top;">
<div class="NoteAnchor">
<img src="Note.gif" alt="*" id="bullet1622459" border="0" width="27" height="34" /><a name="1622459">&nbsp;</a></div>
</td>
<td id="tc1622461" style="background-color: Transparent; border-bottom-color: White; border-bottom-style: solid; border-bottom-width: thin; border-left-color: White; border-left-style: solid; border-left-width: thin; border-right-color: White; border-right-style: solid; border-right-width: thin; border-top-color: White; border-top-style: solid; border-top-width: thin; padding-bottom: pt; padding-left: pt; padding-right: pt; padding-top: pt; vertical-align: top;">
<div class="CellBody"><span class="NoteHeading"><a name="1622461">Mac User Note:</a></span> Disregard the paragraph above, and replace with “Verifies can be scheduled to run at preferred times or can be run automatically during the Verify schedule window, if scheduling and the Auto Verify feature are enabled.”</div>
</td>
</tr>
</table>
<div class="Heading3"><a name="1155198">Verification of Non-Redundant Units</a></div>
<div class="Body"><a name="1431983">Verification of non-redundant units (single disks, spares, and RAID 0 units) </a>read each sector of a drive, sequentially. If a sector cant be read, it is flagged as unreadable, and the next time the controller writes to that location, the drive reallocates the data to a different sector. </div>
<div class="Heading3"><a name="1155201">Verification of Redundant Units</a></div>
<div class="Body"><a name="1155202">Verification of redundant units reads each sector, working from lowest block </a>to highest block. If verification cannot read data in a sector, dynamic sector repair is used to recover the lost data from the redundant drive or drives; this recovered data is written to the problem sector. This forces the drive to reallocate the defective sector with a good spare sector. </div>
<div class="Body"><a name="1432001">If the verify unit process determines that the mirrored drives are not identical </a>or the parity is not correct, the error is corrected. For RAID 1 and 10, this involves copying the miscompared data from the lower port(s) to the higher port(s) of the mirror. For RAID 5, RAID 6, and RAID 50, this involves recalculating and rewriting the parity that was incorrect. AEN 36 (“Verify detected and fixed data/parity mismatch”) is posted to the Alarms page. </div>
<div class="Body"><a name="1432006">For RAID 1 and 10, verification involves copying the data from the lower </a>port(s) to the higher port(s) of the mirror. For RAID 5 and RAID 50, this involves recalculating and rewriting the parity for the entire unit. If the unit is not redundant, a file-system check is recommended to correct the issue. If the errors persist and cannot be overwritten from a backup copy, perform a final incremental backup. You will need to replace the defective drive, recreate the unit, and reinstall the data.</div>
<div class="Heading3"><a name="1155204">How Errors Are Handled</a></div>
<div class="Body"><a name="1155949">Verification makes use of the same error checking and error repair techniques </a>used during ordinary use of drives configured through 3ware RAID controllers. </div>
<div class="Body"><a name="1155206">When verification encounters an error, the controller typically retries the </a>command. If there are cable CRC errors, there may be multiple retries including downgrade of the UDMA mode. If the error persists and is unrepairable (e.g., ECC errors), an error notification is issued to indicate the problem. (See AEN <a href="AEN_0026.html#1146557">0026 Drive ECC error reported</a>.) </div>
<div class="Body"><a name="1155210">If the disk drive is part of a redundant unit that is in a redundant state (not </a>degraded or rebuilding), then Dynamic Sector Repair automatically rewrites the redundant data to the error location to force the drive to reallocate the error location. A notification of repair is posted to the alarms list. The result is a restoration of drive and data integrity; the primary and redundant data are again both valid. </div>
<div class="Body"><a name="1261500">If the unit is not redundant, it is recommended that you perform a file-system </a>check to correct the issue. Under Windows, you can do this by right-clicking on the Drive and choosing Properties; then on the Tools tab, click Check Now. Under Mac OS X, you can do this using the First Aid tab in the Disk Utility—select the disk on the left and then click Verify Disk. If verification encounters problems, you can then use the Repair Disk option on the same screen.</div>
<div class="Body"><a name="1622499">If the errors persist and cannot be overwritten from a backup copy, perform a </a>final backup of files that have changed since your last backup. You will need to replace the defective drive, recreate the array, and reinstall the data. </div>
</div>
<hr align="left" />
<div style="text-align: left;">
<table cellspacing="0">
<tr>
<td>
<a href="toc.html">
<img src="images/toc.gif" alt="Table of Contents" border="0" />
</a>
</td>
<td>
<a href="Maintain_Units.7.16.html">
<img src="images/prev.gif" alt="Previous" border="0" />
</a>
</td>
<td>
<a href="Maintain_Units.7.18.html">
<img src="images/next.gif" alt="Next" border="0" />
</a>
</td>
<td>
<a href="ix.html">
<img src="images/index.gif" alt="Index" border="0" />
</a>
</td>
</tr>
</table>
</div>
<table align="right">
<tr>
<td style="text-align: left;">
<a href="http://www.lsi.com/channel/products" target="_blank">
<img src="LSI-logo.jpg" border="0" />
</a>
</td>
</tr>
<tr>
<td style="text-align: left; font-size: 16px ; font-weight: bold">
<a href="http://www.lsi.com/channel/products" target="_blank">LSI Corporation</a>
</td>
</tr>
</table>
<p style="font-size: .8em">Copyright LSI 2004-2010<br />
To contact Support, go to <a href="http://www.lsi.com/channel/ContactUs">http://www.lsi.com/channel/ContactUs</a></p>
</body>
</html>