New drive on raid connector doesn't work

gultekin · 03-08-2005, 04:29 PM

I had a 40gb disk running on MSI KT266 pro ru. It has been connected to one of the raid channels (IDE3) and was running fine. Of course being only one HDD it is not really raid but Promise sees it as raid. I used to be able to install xp normally.

I recently bought an Barracuda 160gb HDD and I wnated to do the same. I wanted to connect both drives to IDE3 and IDE4 on Raid and work as seperate HDDS but still see them in XP. What happens is that even though I connect new drive on its own and i creates a default array automatically as it used to be, whan I try to install XP, installation does not see the drive.
I thought drive is not working but if I connect it to normal IDE channel it works ok, I even partitioned it in Disk Manager of XP. But once it is fitted to one of the raid IDE, nothing sees it. The old one continues to work and I boot from it.

Please I just need help I don't have space left to do my work, and if possible I want to use it on raid IDe connectors so I don't need to put one of the CD drives as slave. Or if you think another configuration will work better I wouldlike to hear it.

Thanks.

gultekin · 03-08-2005, 07:53 PM

It is really weird. The old drive works fine on raid and I used to use the same Promise driver when I was installing xp. What I realised that if one drive is connected to normal ide and other to raid ide and if I boot from normal ide, xp do not see the one on raid ide. Ok May be I do not need to use Raid but I am still confused why the new drive does not work on its own as the old one on raid? Why I can not install XP? Can it be that either BIOS or promise driver does not support 160GB? But Bios is updated so does promise drivers...
All the weird things find me. I mastered the raid but my problem exceeds that.

Also, if I use the new drive as normal Primary master and the old one as primary slave the performance is sooo poor. Is there any way to connect both, use the bigger one as OS drive and the other as storage or backup but still run a fast drive? Don't forget that I have also 2 CD roms...

Thanks again and again for listening me...

crazijoe · 03-10-2005, 05:27 AM

Connect your 2 CD ROM drives to secondary master slave. Connect you 160GB HDD to primary master and connect you 40GB HDD to primary master on the RAID controller. Make sure you boot sequence is correct. Make sure after you install the OS that you install the MB chipset drivers and the RAID controller drivers. Also make sure you set the jumpers correctly on the drives. DO NOT use CS (cable select).

03-08-2005, 04:29 PM	#1 (permalink)
gultekin Registered User Join Date: Mar 2005 Posts: 4 OS: XP	New drive on raid connector doesn't work I had a 40gb disk running on MSI KT266 pro ru. It has been connected to one of the raid channels (IDE3) and was running fine. Of course being only one HDD it is not really raid but Promise sees it as raid. I used to be able to install xp normally. I recently bought an Barracuda 160gb HDD and I wnated to do the same. I wanted to connect both drives to IDE3 and IDE4 on Raid and work as seperate HDDS but still see them in XP. What happens is that even though I connect new drive on its own and i creates a default array automatically as it used to be, whan I try to install XP, installation does not see the drive. I thought drive is not working but if I connect it to normal IDE channel it works ok, I even partitioned it in Disk Manager of XP. But once it is fitted to one of the raid IDE, nothing sees it. The old one continues to work and I boot from it. Please I just need help I don't have space left to do my work, and if possible I want to use it on raid IDe connectors so I don't need to put one of the CD drives as slave. Or if you think another configuration will work better I wouldlike to hear it. Thanks.

03-08-2005, 07:53 PM	#2 (permalink)
gultekin Registered User Join Date: Mar 2005 Posts: 4 OS: XP	continue: It is really weird. The old drive works fine on raid and I used to use the same Promise driver when I was installing xp. What I realised that if one drive is connected to normal ide and other to raid ide and if I boot from normal ide, xp do not see the one on raid ide. Ok May be I do not need to use Raid but I am still confused why the new drive does not work on its own as the old one on raid? Why I can not install XP? Can it be that either BIOS or promise driver does not support 160GB? But Bios is updated so does promise drivers... All the weird things find me. I mastered the raid but my problem exceeds that. Also, if I use the new drive as normal Primary master and the old one as primary slave the performance is sooo poor. Is there any way to connect both, use the bigger one as OS drive and the other as storage or backup but still run a fast drive? Don't forget that I have also 2 CD roms... Thanks again and again for listening me...

03-10-2005, 05:27 AM	#3 (permalink)
crazijoe Registered User Join Date: Oct 2004 Location: Omaha, The Center of the Universe Posts: 7,632 OS: WinXP, Win2K3 My System	Connect your 2 CD ROM drives to secondary master slave. Connect you 160GB HDD to primary master and connect you 40GB HDD to primary master on the RAID controller. Make sure you boot sequence is correct. Make sure after you install the OS that you install the MB chipset drivers and the RAID controller drivers. Also make sure you set the jumpers correctly on the drives. DO NOT use CS (cable select). __________________ Microsoft MCSA + Messaging, MVP, A+, Network+ http://i16.photobucket.com/albums/b3...other/Help.jpg Do you want a real Republican? HDD diagnostic tools / HDD data recovery software Last edited by crazijoe; 03-10-2005 at 05:28 AM.