- Jan 26, 2005
- 40
- 0
- 0
I have 2x200GB HDs in RAID1 on the SI chip, and I'm wondering if anybody can help me understand a problem I've been having, as the documentation provided is fairly useless.
Basically the fact is that, when XP shuts down improperly (last time it happened it was due to the IRQ_LESS_NOT_EQUAL in UT2003, since I had forgotten to disable NoExecute) the RAID boots up in a 'weird' state where it works properly *BUT* it's extremely slow (from 100-120MB/sec transfer down to 2-3, and over 30ms of seek).
If you load up the SATARAID5 utility the raid set will be 'yellow' (rather than green) and if you go in the info page it says that the raid is in a 'reduced' state (as opposed to 'online'). I haven't been able to find any documentation anywhere about this, and the only way to fix it seems to be to go in the bios, delete the raid set and recreate a RAID1 set with the same drives: this will re-copy the whole drive and things will be ok and fast again.
I am wondering if there is anything else I can do when this happens, as rebuilding the array every time (besides being scary) takes a few hours, and sometimes I even had to open the case and switch the ports around to let the utility let me do it. Some sort of 'checkdisk' program or something would be ideal.
Thanks in advance for any helpful information you might have.
Basically the fact is that, when XP shuts down improperly (last time it happened it was due to the IRQ_LESS_NOT_EQUAL in UT2003, since I had forgotten to disable NoExecute) the RAID boots up in a 'weird' state where it works properly *BUT* it's extremely slow (from 100-120MB/sec transfer down to 2-3, and over 30ms of seek).
If you load up the SATARAID5 utility the raid set will be 'yellow' (rather than green) and if you go in the info page it says that the raid is in a 'reduced' state (as opposed to 'online'). I haven't been able to find any documentation anywhere about this, and the only way to fix it seems to be to go in the bios, delete the raid set and recreate a RAID1 set with the same drives: this will re-copy the whole drive and things will be ok and fast again.
I am wondering if there is anything else I can do when this happens, as rebuilding the array every time (besides being scary) takes a few hours, and sometimes I even had to open the case and switch the ports around to let the utility let me do it. Some sort of 'checkdisk' program or something would be ideal.
Thanks in advance for any helpful information you might have.