R
Richard Byer
Quick question for you hardware guys:
I am intalling a new server here (just a bunch of PC parts that fit the
bill) and I am determined that this one have some redundancy. I tried to
use the Promise IDE RAID connectors on the ASUS mobo (a7v266-e) and could
not get the FastTrak BIOS utility to fire. It does boot, finds 2 brand new
120g barricudas attached on seperate channels, installs the BIOS, but
refuses to respond to the control+F command. The system boots right by it.
So, knowing that I had an 'old' Promise ide raid card (Ultra100 TX2) sitting
in a drawer, I installed that on ANOTHER spare mobo and got the exact same
results. Seems to me that the only real common denominator here is the pair
of 'cudas. I even managed to install Win2k Server on a single one of the
HDs (without mirror) just to prove that the card itself worked and that the
drives were ok.
Any ideas why CONTROL+F will not fire the fasttrak configuration utility so
I can mirror this puppy and get some sleep?
Thanks in advance,
Rich..
I am intalling a new server here (just a bunch of PC parts that fit the
bill) and I am determined that this one have some redundancy. I tried to
use the Promise IDE RAID connectors on the ASUS mobo (a7v266-e) and could
not get the FastTrak BIOS utility to fire. It does boot, finds 2 brand new
120g barricudas attached on seperate channels, installs the BIOS, but
refuses to respond to the control+F command. The system boots right by it.
So, knowing that I had an 'old' Promise ide raid card (Ultra100 TX2) sitting
in a drawer, I installed that on ANOTHER spare mobo and got the exact same
results. Seems to me that the only real common denominator here is the pair
of 'cudas. I even managed to install Win2k Server on a single one of the
HDs (without mirror) just to prove that the card itself worked and that the
drives were ok.
Any ideas why CONTROL+F will not fire the fasttrak configuration utility so
I can mirror this puppy and get some sleep?
Thanks in advance,
Rich..