<?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: Intel Chipset Raid - Why Bother in Graphics</title>
    <link>https://community.intel.com/t5/Graphics/Intel-Chipset-Raid-Why-Bother/m-p/232087#M3783</link>
    <description>&lt;P&gt;I am sorry I bothered you with the question. I am interested in determining if perhaps the issue is implementation by the motherboard vendors that is contributing to the issue.&lt;/P&gt;&lt;P&gt;It can but unlikely as Intel provides the RAID option ROM part that must be put in with the rest of the BIOS but having BIOS correctly access it right even after the RAID drivers take over is down to testing. There is a big number of setup types and drives to do that they likely do some and thats it and for how long for? Getting it right with testing and time is a lot of work and then its finding why it happened in the first place.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am not alone with issues regarding the Intel Raid - there are lots of threads about issues with the drivers / chipset. I am glad it is working for you. &lt;/P&gt;&lt;P&gt;If you ask the motherboard vendor what tests were done for RAID and then tell them to setup a RAID on such ports maybe not with the same drives to see if they get the same problems at their end.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The only problem I had with Intel RAID drivers was with Matrix Storage Manager 8.9.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;List of things if not down to Intel drivers or your motherboards BIOS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Faulty cables both power and data&lt;/P&gt;&lt;P&gt;Faulty PSU&lt;/P&gt;&lt;P&gt;Faulty motherboard either chip or connection link&lt;/P&gt;&lt;P&gt;Overheating&lt;/P&gt;&lt;P&gt;Faulty HDD or SSD&lt;/P&gt;&lt;P&gt;Overclocking&lt;/P&gt;&lt;P&gt;HDD's not suited for RAID&lt;/P&gt;&lt;P&gt;Having HDD's power down in idle mode failing to spin up in time.&lt;/P&gt;</description>
    <pubDate>Mon, 31 Jan 2011 00:47:01 GMT</pubDate>
    <dc:creator>idata</dc:creator>
    <dc:date>2011-01-31T00:47:01Z</dc:date>
    <item>
      <title>Intel Chipset Raid - Why Bother</title>
      <link>https://community.intel.com/t5/Graphics/Intel-Chipset-Raid-Why-Bother/m-p/232082#M3778</link>
      <description>&lt;P&gt;I am wondering why Intel even bothers to put RAID on the chipset. They seem incapable of releasing stable drivers. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a MSI Eclipse board and an EVGA X58 board. Both have 12 GB of Coursair memory, 920 processer, Windows 7 Ultimate X64, etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The MSI board is totally unstable with raid enabled (6 1 TB WD drives) Raid 5 with 4 drives resulted in continual drive failures being reported. I went back to Raid 1 - three sets of raid. I then experienced system freezes (everything stops for a minute or two) to total lockup. I totally broke the raid and reset the drives back to IDE - performance has returned and the lockups and freezes have gone.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The EVGA board has been much more stable, however, I get freezes with raid 5 and to a lessor amount with a reformat and setting up the drives as Raid 1. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I had in the past went back to the 8.6.2.1012 version of the drivers that seemed more stable. In the most recent reformat and reinstall of the os I put in the very latest version of the driver available from Intel - which continues the trend of instability.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Intel, why do you even bother if you cannot support the product that you designed by providing stable drivers. We pay a premium for these boards and expect them to work with the features that are included including your crappy RAID support. Please fix your drivers so that your components are usable.&lt;/P&gt;</description>
      <pubDate>Sat, 29 Jan 2011 15:01:35 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Intel-Chipset-Raid-Why-Bother/m-p/232082#M3778</guid>
      <dc:creator>CKels</dc:creator>
      <dc:date>2011-01-29T15:01:35Z</dc:date>
    </item>
    <item>
      <title>Re: Intel Chipset Raid - Why Bother</title>
      <link>https://community.intel.com/t5/Graphics/Intel-Chipset-Raid-Why-Bother/m-p/232083#M3779</link>
      <description>&lt;P&gt;Intel, why do you even bother if you cannot support the product that you designed by providing stable drivers. We pay a premium for these boards and expect them to work with the features that are included including your crappy RAID support. Please fix your drivers so that your components are usable.&lt;/P&gt;&lt;P&gt;If Intel RAID drivers as in RST 10.1.0.1008 are so unstable then why is it that I can run two RAID 5 arrays each with three drives in and stable?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is more to having a stable RAID then the drivers used to run them.&lt;/P&gt;</description>
      <pubDate>Sun, 30 Jan 2011 22:49:48 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Intel-Chipset-Raid-Why-Bother/m-p/232083#M3779</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2011-01-30T22:49:48Z</dc:date>
    </item>
    <item>
      <title>Re: Intel Chipset Raid - Why Bother</title>
      <link>https://community.intel.com/t5/Graphics/Intel-Chipset-Raid-Why-Bother/m-p/232084#M3780</link>
      <description>&lt;P&gt;Which motherboard are you using? I get stability with my EVGA X58 and my MSI EClipse board using driver version 8.6.2.1012. Issues with the disk being marked bad, lockups and freezes occur with later drivers - more so on the MSI board than the EVGA board. &lt;/P&gt;</description>
      <pubDate>Sun, 30 Jan 2011 22:56:27 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Intel-Chipset-Raid-Why-Bother/m-p/232084#M3780</guid>
      <dc:creator>CKels</dc:creator>
      <dc:date>2011-01-30T22:56:27Z</dc:date>
    </item>
    <item>
      <title>Re: Intel Chipset Raid - Why Bother</title>
      <link>https://community.intel.com/t5/Graphics/Intel-Chipset-Raid-Why-Bother/m-p/232085#M3781</link>
      <description>&lt;P&gt;Which motherboard are you using?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;GIGABYTE - GA-P55-UD4 should you really need to know.</description>
      <pubDate>Sun, 30 Jan 2011 23:11:25 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Intel-Chipset-Raid-Why-Bother/m-p/232085#M3781</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2011-01-30T23:11:25Z</dc:date>
    </item>
    <item>
      <title>Re: Intel Chipset Raid - Why Bother</title>
      <link>https://community.intel.com/t5/Graphics/Intel-Chipset-Raid-Why-Bother/m-p/232086#M3782</link>
      <description>&lt;P&gt;I am sorry I bothered you with the question. I am interested in determining if perhaps the issue is implementation by the motherboard vendors that is contributing to the issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am not alone with issues regarding the Intel Raid - there are lots of threads about issues with the drivers / chipset. I am glad it is working for you. &lt;/P&gt;</description>
      <pubDate>Sun, 30 Jan 2011 23:36:32 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Intel-Chipset-Raid-Why-Bother/m-p/232086#M3782</guid>
      <dc:creator>CKels</dc:creator>
      <dc:date>2011-01-30T23:36:32Z</dc:date>
    </item>
    <item>
      <title>Re: Intel Chipset Raid - Why Bother</title>
      <link>https://community.intel.com/t5/Graphics/Intel-Chipset-Raid-Why-Bother/m-p/232087#M3783</link>
      <description>&lt;P&gt;I am sorry I bothered you with the question. I am interested in determining if perhaps the issue is implementation by the motherboard vendors that is contributing to the issue.&lt;/P&gt;&lt;P&gt;It can but unlikely as Intel provides the RAID option ROM part that must be put in with the rest of the BIOS but having BIOS correctly access it right even after the RAID drivers take over is down to testing. There is a big number of setup types and drives to do that they likely do some and thats it and for how long for? Getting it right with testing and time is a lot of work and then its finding why it happened in the first place.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am not alone with issues regarding the Intel Raid - there are lots of threads about issues with the drivers / chipset. I am glad it is working for you. &lt;/P&gt;&lt;P&gt;If you ask the motherboard vendor what tests were done for RAID and then tell them to setup a RAID on such ports maybe not with the same drives to see if they get the same problems at their end.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The only problem I had with Intel RAID drivers was with Matrix Storage Manager 8.9.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;List of things if not down to Intel drivers or your motherboards BIOS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Faulty cables both power and data&lt;/P&gt;&lt;P&gt;Faulty PSU&lt;/P&gt;&lt;P&gt;Faulty motherboard either chip or connection link&lt;/P&gt;&lt;P&gt;Overheating&lt;/P&gt;&lt;P&gt;Faulty HDD or SSD&lt;/P&gt;&lt;P&gt;Overclocking&lt;/P&gt;&lt;P&gt;HDD's not suited for RAID&lt;/P&gt;&lt;P&gt;Having HDD's power down in idle mode failing to spin up in time.&lt;/P&gt;</description>
      <pubDate>Mon, 31 Jan 2011 00:47:01 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Intel-Chipset-Raid-Why-Bother/m-p/232087#M3783</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2011-01-31T00:47:01Z</dc:date>
    </item>
    <item>
      <title>Re: Intel Chipset Raid - Why Bother</title>
      <link>https://community.intel.com/t5/Graphics/Intel-Chipset-Raid-Why-Bother/m-p/232088#M3784</link>
      <description>&lt;P&gt;Thanks Peter.&lt;/P&gt;</description>
      <pubDate>Mon, 31 Jan 2011 01:04:51 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Intel-Chipset-Raid-Why-Bother/m-p/232088#M3784</guid>
      <dc:creator>CKels</dc:creator>
      <dc:date>2011-01-31T01:04:51Z</dc:date>
    </item>
  </channel>
</rss>

