- May 21, 2001
- 2,952
- 0
- 0
I am running a 1.4 GHz T-Bird on an IWill KK266R with WinXP. I also have a Promise SX4000 RAID card that supports a 3x100GB RAID5 array. Two weeks ago, I developed a boot problem where XP would freeze about 20s after loaded, either at the login screen or once it started (assuming I logged in before it froze). I initially thought that this was a software problem and systematically removed programs from my startup. After several boot attempts with the same problem, CHKDSK started running with XP startup on each boot. Even if it would complete successfully, it would appear again on the next boot, even if I managed to shut down properly. Finally, one of my HDs on the RAID array went offline, followed by a second a few boots later. I ran the appropriate utilities to check the drives and all three passed with no errors from the extended test. I was also able to use the recovery console to run chkdsk on the partitions of the array, again with no errors. The array was not damaged and I was able to restore it simply by deleting the array and then recreating it in the config utility.
Using a second machine, I was able to boot normally off of the array, and there did not seem to be any problems. However, once I returned the RAID card to my original PC, it freezes while booting, usually right before the black and white XP startup bar appears. I also cannot boot into safe mode. I've removed all of my card besides my vid card and the RAID controller, but the problem is the same.
What am I looking at here? I tested the machine with different RAM and that had no effect. Did my mobo bite it or something? Thanks very much for any advice you have.
Using a second machine, I was able to boot normally off of the array, and there did not seem to be any problems. However, once I returned the RAID card to my original PC, it freezes while booting, usually right before the black and white XP startup bar appears. I also cannot boot into safe mode. I've removed all of my card besides my vid card and the RAID controller, but the problem is the same.
What am I looking at here? I tested the machine with different RAM and that had no effect. Did my mobo bite it or something? Thanks very much for any advice you have.
