Hi,
I just resolved an annoying problem and I thought I'd share the solution in case it affects others.
I built a new E6600 system using DFI's Infinity 975X/G board. I plugged in three HDDs drives into SATA interfaces #1-3. The 1st two drives were brand-new Samsung HD080HJ drives, the 3rd was a Seagate 7200.7 with all of my files and documents. I set up RAID-0 on the two Samsung drives and proceeded to install XP SP2 Home Upgrade. No problem installing the ICH7R RAID drivers, partitioned and formatted the RAID volume, and had no problem with the install copying the files onto the volume. However, after the reboot, the PC would not boot. I kept getting "Disk Read Error. Press CTRL-ALT-DELETE to restart.".
I tried everything, updated BIOS, latest RAID drivers from DFI and Intel, tested the HDDs with Samsung's HUTIL, couldn't find a problem. Then I disconnected the Seagate drive and the problem was solved. No problem after the reboot and XP was fully installed. I reconnected the 3rd drive and all seems well.
Any idea why this happened, and perhaps who I should inform if this is a bug? I'm really not sure if this is a DFI, Intel, or Microsoft problem.
Cheers,
erikt
I just resolved an annoying problem and I thought I'd share the solution in case it affects others.
I built a new E6600 system using DFI's Infinity 975X/G board. I plugged in three HDDs drives into SATA interfaces #1-3. The 1st two drives were brand-new Samsung HD080HJ drives, the 3rd was a Seagate 7200.7 with all of my files and documents. I set up RAID-0 on the two Samsung drives and proceeded to install XP SP2 Home Upgrade. No problem installing the ICH7R RAID drivers, partitioned and formatted the RAID volume, and had no problem with the install copying the files onto the volume. However, after the reboot, the PC would not boot. I kept getting "Disk Read Error. Press CTRL-ALT-DELETE to restart.".
I tried everything, updated BIOS, latest RAID drivers from DFI and Intel, tested the HDDs with Samsung's HUTIL, couldn't find a problem. Then I disconnected the Seagate drive and the problem was solved. No problem after the reboot and XP was fully installed. I reconnected the 3rd drive and all seems well.
Any idea why this happened, and perhaps who I should inform if this is a bug? I'm really not sure if this is a DFI, Intel, or Microsoft problem.
Cheers,
erikt
Facebook
Twitter