I have a window 2003 server, RAID SAS Zero Channel raid controller. C drive is a mirror, data drives are Raid 5. I added to the System a SATA drive to the mother board. The system booted. I noticed in Disk Manager that the C Drive is Drive 1 and it made the SATA drive Drive 0. I am concerned about the boot.ini
It is currently. The SAS Mirror C has the MBR on it.
It looks as though C drive was bumped from Disk0 to Disk1 in the DiskManager.
I am concerned about the boot.ini
It is currently.
indows Server 2003, Standard" /fastdetect /NoExecute=OptOut /3GB /USERVA=3030
The SCSI - SAS controller is set as the primary boot device. My concern is that the OS beleives the SATA drive is now Drive 0 on the next system boot.
I saw a reference to bootcfg on ms site http://support.microsoft.com/kb/317521/en-us
It looks as though most of the commands are only available from the recovery console
My question is that it made it DISK0 because there was no Bios on the SATA on the motherboard?
How do I compensate or resolve the issue with out loosing the ability to boot the system?
Woud diabling the SATA drive in Device Manger, Rebooting, Disable the SATA controller resolve this issue?
Would Loosing the SATA drive as Drive0 cause the corrected boot.ini to fail at later time?