Atomicboy22
Technical User
I have a thread a little bit down, however I thought I would start a new one as this is a seperate problem.
I have configured 2 160G drives in raid 0. Everything good. I tried to connect another 40G drive to ide1 (secondary, the primary ide, was inseted into the raid 0 ide slot, and I just left the secondry ide in ide 1, which only my cdrom was before, now I mastered the 40G and slaved the cdrom to the ide1). As soon as I did this, windows wouldn't boot on the raid 0 array, it would say an error has occurred, and would offer safe mode, normal, and a couple other options for booting, however slecting anyone of them would cause a reboot. I then went into the bios and set the secondary ide master to not detect, and it booted fine after that, and the 40G drive appears in windows (even though it's set as "not detect" in the bios), however I did a hdd test on it, and I'm only getting 3mbs on it, so something isn't right (understandably so).
Is this because there is still a boot record on the 40G, and it is looking to that before raid 0 array? My boot array is the raid 0 then cdrom then floppy, so it shouldn't even be a problem, but then again I don't really know how raid effects everything else, and it's obviosly effecting something when I have the bios detect this drive.
What should I do? I have it on there as my backup drive for important data, that I mirror from dir's in the raid 0 array, so it's kinda needed.
I have configured 2 160G drives in raid 0. Everything good. I tried to connect another 40G drive to ide1 (secondary, the primary ide, was inseted into the raid 0 ide slot, and I just left the secondry ide in ide 1, which only my cdrom was before, now I mastered the 40G and slaved the cdrom to the ide1). As soon as I did this, windows wouldn't boot on the raid 0 array, it would say an error has occurred, and would offer safe mode, normal, and a couple other options for booting, however slecting anyone of them would cause a reboot. I then went into the bios and set the secondary ide master to not detect, and it booted fine after that, and the 40G drive appears in windows (even though it's set as "not detect" in the bios), however I did a hdd test on it, and I'm only getting 3mbs on it, so something isn't right (understandably so).
Is this because there is still a boot record on the 40G, and it is looking to that before raid 0 array? My boot array is the raid 0 then cdrom then floppy, so it shouldn't even be a problem, but then again I don't really know how raid effects everything else, and it's obviosly effecting something when I have the bios detect this drive.
What should I do? I have it on there as my backup drive for important data, that I mirror from dir's in the raid 0 array, so it's kinda needed.