adding additional drive to a DC

I just added 3 additional drives to an external drive enclosure on a DC.  (win 2003).  It fails to boot due to AD not being available.  It's trying to access the new drives for it's NTDS (AD) information.  Once I pull the drives out it works perfectly fine.  I have the NTDS data on it's second array, this being the third.

How can I fix this?
gopher_49Asked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
Netman66Connect With a Mentor Commented:
Honestly, I've never heard of Server attempting to assign a volume drive letter that is already being used to a new volume .  If E drive is already a volume somewhere then it should use the next available drive letter that is free.

Where is drive E located?  Is it on a SAN or NAS or is it local to the box?

It may be that the Array controller created a new Primary partition - which will take precedence over an Extended partition - however, it should still NOT attempt to assign a drive letter that is already used.

I'm going to see if I can find some documentation that describes how Windows should react to Primary versus Extended partitions - it may take a bit.

0
 
gopher_49Author Commented:
Also,

I just moved the 3 x drives to different slots on the external enclosure.  This assigned different SCSI id's for the drives and allowed the DC to boot properly.  I have 3 x open slots on my external enclosure that I would like to use in the future.  How can I use these slots?  It seems that these slots have the same SCSI id's as drive array two.  Drive array two being the one with the NTDS info......
0
 
Netman66Commented:
Make sure the jumpers on the new drives are set to SCAM.  If they are hard set to a specific ID number then this may explain the conflict.
0
Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
gopher_49Author Commented:
I moved them to different slots on the external enclosure.  Everything works now, however, does this tell me if enabling SCAM would of fixed the problem?  If the ID's are fixed them moving them to different slots on the external enclosure wouldn't of made a difference, correct?
0
 
Netman66Commented:
Depends whether the drive cage is duplexed or not.  If duplexed then the second half of the cage is on a different channel on the RAID controller.  Thus no issue with IDs.
0
 
gopher_49Author Commented:
It's running in non-cluster mode.  This means the backplane is split.  Each SCSI port on the extrernal enclosure is plugged into a different controller on a different server.  I'm wondering if the SCSI id's in the internal drive slots are the same as the id's as the external slots.  The problem went away when I changed the external drives to a different slots.  
0
 
Netman66Commented:
It likely is exactly the same - a split backplane (duplexed drive cage).  It's easy enough to check.  Pull the cover and see how many ribbons are running from the cage to the controller.

0
 
gopher_49Author Commented:
I'll have to do this after hours...  There are two controllers in the backplane.  I'll ask the company I purchased it from and get back with you.  It's a Dell PowerVault 210s.
0
 
gopher_49Author Commented:
There is only one cable per controller.  This seems to be a windows 2003 server problem.  Windows tried to assign the new array to the logical drive E:.  E: is where the Active Directory information is stored.  I'll have to go into active directory restore mode and run the NTDS utility.  Here I can move the NTDS information to another drive.  This will allow the server to boot with the new array being drive E:.  For now I moved the drives to different slots which in return allowed Active Directory to boot.  In the future if I add more drives I'll have to move the NTDS data to another drive.  I'll have to then temporarily move the other data files to a different drive.  Once I get the new array formatted I'll then move the data back onto it, or, a different drive.

I was told the SCSI id's cannot be changed and are fixed on the PowerVault 210s.  This validates my theory of it being a Windows logical drive assignment issue.  

What are your thoughts?
0
 
gopher_49Author Commented:
Drive E is local to the box.  It's located in the internal drive bay of the HP ML350.  
0
All Courses

From novice to tech pro — start learning today.