1 Reply Latest reply on Feb 13, 2012 12:38 PM by WelmoedJ

    Intel Matrix Storage Technology - Windows does not boot up




      we have about 5.000 HP rp5700 computers running Win XP spread out to many locations. All of them are running Intel Matrix Storage Technology with RAID 1 - Mirroring on two disks.

      The problem we have been facing for a long period is that very often PC is not able to boot up after reboot (mostly after powerloss).

      Usually there is an information about corrupted system files or just a black screen.

      To make boot up process possible user must disconnect one drive. Then PC is able to start. When the disk is connected again rebuilding process starts and system is running correctly. We have been trying with different Intel drivers but it does not help.


      Have you heard about similar problems?




        • 1. Re: Intel Matrix Storage Technology - Windows does not boot up

          Though not completely identically, I have reported similar behavior.

          The system here is and Intel based mainboard/CPU and W XP Home with RAID1.


          My problem is that on cold boot the first drive fails to be recognized every now and then (3 week interval) but still starts Windows XP.

          Thereupon it starts showing the "disks" and shows a failure of disk 2.

          I disabled the drive cacheing functions to see if that would solve the issue, but no result.


          The system log however only reports iastor0 (first drive) timing out (error IDs 9 and 7024).

          Yet the second drive is set to "failure".

          Testing th drives with the manufacturer's diagnostic tools never have shown a failure on either drive.

          I therefore presume it's either the driver or the management software that's causing these situations over and over.


          Did you check the system (evetually the application) logs?

          In the logs I also found repeated errors of the Windows Search function, so that could also be part of the problem.

          After "killing" the management software I have not yet seen a return of this error nor that of Search (each day sometimes all over the 3 weeks period!).

          But... recall the three weeks of proper functioning! So the issue perhaps is yet not resolved.


          Hopefully you'll find something here or through my error description.

          My other thread has probably been a waste of time as nobody seems to care to reply.