<?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 msa1500cs &amp;quot;Consistency Check Failed&amp;quot; in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/msa1500cs-quot-consistency-check-failed-quot/m-p/4269460#M33073</link>
    <description>hi guys,&lt;BR /&gt;&lt;BR /&gt;On 13th (yeah, bad luck) a msa1500cs with a 6-disks sata raid6 array was connected through a qlogic hba with a proliant dl380 g4 and mounted as ext3 under rhel5.&lt;BR /&gt;&lt;BR /&gt;a cron script started which executed a mv command, then the kernel spitted this error:&lt;BR /&gt;&lt;BR /&gt;Sep 13 22:10:01 fileserver kernel: EXT3-fs warning (device dm-0): empty_dir: bad directory (dir #76219579) - no `.' or `..'&lt;BR /&gt;&lt;BR /&gt;following this, a lot more errors appeared in kernel log (see attached file) finally ending with a kernel panic this morning.&lt;BR /&gt;&lt;BR /&gt;ran hpaducli today and it says:&lt;BR /&gt;&lt;BR /&gt;Consolidated Error Report:&lt;BR /&gt;   Controller: MSA1500 CS in SGA0733024&lt;BR /&gt;       Device: Logical Drive 3&lt;BR /&gt;      Message: Parity Initialization Failed&lt;BR /&gt;   Controller: MSA1500 CS in SGA0733024&lt;BR /&gt;       Device: Logical Drive 4&lt;BR /&gt;      Message: Parity Initialization Failed&lt;BR /&gt;&lt;BR /&gt;however, neither disks nor controller shows any red light or unusual light activity. how can i troubleshoot further?&lt;BR /&gt;many thanks,&lt;BR /&gt;costin</description>
    <pubDate>Mon, 15 Sep 2008 12:38:27 GMT</pubDate>
    <dc:creator>costin gusa</dc:creator>
    <dc:date>2008-09-15T12:38:27Z</dc:date>
    <item>
      <title>msa1500cs "Consistency Check Failed"</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1500cs-quot-consistency-check-failed-quot/m-p/4269460#M33073</link>
      <description>hi guys,&lt;BR /&gt;&lt;BR /&gt;On 13th (yeah, bad luck) a msa1500cs with a 6-disks sata raid6 array was connected through a qlogic hba with a proliant dl380 g4 and mounted as ext3 under rhel5.&lt;BR /&gt;&lt;BR /&gt;a cron script started which executed a mv command, then the kernel spitted this error:&lt;BR /&gt;&lt;BR /&gt;Sep 13 22:10:01 fileserver kernel: EXT3-fs warning (device dm-0): empty_dir: bad directory (dir #76219579) - no `.' or `..'&lt;BR /&gt;&lt;BR /&gt;following this, a lot more errors appeared in kernel log (see attached file) finally ending with a kernel panic this morning.&lt;BR /&gt;&lt;BR /&gt;ran hpaducli today and it says:&lt;BR /&gt;&lt;BR /&gt;Consolidated Error Report:&lt;BR /&gt;   Controller: MSA1500 CS in SGA0733024&lt;BR /&gt;       Device: Logical Drive 3&lt;BR /&gt;      Message: Parity Initialization Failed&lt;BR /&gt;   Controller: MSA1500 CS in SGA0733024&lt;BR /&gt;       Device: Logical Drive 4&lt;BR /&gt;      Message: Parity Initialization Failed&lt;BR /&gt;&lt;BR /&gt;however, neither disks nor controller shows any red light or unusual light activity. how can i troubleshoot further?&lt;BR /&gt;many thanks,&lt;BR /&gt;costin</description>
      <pubDate>Mon, 15 Sep 2008 12:38:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1500cs-quot-consistency-check-failed-quot/m-p/4269460#M33073</guid>
      <dc:creator>costin gusa</dc:creator>
      <dc:date>2008-09-15T12:38:27Z</dc:date>
    </item>
    <item>
      <title>Re: msa1500cs "Consistency Check Failed"</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1500cs-quot-consistency-check-failed-quot/m-p/4269461#M33074</link>
      <description>ps: attached the hpaducli report</description>
      <pubDate>Mon, 15 Sep 2008 13:05:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1500cs-quot-consistency-check-failed-quot/m-p/4269461#M33074</guid>
      <dc:creator>costin gusa</dc:creator>
      <dc:date>2008-09-15T13:05:18Z</dc:date>
    </item>
    <item>
      <title>Re: msa1500cs "Consistency Check Failed"</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1500cs-quot-consistency-check-failed-quot/m-p/4269462#M33075</link>
      <description>Looks like a 'strip kill' has happened (those 13ths...). According to the ADU report, one disk drive has failed and others show issues, too, but I don't have the tools to analyze it easily and - I'm sorry, but I don't have time to decode the SCSI status information manually.&lt;BR /&gt;&lt;BR /&gt;I suggest you log a call with HP and let them take a look at the ADU report.</description>
      <pubDate>Mon, 15 Sep 2008 17:04:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1500cs-quot-consistency-check-failed-quot/m-p/4269462#M33075</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2008-09-15T17:04:44Z</dc:date>
    </item>
    <item>
      <title>Re: msa1500cs "Consistency Check Failed"</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1500cs-quot-consistency-check-failed-quot/m-p/4269463#M33076</link>
      <description>the failed one is in the local smart array controller - ignore it (&lt;A href="http://forums12.itrc.hp.com/service/forums/questionanswer.do?threadId=1245574)," target="_blank"&gt;http://forums12.itrc.hp.com/service/forums/questionanswer.do?threadId=1245574),&lt;/A&gt; it is safely running on spare drive.</description>
      <pubDate>Tue, 16 Sep 2008 06:49:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1500cs-quot-consistency-check-failed-quot/m-p/4269463#M33076</guid>
      <dc:creator>costin gusa</dc:creator>
      <dc:date>2008-09-16T06:49:24Z</dc:date>
    </item>
  </channel>
</rss>

