• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Problem setting up my RAID.

M

mluke245

Limp Gawd
Joined
Apr 23, 2005
Messages
174
First and foremost would just like to say "Hey" to everyone. I'm not new to the forum but this is my first official post.

System Specs :

AMD 4000+ @ Stock
Soltek K890Pro-939
---Northbridge VIA K8T890 + Southbridge VT8237
---Promise PDC20579
2 x WD Raptor 36gb - RAID 0
2 x Seagate 300gb SATA
ATi Radeon X850 XT
1gb Crucial Tracer @ default timings
Creative Sound Blaster Audigy 2 ZS Platinum Pro
yadda yadda yadda

Basically this is a last resort for me.... I currently have my WD Raptor's on the VT8237 controller striped to RAID 0. All is good with that... installed the 3rd Party VIA RAID drivers and they work fine. However, I have my Seagates on the Promise controller....this is where the problem begins. First off when I installed the 3rd Party Promise RAID drivers they worked fine. Windows detected the RAID 0 array....let me create a partition and the whole nine yards. However, I began installing Windows on the WD Raptor Array....basically keeping the Seagates untouched for the 600gb of space. Well when I started to install Windows it gave me the blue screen of death....stateing "driver unloaded without canceling pending operations." The root of the problem was the ftsata2.sys file. Beings it was the first time I seen the error...I just restarted and hoped the problem would go away...but it didn't. It always happens when its "Registrying Components" with about 12 minutes left in the install.

Everything is set in the BIOS for RAID...according to the manual. Another problem I run into is when I set the Promise controller to " SATA " instead of RAID...it only detects my HD's when booting up....Windows doesn't see them at all. When I try to install Windows on my Raptor Array with the Promise Controller set to SATA it won't even install windows. It keeps repeating the process of booting from the CD even after it has been setup (partitioned, 3rd party drivers, etc). I've reconfigured the first boot device and which array to boot up from...but it didn't work.

I've exhausted all the options I can think of....and quite frankly I'm getting pretty tired right now :) . Hopefully someone can give me some input on the problem....or at leats point me in a good direction. I'm starting to wonder if an Nforce 4 Pro chipset would have been alot less of a headache...I really don't want to buy a new Mobo though....Hopefully its just something I'm missing on my end....thanks for the help in advance!
 
I would only install the F6 disk for the RAID controller that you will be installing Windows on. I would use Device Manager to install the driver for the other controller after you complete the install and get to desktop.

Also, I am going to close your duplicate thread to keep all of the replies and discussion in one place...would you like me to delete it as well?
 
When I have mutiple drives in a system and I want to install Windozes I always unhook all the unneeded drives.
This makes sure that the boot files ect, end up on the Windoze drive.

So I would only have your Raptor hooked up when you first install Windozes.
Then once its up and running add all the other drives.
You may well have to go into the bios and change the Raptors back to your boot drives after you have added the other array.

Luck......... :D
 
DougLite said:
I would only install the F6 disk for the RAID controller that you will be installing Windows on. I would use Device Manager to install the driver for the other controller after you complete the install and get to desktop.

Also, I am going to close your duplicate thread to keep all of the replies and discussion in one place...would you like me to delete it as well?
Click to expand...

Ah wow....why didn't I think of that? haha...well I'll go ahead and try that and report back what I find. Oh, and go ahead and delete the double post...that was my bad :).

--------------------
UPDATE:

Tried just adding new hardware and installing the drivers that way, but it always gives me " Device Cannot Start (Code:10)" . Tried going back into the Promise RAID Manager and deleting and creating a new array and that didn't work. Double-checked to see if I had the RAID controller set to SATA in the BIOS but it was set to RAID as well. Now I'm stumped :(
 
Tigerbiten said:
When I have mutiple drives in a system and I want to install Windozes I always unhook all the unneeded drives.
This makes sure that the boot files ect, end up on the Windoze drive.

So I would only have your Raptor hooked up when you first install Windozes.
Then once its up and running add all the other drives.
You may well have to go into the bios and change the Raptors back to your boot drives after you have added the other array.

Luck......... :D
Click to expand...

Problem is though, 'windozes' is not detecting my Promise RAID controller now, so in return it doesn't even detect my hard drives. On top of that, when I try to add new hardware and install the drivers that way...it always says my device won't start (as stated above).

Thanks for the help guys, keep thinking for me though...I'm all out of ideas!!
 
I just tried a different approach now, only to find ANOTHER blue screen of death giving me "Bad Pool Header" . Almost instantaneously when I boot into windows it gives me the blue screen and goes through the reboot phase. Why is this giving me so much problems??
 
Just another update. I limited the "Bad Pool Header" error down to a software error. When I installed the FastTrak Utility it immediatey gave me that error...so now I know not to install that. Before that, however, I was able to view my array from the PAM RAID Viewer, but Windows itself didn't recognize my drives or anything. The utility could view it, but Windows didn't assign any drive letters or anything.

I've honestly never gone this route so your help is needed again....how do I get windows to view the array? Maybe installing the 4 in 1 drivers would solve that? I appreciate your guys help because I got this far. :D
 
I FINALLY got it after some trial and error. I would like to thank both of you and DougLite for pointing me in the right direction. After a little search within the PAM Raid Program in some help topics I found exactly what I was looking for. Just had to download newer drivers, specify where and install them, then I created the 0 Array using the PAM Program. From then on the 'Help Topics' helped me all the way through and I am currently formatting all 558.92 gb of hard drive space. Windows detects it and all :) . Ahh feels good to solve that headache.

Sometimes I wish things were as easy as installing Memory :) .

Thanks again.... :D
 
You must log in or register to reply here.
Back
Top