I fogot one thing, I also get the following error in the system event viewer,
Event 9, iaStor. The device, \Device\Ide\iaStor0, did not respond within the timeout period.
Hello there yes Intel can't work out (or say) what the problem is and so here's what you need to do...install Matrix Storage Manager version 8.8 which works fine in Windows 7 32/64 bit but not supported by Intel.
Hi PeterUK and thank you for your reply. I when through the thread you posted and it appears you had the exact problem I'm now experiencing and many others. I'm surprised the thread did not so when I did a search on this forum. I have downloaded the older 8.8 driver but I have a question. The RAID5 array is still rebuilding, I'm guessing I should wait until the rebuild is complete before I install and roll back to 8.8? Or can I go ahead and run the 8.8 installer and roll it back? Thank you for help.
1 of 1 people found this helpful
You don't have to wait and in the many times I went from 8.9 to 8.8 (both driver and manager) and back trying to work out what the problem was I did as it was rebuilding and rarely a BSOD happens but it didn't cause any problems when it did. The best thing to do after is to run a verification and repair.
PeterUK you are the man! I have been wrestling with this fileserver for days and it is driving me nuts. Exact same problems except RAID 10. I will give this a try and see what happens. This has caused all kinds of issues and made this and last week a living hell. It has set back my work and caused me to order a 3 new hard drives that weren't needed.
Alternatively you could schedule a restart nightly. That allowed me to limp along for about a month. Kept the drives from failing and computer from freezing after iastor timeouts.
@Intel: This was a really bad experience. I'd love it if I could find this information before I plan a build, not after. I planned this build assuming the Intel RAID would work. I don't have $500 for a RAID card right now. I undertand MSM is free and all - I expected lower performance/reliability from MSM, but not at this level.
I rolled back to the 184.108.40.2069 with no problem so far. Now I'm just waiting for the array to rebuild it says 241hrs, then hopefully no more problems.
Hello and thank you. I had the same problem this last summer, under vistax64. It was really painfull, and made me buy an other 2To hard drive to use a raid 10 solution, with a much more faster rebuild time, but the same issue.
At last, Windows Sevenx64 WITHOUT intels drivers solved my problems for months.
Last week, i tried to migrate my 4*2To Raid 10 to a 4*2To Raid5, so, i installed the 8.9 driver. During the two days migration, i had a error on a drive. I put the midration to the end, and after, run the rebuild procedure.
there's about 60 hours left for rebuildind, should'I change my driver first? Is it a good idea to wait the end of the reconstruction, and the to remove the intel driver after?
At last, even after a reboot, my raid disk is still recognised as a 4To one. I was hoping for a 6To one. Of course i looked in the "hard disk administration"'s window. (I'm not sure for this translation of the french "gestion des disques"). I hope that after the rebuild operation, there will have 6To avaible, so i wait.
I ask you, please, please, please, to answer my questions. I hope my "solution" : "no intel driver at all" will help someone. If you don't undestand my english, please, be kind and ask me to reformulate.
Best regards, Horzab.
Thanks to you, PeterUK, i tried a new intel software, the 9.5 version. Rebuilding took 5 hours, instead à 83, and gave me a good hope in future.
Unfortunatly, two problems remain :
1- My 4*2To-Raid10 to 4*2To-Raid5 migration show me , as expected a 2To free space is show in the intel raid manager. I tried to expand the first raid drive to a 6To one, and get an error message. I have 4Go of free memory, and i log in with an administrator account, so, all the help solutions don't help. I reboot, same error. i create a new volume of 2To : It works. It works, but i don't want of it.
2- i had my first audio sluttering with my PC. ((on since 9 month), It's a troubleshooting know in this forum with the 9.5 version.
I'll try to change the version of intel matrix storage, if it work, I'll put the solution on this board.
If someone has a solution, i take it.
Thank you for your reading.
once again, i'm back.
I tried 8.8,
once again, i'm back.
I tried 8.8, 9.4, with no result => impossible to extend my 4To disk to a 6To one. It's not the first subject of this post, so, I'm about to make a new subject. If you read this post, and have an idea, you still can answer
Thank you, hypothetical reader.
9.4, with no result => impossible to extend my 4To disk to a 6To one. It's not the first subject of this post, so, I'm about to make a new subject. If you read this post, and have an idea, you still can answer
Thank you, hypothetical reader.
I also got this random fail drive problem with Intel® Matrix Storage Manager version 8.9.
I read the article in this forum as well as this official note from Intel: http://www.intel.com/support/chipsets/imsm/sb/CS-030818.htm, and it mentioned that I can either try 8.8 or Intel® Rapid Storage Technology version 9.5. However i cannot find any link in intel website that can download 9.5!
Some people suggestion to goggle it, but I would prefer to get it from the official site. It is amazing that the document from Intel mention about a software that doesn't exist on its own website.
Any one manage find a link from Intel? I am using Win7 64bit.
Not sure where you might find some official documentation on this but the "green" drives are generally not supported within RAID systems. The error correction that they employ can cause them to "hang" for long periods (30 sec?) and most RAID systems will mark this as a failed drive. I think you will find info on the drive maker's sites (Samsung, Seagate, WD). Not really an Intel issue.
It is an Intel issue, I rolled back to the older driver just like PeterUK suggested and bingo no more problems. I also received a reply from an email I sent to Intel support recommending that I also rollback the driver because it is a know issue. Also Intel has posted it in their knowledge base see the linkthat PeterUK put in his original reply to me. Roll back the driver, problem solved.
Glad you were able to solve your issue.