<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Remapping Media Errors when Rebuilds Fail in Netservers</title>
    <link>https://community.hpe.com/t5/netservers/remapping-media-errors-when-rebuilds-fail/m-p/2768087#M2959</link>
    <description>So you suggest recreating the array with 2 new drives, and restoring from backup, I assume.  If the bad block contains live data that cannot be read, then when you ran a backup, that data has the same chance of being corrupt on the tape. If the bad block contained parity data, which was not backed up before the failure, then you have a chance of being better off than you were if you replace both drives and restore. &lt;BR /&gt;</description>
    <pubDate>Fri, 19 Jul 2002 21:38:46 GMT</pubDate>
    <dc:creator>Chris Blumenshine</dc:creator>
    <dc:date>2002-07-19T21:38:46Z</dc:date>
    <item>
      <title>Remapping Media Errors when Rebuilds Fail</title>
      <link>https://community.hpe.com/t5/netservers/remapping-media-errors-when-rebuilds-fail/m-p/2768086#M2958</link>
      <description>Hello All,&lt;BR /&gt;&lt;BR /&gt;I wanted to get some opinions as this has been a heated topic as of late:&lt;BR /&gt;Scenario is a hardware Raid 5 with 3 or more hdds.  &lt;BR /&gt;Ch 0&lt;BR /&gt;ID 0 Online A0-0  10 media errors&lt;BR /&gt;ID 1 Online A0-1  no errors&lt;BR /&gt;ID 2 Failed A0-2  no errors&lt;BR /&gt;&lt;BR /&gt;One hdd fails and the rebuild fails at the same percentage on multiple hdds.  Upon closer inspection one of the hdds that is still in an Online State has Media Errors.  &lt;BR /&gt;&lt;BR /&gt;Some techs recommend to run a disk verify off the SCSI controller and remap the bad blocks.  Doing so usually finds the bad blocks at the same percentage where the rebuild fails and once remapping is complete the rebuild will complete 100%.  Seems to be a fix.  &lt;BR /&gt;&lt;BR /&gt;However the question is what is the status of the data on the bad blocks??  If the data was corrupt on the bad blocks are you introducing corruption into the array because you essentially have two failed blocks in the Data Stripe??  If the data is ok you should be ok but how do you know?  Any thoughts on this??  &lt;BR /&gt;&lt;BR /&gt;I believe that if you are in this situation you are better off replacing the hdd that had the media error and recreating the array.  &lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;Greg</description>
      <pubDate>Fri, 19 Jul 2002 14:36:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/netservers/remapping-media-errors-when-rebuilds-fail/m-p/2768086#M2958</guid>
      <dc:creator>Greg Carlson</dc:creator>
      <dc:date>2002-07-19T14:36:15Z</dc:date>
    </item>
    <item>
      <title>Re: Remapping Media Errors when Rebuilds Fail</title>
      <link>https://community.hpe.com/t5/netservers/remapping-media-errors-when-rebuilds-fail/m-p/2768087#M2959</link>
      <description>So you suggest recreating the array with 2 new drives, and restoring from backup, I assume.  If the bad block contains live data that cannot be read, then when you ran a backup, that data has the same chance of being corrupt on the tape. If the bad block contained parity data, which was not backed up before the failure, then you have a chance of being better off than you were if you replace both drives and restore. &lt;BR /&gt;</description>
      <pubDate>Fri, 19 Jul 2002 21:38:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/netservers/remapping-media-errors-when-rebuilds-fail/m-p/2768087#M2959</guid>
      <dc:creator>Chris Blumenshine</dc:creator>
      <dc:date>2002-07-19T21:38:46Z</dc:date>
    </item>
  </channel>
</rss>

