Ok everyone,
I got it figured out!
It wasn't the ram, or a faulty controller.
It seems that when you build a pc, the bios numbers you're HDD's random. This number is written somewhere in the first 10 bits avalable on you're HDD. But as soon as you make a Raid configuration it numbers both HDD for that specific raid configuration the same becouse the bios and os wants to see the HDD together as one drive... Before you make a Raid configuration the HDDs need to have a different number. In my case I had my storage HDD as drive 0, and the raid configuration as 1. Somehow drive o is deeded in you're pc to boot at all, so when I removed the storge HDD it couldn't boot anymore. Also, both Caviar Blacks (raid0) had the same number, so on the same controller, wich was the marvell controller, it couldn't see one drives becouse they had the same number. That is why one drive only worked on the ICH10R chipset and the other worked on both....
By doing a complete drivesweep, wich sets all the bits to 0, both drives had the capability to have a new number. And this solved the problem. Now I could make a new raid configuration wich is now drive 0, so I don't have this problem anymore.
How it happend that my storage HDD became number 0 and my raid number 1 is unclear to me, becouse the OS drive is automaticaly set to drive 0 usually. But I guess it has to do with me having all my user files linked to the storage HDD.
Thanks everyone for they're suggestions and thinking!
DJ
I got it figured out!
It wasn't the ram, or a faulty controller.
It seems that when you build a pc, the bios numbers you're HDD's random. This number is written somewhere in the first 10 bits avalable on you're HDD. But as soon as you make a Raid configuration it numbers both HDD for that specific raid configuration the same becouse the bios and os wants to see the HDD together as one drive... Before you make a Raid configuration the HDDs need to have a different number. In my case I had my storage HDD as drive 0, and the raid configuration as 1. Somehow drive o is deeded in you're pc to boot at all, so when I removed the storge HDD it couldn't boot anymore. Also, both Caviar Blacks (raid0) had the same number, so on the same controller, wich was the marvell controller, it couldn't see one drives becouse they had the same number. That is why one drive only worked on the ICH10R chipset and the other worked on both....
By doing a complete drivesweep, wich sets all the bits to 0, both drives had the capability to have a new number. And this solved the problem. Now I could make a new raid configuration wich is now drive 0, so I don't have this problem anymore.
How it happend that my storage HDD became number 0 and my raid number 1 is unclear to me, becouse the OS drive is automaticaly set to drive 0 usually. But I guess it has to do with me having all my user files linked to the storage HDD.
Thanks everyone for they're suggestions and thinking!
DJ
