1 11 12 13 14 15 36 Previous Next 526 Replies Latest reply: Sep 15, 2012 7:30 AM by paludo Go to original post RSS
  • 180. Re: Random drive fails with new Matrix Storage Manager 8.9
    MrRatt Community Member
    Currently Being Moderated

    kau wrote:

     

    This problem has be resolved by updating the motherboad BIOS Intel RAID option ROM on a Asus P6T.  A user was able to replace the Intel Storage option rom 8.0.0.1038  that is present in the standard P6T 0603 BIOS with the 8.8.0.1009.  He was pretty certain that option rom 8.0.0.1038 had an issue with the version 8.9 of the Intel Matrix Storage Manager in Vista x64.

     

    If you want to use the new storage manager you'll either need to replace the option ROM yourself which will probably void your motherboard warranty and may cause other problems or request a BIOS update containing a newer option ROM from your motherboard manufacturer.  You can determine the option ROM version you have in the Intel Matrix Storage Console by going to Intel Matrix Storage Manager tab in the System Report in the View menu.

     

    Storage rom     Matrix Storage 
                    Manager on Vista x64
    8.0.0.1038      8.8                  OK
    8.0.0.1038      8.9                  Hangs on Vista boot progress screen
                                         able to use last known good
                                         configuration to revert back to 8.8
    8.8.0.1009      8.8                  OK
    8.8.0.1009      8.9                  OK

     

    As a user with the problem reported in this thread, I'd have to disagree. You have found a solution for another problem, but not the one described here..

     

    I haven't seen anyone else in this thread state that their system would not boot to Windows after installing the 8.9 drivers or app. The problem was that it would mark a working drive as having failed and force the arrays to be rebuilt over and over again..

     

    RAID Option ROM Version 8.9.0.1023 on my Intel DX58SO... If I use the 8.9 drivers, I have the problem described in this thread... My RAID arrays haven't rebuilt once since I "downgraded" to 8.8.

  • 181. Re: Random drive fails with new Matrix Storage Manager 8.9
    drive-me-nuts Community Member
    Currently Being Moderated

    I agree with JefUK about the red herring.  However, I advance an alternative hypothesis that may help explain why this problem continues to persist with no end in sight.

    I believe "Elizabeth" does not represent the best interests of Intel Corporation.  It may be possible she does not work for the company and is just a decoy or a ruse.  The rationale is simple:  Anyone within Intel who is aware of hundreds of software failures would (1) immediately report it to the programmers who originated it.  Such a notice is standard operating practice, and failure to do so could lead to termination from the company. Immediately upon notification, the Intel programming team would issue a patch and (2) release a beta test to those affected (all of us).  Note that neither (1) nor (2) has occurred.

     

    Replicating the problem on in-house machinery, or sending a problem machine to Intel Corporation is again irrelvant, the fact is the problem exists and any customer oriented industry would not care if an employee could or could not replicate the failure; the most relevant information is there are hundreds of customers with a problem that Intel must solve immediately.  It is a no-brainer to send a 8.9 patch with select lines of code deleted; such a test would be of minimal cost to Intel and generate goodwill among users most affected by Intel's failing software.

     

    So I suggest an alternative solution:  Contact Intel at the highest levels, starting with CEO Paul Otellini.  Send email with a URL reference to this very string to each member of the Board of Directors.  Politely point out this persistent and pervasive problem will affect public perception of Intel and our future desire to buy intel products or invest as Intel shareholders.  In this manner the problem will be solved immediately.

    http://www.intel.com/pressroom/kits/bios/Otellini.htm

  • 182. Re: Random drive fails with new Matrix Storage Manager 8.9
    drive-me-nuts Community Member
    Currently Being Moderated

    These are the individuals that we must contact to solve this problem.  Please post email addresses if you find them.

     

  • 183. Re: Random drive fails with new Matrix Storage Manager 8.9
    chriskeeble Community Member
    Currently Being Moderated

    @drive-me-nuts:  Your post is exactly the sort of thing that promotes larger corprations to be ultra-cautious and even defensive when doing anything relating to releasing software / driver updates, or even discussing the issue with the larger community.

     

    I am quite possibly as unhappy about the situation as you are, but I do know from discussions with people inside Intel that they are looking at the problem, and Elizabeth has explained what they have done, and indeed already done, about the problem. Read up in the thread to find out.

     

    While it may not be what you would do, or it may not be happening as fast as you would do it, they are at least addressing the problem, and discussing it with us all.

     

    Abridged version of the above = Wind your neck in.

     

  • 184. Re: Random drive fails with new Matrix Storage Manager 8.9
    drive-me-nuts Community Member
    Currently Being Moderated

    Hello Chriskeeble:

    Is ultra-cautious good or bad?  Who cares if Intel is looking at the problem?  The only thing that matters is that Intel either fixes the problem or removes the defective 8.9 software from their website, as hundreds or perhaps thousands of people are losing their hard earned data or trashing perfectly good hard drives because of Intel's incompetence.

     

    You make a very good point, we should be contacting attorneys to initiate a class action lawsuit.

     

    Corporate Mailing Address

    2200 Mission College Blvd.
    Santa Clara, CA 95054-1549
    USA
                  (408) 765-8080         (408) 765-8080
  • 185. Re: Random drive fails with new Matrix Storage Manager 8.9
    w00thisButtonDo Community Member
    Currently Being Moderated

    It is just little "help" from intel to hard drive manufacturers. Crisis

  • 186. Re: Random drive fails with new Matrix Storage Manager 8.9
    Grendel Community Member
    Currently Being Moderated

    drive-me-nuts wrote:

     

    > I believe "Elizabeth" does not represent the best interests of Intel Corporation. It may be

    > possible she does not work for the company and is just a decoy or a ruse. The rationale

    > is simple: [..]
    > So I suggest an alternative solution: Contact Intel at the highest levels, starting with CEO

    > Paul Otellini.

     

    Right, that will just **** off the engineers working on that problem, I bet they are under a lot of pressure already. Let me assure you that Elizabeth is real and does indeed work for Intel, at an Intel facility.

     

    Someone mentioned earlier that the option ROM may cause the problem, I disagree. The ROM code is only used to create a RAID array/volume (basically writing a sector or two to the disks that describe the layout) and to boot the OS until the driver gets loaded. The driver will then completely take over the hardware, no more ROM code involved. It could be possible that newer option ROMs write extended data blocks when creating the array, I doubt that tho.

     

    As for Intel creating an instrumented version of the driver -- 50/50 chance that this will help since the driver won't be the same anymore. Plus, in order to make use of an instrumented version one most likely has to install the debug build of the OS which, again, will considerably change the outcome. Which, BTW, may be the reason for Intel having a hard time to reproduce the problem.

  • 187. Re: Random drive fails with new Matrix Storage Manager 8.9
    JefBelgium Community Member
    Currently Being Moderated

    Hi,

    Just wanted to add my pain here.

     

    Bought a new system about 2 months ago.

    Mobo: Intel DX58SO
    Processor: Intel Core i7 950
    Memory: Corsair CM3X2G1333C9 3 X 2GB
    4 HD Samsung HD322HJ Drives in RAID 10 configuration
    WINDOWS XP Pro

    System runs 24/7.

     

    I assembled the system and installed windows xp with the 8.9 driver. The next day when I came to work, I saw the "drive failed" and "degraded volume" messages. The system had been running over night.

    In the system log I saw a lot of these: "The device, \Device\Ide\iaStor0, did not respond within the timeout period".

     

    I rebuild the array and it reported OK. Next day, the same thing. It was the same drive so I thought maybe the disk was not ok. Since I luckily happend to have another one I switched it. Rebuild.

     

    The next morning, same sh*t. And this time a different drive drive.

    Out of desparation, I actually contacted Intel through chat support, but of course, it was like chatting with a donkey (what was I thinking). Started searching the web and intel's support site, and I came across JefUK's posts.

     

    Downgraded to 8.8. Have not had a single problem since.

     

    Don't know what I would have done if I didn't come across JefUk's posts.

    And how "intel" is not able to replicate the problem after all this time is beyond me.

     

    Jef

  • 188. Re: Random drive fails with new Matrix Storage Manager 8.9
    albundy118 Community Member
    Currently Being Moderated

    Hi,

     

    just for the statistics I've also the same mentioned Issues. 2x failed in 2 weeks and always waiting 3-4 days untils rebuild was done :-(

    My setup:

     

    ASUS - P6T V2 Deluxe

    Intel i7 920

    ICH10R - Raid 5 ( 5x Seagate 7200.11 - 1,5 TB)

    Windows 7 x64 Pro

    Intel Matrix 8.9 1023 ( 2x failed HD was marked)

     

    I've downgraded to 8.8 although Windows 7 isn't on supported OS but so far no problems. Rebuilding is still in progress... If v.8.8 will also give a failed HD I will post it to here.

     

    Let's hope there is already enough pressure @ Intel that they take it serious!

     

    BR

    Florian

  • 189. Re: Random drive fails with new Matrix Storage Manager 8.9
    Island88 Community Member
    Currently Being Moderated

    I like to say I seem to have the same issue as the rest of you, except it happens with 8.6

     

    This is my current setup:

    Asus P6T, AMI Bios version 0707 (updated a little over a week ago to this Bios)
    Intel Core I7 920, rev. D0, 2.67GHZ
    X58 Tylersburg, ICH10R
    3x2 GB Corsair XMS3 CM3X2G1600C8 8-8-8-24
    2xWD Cavier Black WD6401AALS, 640GB, 7200rpm, 32MB, SataII (Raid0)
    1xMaxtor DiamondMax 22, 1000GB, 7200rpm, 32MB, SataII

    OS: 2xXPpro x86, 1xVista x86

     

    The first time it ever happend was while I was browsing the internet with FireFox. The computer froze but the clock on my G15 was still running. It ended with a BSOD. The controller reported that the first drive of the array had an error. I deleted the array, created a new array, restored the backup and all was fine until the next time. Again using FF and this time I looked at the eventviewer to find out that IaStore timed out. I made a post on Tweakers.nl (Dutch). The funny thing was, that even though drive0 had and error, the computer would still work flawlessly, although as generation1 (drive0). Do note that, after the second time, I did a full HD scan with the Western Digital diagnostic tool and both drives came out clean.

     

    I since then placed the drives on different ports.

     

    Yesterday I came upon this forum and read all the 13 pages. I updated to 8.7 as it seemed a safe bet. Today, when I started the computer and booted into WinXP x86 the drive led stayed on for quite a while without anything happening, this is a sign of trouble. However, after a couple of minutes the computer seemed fine as the light went off. Later on I decided to see if the 'wait' was in the EventViewer and to my suprise, it was. At 6:06pm and 6:08pm I got the IaStore message, however, the system did not fail. I guess that is quite an improvement.

     

    With 8.6 I had the idea that the Array problems happend about once a week. In the weekend this computer is mostly on. During the week it only runs in the evening for about 6 to 8 hours. As noted, since yesterday late (or really this morning early) I'm on 8.7.

     

    Not sure if this means anything but I also wanted to write it off my chest as it bothers me a lot. I have already spend so much time with this HD issue that I'm ready to go out and buy a proper controller. However, money is an issue here.

     

    Thank you for reading.

  • 190. Re: Random drive fails with new Matrix Storage Manager 8.9
    Zbig Community Member
    Currently Being Moderated

    Just out of curiosity, question to the users experiencing this problem: are your systems configured to use a swap file located on the failing array? As I've wrote in another thread, I'm experiencing verification errors on the RAID1 mirrored array using Windows 7. After some investigation I've found out that most probably (I have to perform some more checks yet) these inconsitencies happen within the area used by the Windows pagefile. As a matter of fact, I'm experiencing this issue on the IMSM v8.8 too, but maybe this is somehow related? Maybe that's the similar error, but It's more critical on RAID5 while the discrepancy gets caught and considered a drive failure? Have someone experienced the false drive failure while not using RAID5-hosted swap file - located on another physical drive or disabled altogether?

  • 191. Re: Random drive fails with new Matrix Storage Manager 8.9
    MrRatt Community Member
    Currently Being Moderated

    Zbig -- I have two RAID arrays which have both shown the symptoms described here... C (320gb drives in RAID1) and D (1.5tb drives in RAID1). C is the OS drive and contains the page file/swap file/temp folders etc... Both arrays were failing randomly, although D failed more often. I remember at least one time when I did a Test & Verify I obtained errors, but I'm not sure anymore whether that was on the C or D array, or if it was prior to my latest reload of Windows Vista Ultimate x64.

  • 192. Re: Random drive fails with new Matrix Storage Manager 8.9
    oattes Community Member
    Currently Being Moderated

    I am also seeing the behaviour described in this thread. I experienced degraded RAID events every few days throughout a one month period with 8.9. Since falling back to 8.8, the raid arrays have been rock solid for 6 weeks. Here is the system report -- hope it helps in hunting this one down. If any more system detail is needed, I would be happy to provide it.

     

    System Information

    Kit Installed: 8.8.0.1009
    Kit Install History: 8.8.0.1009, Uninstall
    Shell Version: 8.8.0.1009

    OS Name: Microsoft® Windows Vista™ Ultimate
    OS Version: 6.0.6002 Service Pack 2 Build 6002
    System Name: HOMEPC
    System Manufacturer: Intel Corporation
    System Model: DG965WH
    Processor: Intel(R) Core(TM)2 CPU          6600  @ 2.40GHz
    BIOS Version/Date: Intel Corp. MQ96510J.86A.1751.2008.0811.0002, 08/11/2008

    Language: ENU

     

    Intel(R) Matrix Storage Manager

    Intel RAID Controller: Intel(R) ICH8R/ICH9R/ICH10R SATA RAID Controller
    Number of Serial ATA ports: 6

    RAID Option ROM Version: 6.1.0.1002
    Driver Version: 8.8.0.1009
    RAID Plug-In Version: 8.8.0.1009
    Language Resource Version of the RAID Plug-In: 8.8.0.1009
    Create Volume Wizard Version: 8.8.0.1009
    Language Resource Version of the Create Volume Wizard: 8.8.0.1009
    Create Volume from Existing Hard Drive Wizard Version: 8.8.0.1009
    Language Resource Version of the Create Volume from Existing Hard Drive Wizard: 8.8.0.1009
    Modify Volume Wizard Version: 8.8.0.1009
    Language Resource Version of the Modify Volume Wizard: 8.8.0.1009
    Delete Volume Wizard Version: 8.8.0.1009
    Language Resource Version of the Delete Volume Wizard: 8.8.0.1009
    ISDI Library Version: 8.8.0.1009
    Event Monitor User Notification Tool Version: 8.8.0.1009
    Language Resource Version of the Event Monitor User Notification Tool: 8.8.0.1009
    Event Monitor Version: 8.8.0.1009

    Array_0000
    Status: No active migrations
    Hard Drive Data Cache Enabled: No
    Size: 596.1 GB
    Free Space: 0 GB
    Number of Hard Drives: 2
    Hard Drive Member 1: ST3320620AS
    Hard Drive Member 2: ST3320620AS
    Number of Volumes: 1
    Volume Member 1: RAID640

    Array_0001
    Status: No active migrations
    Hard Drive Data Cache Enabled: Yes
    Size: 1863 GB
    Free Space: 0 GB
    Number of Hard Drives: 4
    Hard Drive Member 1: ST3500630AS
    Hard Drive Member 2: ST3500630AS
    Hard Drive Member 3: WDC WD5000AAKS-00A7B0
    Hard Drive Member 4: WDC WD5000AAKS-00A7B0
    Number of Volumes: 1
    Volume Member 1: RAID2000

    RAID640
    Status: Normal
    System Volume: Yes
    Volume Write-Back Cache Enabled: Yes
    RAID Level: RAID 0 (striping)
    Strip Size: 128 KB
    Size: 596.1 GB
    Physical Sector Size: 512 Bytes
    Logical Sector Size: 512 Bytes
    Number of Hard Drives: 2
    Hard Drive Member 1: ST3320620AS
    Hard Drive Member 2: ST3320620AS
    Parent Array: Array_0000

    RAID2000
    Status: Normal
    System Volume: No
    Volume Write-Back Cache Enabled: Yes
    RAID Level: RAID 5 (striping with parity)
    Strip Size: 128 KB
    Size: 1397.2 GB
    Physical Sector Size: 512 Bytes
    Logical Sector Size: 512 Bytes
    Number of Hard Drives: 4
    Hard Drive Member 1: ST3500630AS
    Hard Drive Member 2: ST3500630AS
    Hard Drive Member 3: WDC WD5000AAKS-00A7B0
    Hard Drive Member 4: WDC WD5000AAKS-00A7B0
    Parent Array: Array_0001

    Hard Drive 0
    Usage: Array member
    Status: Normal
    Device Port: 0
    Device Port Location: Internal
    Current Serial ATA Transfer Mode: Generation 2
    Model: ST3320620AS
    Serial Number: 3QF0JHWC
    Firmware: 3.AAE
    Native Command Queuing Support: Yes
    Hard Drive Data Cache Enabled: No
    Size: 298 GB
    Physical Sector Size: 512 Bytes
    Logical Sector Size: 512 Bytes
    Number of Volumes: 1
    Volume Member 1: RAID640
    Parent Array: Array_0000

    Hard Drive 1
    Usage: Array member
    Status: Normal
    Device Port: 1
    Device Port Location: Internal
    Current Serial ATA Transfer Mode: Generation 2
    Model: ST3320620AS
    Serial Number: 3QF0MSQE
    Firmware: 3.AAE
    Native Command Queuing Support: Yes
    Hard Drive Data Cache Enabled: No
    Size: 298 GB
    Physical Sector Size: 512 Bytes
    Logical Sector Size: 512 Bytes
    Number of Volumes: 1
    Volume Member 1: RAID640
    Parent Array: Array_0000

    Hard Drive 2
    Usage: Array member
    Status: Normal
    Device Port: 2
    Device Port Location: Internal
    Current Serial ATA Transfer Mode: Generation 2
    Model: ST3500630AS
    Serial Number: 5QG08XNJ
    Firmware: 3.AAE
    Native Command Queuing Support: Yes
    Hard Drive Data Cache Enabled: Yes
    Size: 465.7 GB
    Physical Sector Size: 512 Bytes
    Logical Sector Size: 512 Bytes
    Number of Volumes: 1
    Volume Member 1: RAID2000
    Parent Array: Array_0001

    Hard Drive 3
    Usage: Array member
    Status: Normal
    Device Port: 3
    Device Port Location: Internal
    Current Serial ATA Transfer Mode: Generation 2
    Model: ST3500630AS
    Serial Number: 5QG08YCW
    Firmware: 3.AAE
    Native Command Queuing Support: Yes
    Hard Drive Data Cache Enabled: Yes
    Size: 465.7 GB
    Physical Sector Size: 512 Bytes
    Logical Sector Size: 512 Bytes
    Number of Volumes: 1
    Volume Member 1: RAID2000
    Parent Array: Array_0001

    Hard Drive 4
    Usage: Array member
    Status: Normal
    Device Port: 4
    Device Port Location: Internal
    Current Serial ATA Transfer Mode: Generation 2
    Model: WDC WD5000AAKS-00A7B0
    Serial Number: WD-WMASY0200786
    Firmware: 01.03B01
    Native Command Queuing Support: Yes
    Hard Drive Data Cache Enabled: Yes
    Size: 465.7 GB
    Physical Sector Size: 512 Bytes
    Logical Sector Size: 512 Bytes
    Number of Volumes: 1
    Volume Member 1: RAID2000
    Parent Array: Array_0001

    Hard Drive 5
    Usage: Array member
    Status: Normal
    Device Port: 5
    Device Port Location: Internal
    Current Serial ATA Transfer Mode: Generation 2
    Model: WDC WD5000AAKS-00A7B0
    Serial Number: WD-WMASY0255169
    Firmware: 01.03B01
    Native Command Queuing Support: Yes
    Hard Drive Data Cache Enabled: Yes
    Size: 465.7 GB
    Physical Sector Size: 512 Bytes
    Logical Sector Size: 512 Bytes
    Number of Volumes: 1
    Volume Member 1: RAID2000
    Parent Array: Array_0001

  • 193. Re: Random drive fails with new Matrix Storage Manager 8.9
    w00thisButtonDo Community Member
    Currently Being Moderated

    I don't think you have same issue as thread started. Looks like it is memory or other hardware related issue or maybe MSM 8.6 was too buggy only for ICH10R. You can analyze your dump files if they are, to get more information. Just let it work a couple weeks, before report "same issue"

  • 194. Re: Random drive fails with new Matrix Storage Manager 8.9
    Elizabeth Community Member
    Currently Being Moderated

    @gpinzone: thanks for adding your details! appreciate it.

     

    @kau: thanks for the info about the option ROM. That is interesting. One user much earlier in the thread also commented that updating the BIOS/option ROM resolved the issue for them, except they downgraded to an older revision of the option ROM. As you mentioned, the option ROMs are specific to a platform. I can get more details on what platform v8.0 is intended for (I am a bit fuzzy on the 8.x versions - I actually thought 8.0 was the OROM that supported Intel(R) ICH9M, in which case it wouldn't work on any other platform - hence the reason I need to check versions). But @Grendel is right in that the option ROM is not in play when Windows is loaded which is when (I think) everyone is experiencing the issue, so it doesn't seem to make sense to me that it would help. Will think on that ..

     

    @Grendel: no one's installed of debug versions of the driver or OS. They wouldn't help until we find a system that shows the issue and might make it harder to actually see it - that's why it's not done.

     

     

     

    Anyway, we still continue to install v8.8/v8.9 on systems, trying to find one that will show the issue so we can debug it .. but the one thing that did occur to me is a common difference between all of your systems and ours is that we all just install v8.8 and then upgrade, while you've all been using v8.8 (or another version) for a longer period of time before upgrading. While I cannot think of a reason why that would matter in trying to replicate it, I figured I'd try anyway .. so I set up a system at my desk that I am letting sit with v8.8 for a few days before upgrading to see if it helps. Not at all sure why it would, but it certainly can't hurt.

1 11 12 13 14 15 36 Previous Next