Solved

Windows 2003 - Disk Manger Driver number change

Posted on 2007-03-28
2
1,126 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
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

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

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

Suggested Solutions

Title # Comments Views Activity
Best Server Board For The Money 19 100
Way to setup network drive share permanently mapped to server 3 73
New HP server install iLo 4 56
Formatting a new 4TB Seagate drive 11 76
this article is a guided solution for most of the common server issues in server hardware tasks we are facing in our routine job works. the topics in the following article covered are, 1) dell hardware raidlevel (Perc) 2) adding HDD 3) how t…
Learn about cloud computing and its benefits for small business owners.
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…
In a recent question (https://www.experts-exchange.com/questions/29004105/Run-AutoHotkey-script-directly-from-Notepad.html) here at Experts Exchange, a member asked how to run an AutoHotkey script (.AHK) directly from Notepad++ (aka NPP). This video…

856 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