<?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 MSA1000 RAID5 Parity problem in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/msa1000-raid5-parity-problem/m-p/3211196#M11328</link>
    <description>IÂ´m trying to create a volume with 7 disks of 146GB in a MSA1000 with only one controller with 256cache. &lt;BR /&gt;In the CLI, I see that the volume is initiating the parity and we are at a prox 15% of achievement, it goes back automatically to 0% and starts again the parity process. The ACU shows a warning message â  the I/O performance is degrading until the parity is completedâ  . &lt;BR /&gt;I left 24h the parity running and I keep having the same problem.&lt;BR /&gt;&lt;BR /&gt;Have you got any information that can help me to try to find the solution to this pr</description>
    <pubDate>Sat, 06 Mar 2004 03:09:47 GMT</pubDate>
    <dc:creator>martin Trullas</dc:creator>
    <dc:date>2004-03-06T03:09:47Z</dc:date>
    <item>
      <title>MSA1000 RAID5 Parity problem</title>
      <link>https://community.hpe.com/t5/disk-enclosures/msa1000-raid5-parity-problem/m-p/3211196#M11328</link>
      <description>IÂ´m trying to create a volume with 7 disks of 146GB in a MSA1000 with only one controller with 256cache. &lt;BR /&gt;In the CLI, I see that the volume is initiating the parity and we are at a prox 15% of achievement, it goes back automatically to 0% and starts again the parity process. The ACU shows a warning message â  the I/O performance is degrading until the parity is completedâ  . &lt;BR /&gt;I left 24h the parity running and I keep having the same problem.&lt;BR /&gt;&lt;BR /&gt;Have you got any information that can help me to try to find the solution to this pr</description>
      <pubDate>Sat, 06 Mar 2004 03:09:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/msa1000-raid5-parity-problem/m-p/3211196#M11328</guid>
      <dc:creator>martin Trullas</dc:creator>
      <dc:date>2004-03-06T03:09:47Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1000 RAID5 Parity problem</title>
      <link>https://community.hpe.com/t5/disk-enclosures/msa1000-raid5-parity-problem/m-p/3211197#M11329</link>
      <description>I have seen such a problem with disks that had an old firmware level and had to be upgraded. Please get in touch with your supplier or HP support.</description>
      <pubDate>Sat, 06 Mar 2004 05:51:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/msa1000-raid5-parity-problem/m-p/3211197#M11329</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2004-03-06T05:51:29Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1000 RAID5 Parity problem</title>
      <link>https://community.hpe.com/t5/disk-enclosures/msa1000-raid5-parity-problem/m-p/3211198#M11330</link>
      <description>Sorry I made a mistake and I write againg the reply in the other forum.&lt;BR /&gt;Here is the reply:&lt;BR /&gt;Before I tried with 7 disks of 146GB but now I have tried with another 10 disk of 72GB 15rpm we had in the same MSA100 and I had the same problem. The parity goes back automatically at aprox 30% of achievement. So IÂ´m really not sure if it is a problem of the disks. After what I have done is try with this 10 disks of 72GB 15rpm in another MSA1000 we had available and I get the same problem. &lt;BR /&gt;Both MSA1000 are actualized with the latest fireware 4.24. &lt;BR /&gt;So as you can see I can't find the real problem, if it its a disk, or a cabinet or a firmware problem.&lt;BR /&gt;Tomorrow morning I will call</description>
      <pubDate>Sun, 07 Mar 2004 06:28:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/msa1000-raid5-parity-problem/m-p/3211198#M11330</guid>
      <dc:creator>martin Trullas</dc:creator>
      <dc:date>2004-03-07T06:28:11Z</dc:date>
    </item>
  </channel>
</rss>

