<?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 Disk error code 33 in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/disk-error-code-33/m-p/4447473#M142189</link>
    <description>I've taken over a Proliant ML 150 with two 136 Gig Compaq drives mirrored.  About once a day for the last year and a half, the Event Viewer logs a Error code 33 on HD 0.  It says "Data was recovered using error correction code on device \Device \Harddisk 0.  I never see the error for disk 1.  &lt;BR /&gt;&lt;BR /&gt;Is this just a file system problem?  Do I just hit Ctrl + A at boot up and find a disk check utility?  How would I run a hardware diagnostic on the drive?</description>
    <pubDate>Thu, 25 Jun 2009 18:41:02 GMT</pubDate>
    <dc:creator>mtroxel</dc:creator>
    <dc:date>2009-06-25T18:41:02Z</dc:date>
    <item>
      <title>Disk error code 33</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/disk-error-code-33/m-p/4447473#M142189</link>
      <description>I've taken over a Proliant ML 150 with two 136 Gig Compaq drives mirrored.  About once a day for the last year and a half, the Event Viewer logs a Error code 33 on HD 0.  It says "Data was recovered using error correction code on device \Device \Harddisk 0.  I never see the error for disk 1.  &lt;BR /&gt;&lt;BR /&gt;Is this just a file system problem?  Do I just hit Ctrl + A at boot up and find a disk check utility?  How would I run a hardware diagnostic on the drive?</description>
      <pubDate>Thu, 25 Jun 2009 18:41:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/disk-error-code-33/m-p/4447473#M142189</guid>
      <dc:creator>mtroxel</dc:creator>
      <dc:date>2009-06-25T18:41:02Z</dc:date>
    </item>
    <item>
      <title>Re: Disk error code 33</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/disk-error-code-33/m-p/6441042#M142213</link>
      <description>&lt;P&gt;Install HP utility to diagnostics issue :&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Array Configuration Utility&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A target="_blank" href="http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?cc=us&amp;amp;lc=en&amp;amp;dlc=en&amp;amp;tmp_geoLoc=true&amp;amp;softwareitem=MTX-311dda721cb5421eae2c422f7f"&gt;http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?cc=us&amp;amp;lc=en&amp;amp;dlc=en&amp;amp;tmp_geoLoc=true&amp;amp;softwareitem=MTX-311dda721cb5421eae2c422f7f&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A target="_blank" href="http://www.hp.com/ctg/Manual/c00709035.pdf"&gt;http://www.hp.com/ctg/Manual/c00709035.pdf&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 08 Apr 2014 15:31:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/disk-error-code-33/m-p/6441042#M142213</guid>
      <dc:creator>scharchouf</dc:creator>
      <dc:date>2014-04-08T15:31:50Z</dc:date>
    </item>
    <item>
      <title>Re: Disk error code 33</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/disk-error-code-33/m-p/6441064#M142214</link>
      <description>Not sure what generation your server is, but obviously it is not using a smart array controller, but a "normal" SATA controller, maybe using a driver based mirroring?&lt;BR /&gt;&lt;BR /&gt;The disk has probably defective areas, detected during write operations. If the disks are used. If you don't use RAID, you can probably test the disks with windows error checking?</description>
      <pubDate>Tue, 08 Apr 2014 15:41:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/disk-error-code-33/m-p/6441064#M142214</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2014-04-08T15:41:36Z</dc:date>
    </item>
  </channel>
</rss>

