Darkstar850
[H]ard|Gawd
- Joined
- Feb 18, 2004
- Messages
- 1,307
I just got a Promise Tx2000 raid controller for my file server to run Raid1 for my files. There are 3 HD, one boot drive running Windows 2000. I have 2 120GB maxtor 7200 RPM ATA drives for the Raid. I have each disk set to master, and each one is on its own IDE channel on the raid controller.
I have installed the drivers for the controller, and it shows correctly in device manager. During boot, I have the option to go into the controller's BIOS. Both drives show up in Raid1, and the array shows as functional.
However, the array does not show in Windows. I am pretty sure why it isn't working, but I am not sure how to fix it. According to the TX2000 manual, if there is a * by the array in the controller BIOS, the array is bootable, and will attempt to become the C drive. My array does have the *. I have tried auto creating the array, and manually creating it, and it automatically becomes bootable.
How do I stop the array from attempting to becoming bootable and seize C:? I read the entire manual from promise's site, but the issue was not discussed.
Thanks
I have installed the drivers for the controller, and it shows correctly in device manager. During boot, I have the option to go into the controller's BIOS. Both drives show up in Raid1, and the array shows as functional.
However, the array does not show in Windows. I am pretty sure why it isn't working, but I am not sure how to fix it. According to the TX2000 manual, if there is a * by the array in the controller BIOS, the array is bootable, and will attempt to become the C drive. My array does have the *. I have tried auto creating the array, and manually creating it, and it automatically becomes bootable.
How do I stop the array from attempting to becoming bootable and seize C:? I read the entire manual from promise's site, but the issue was not discussed.
Thanks