Windows 2003 - Disk Manger Driver number change

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.
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows 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?
robmulveyAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

warrenbucklesCommented:
Hello robmulvey:

This would be a problem if you were booting off the SATA devices.  However, you are using the SCSI BIOS extensions to INT 13 to boot and the boot device enumeration in BOOT.INI refers to the SCSI sub-system, which sets the SCSI boot drive to disk(0) at boot time.

Even if you were booting off the SATA drives, the problem could be fixed by changing the boot drive in BIOS to the correct SATA device.

The enumeration of drives in Disk Manager doesn't map directly to the drive enumeration at boot time.

wb
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
robmulveyAuthor Commented:
I did get a chance to test it on another duplicate system not in production.  It did not affect the boot.  
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.