hi everyone: I was really hoping I wouldn't be one of the people posting here they lost their raid 0 array, but I did, as well as 1 of the drives 
Fortunately I am a back-up freak, so all is not lost. I was using 2 Raptors, about a month old, and started a DVD encoding session before going to bed last night.
Woke up to a BSOD- rebooted, and my raid bios said that one of the drives was damaged, or had an error ( something to that effect).
Went to the MB bios, and the faulty drive was no longer listed as a WD36.... , but was now listed as a WD200BB (WTF), and drive capacity was listed as -0- MB. Broke the array, tried fdisk, partition magic, etc, and all said the drive was not there. MB bios, during POST, said there was no fixed disc attached. Swapped SATA ports, as well as cables, same thing, so RMA time.
I had the pci bus locked at 33, so I was running the drives in spec. Now I am afraid to do any encoding after I get the new drive. Any reason this happened, other than a faulty drive?
(all 3 drives in my box have a 120 mm fan blowing directly through/ on them).
Fortunately I am a back-up freak, so all is not lost. I was using 2 Raptors, about a month old, and started a DVD encoding session before going to bed last night.
Woke up to a BSOD- rebooted, and my raid bios said that one of the drives was damaged, or had an error ( something to that effect).
Went to the MB bios, and the faulty drive was no longer listed as a WD36.... , but was now listed as a WD200BB (WTF), and drive capacity was listed as -0- MB. Broke the array, tried fdisk, partition magic, etc, and all said the drive was not there. MB bios, during POST, said there was no fixed disc attached. Swapped SATA ports, as well as cables, same thing, so RMA time.
I had the pci bus locked at 33, so I was running the drives in spec. Now I am afraid to do any encoding after I get the new drive. Any reason this happened, other than a faulty drive?
(all 3 drives in my box have a 120 mm fan blowing directly through/ on them).