Solved

Windows 2003 - Disk Manger Driver number change

Posted on 2007-03-28
2
1,132 Views
Last Modified: 2010-05-18
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?
0
Comment
Question by:robmulvey
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 14

Accepted Solution

by:
warrenbuckles earned 500 total points
ID: 18813762
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
 

Author Comment

by:robmulvey
ID: 18845611
I did get a chance to test it on another duplicate system not in production.  It did not affect the boot.  
0

Featured Post

What Is Transaction Monitoring and who needs it?

Synthetic Transaction Monitoring that you need for the day to day, which ensures your business website keeps running optimally, and that there is no downtime to impact your customer experience.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Data center, now-a-days, is referred as the home of all the advanced technologies. In-fact, most of the businesses are now establishing their entire organizational structure around the IT capabilities.
We look at whether swapping a controller board on a failed hard drive is likely to solve the problem.
This video Micro Tutorial explains how to clone a hard drive using a commercial software product for Windows systems called Casper from Future Systems Solutions (FSS). Cloning makes an exact, complete copy of one hard disk drive (HDD) onto another d…
There's a multitude of different network monitoring solutions out there, and you're probably wondering what makes NetCrunch so special. It's completely agentless, but does let you create an agent, if you desire. It offers powerful scalability …

688 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question