Solved

adding additional drive to a DC

Posted on 2006-11-14
10
256 Views
Last Modified: 2010-04-19
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?
0
Comment
Question by:gopher_49
[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
  • 6
  • 4
10 Comments
 

Author Comment

by:gopher_49
ID: 17942825
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
 
LVL 51

Expert Comment

by:Netman66
ID: 17943086
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
 

Author Comment

by:gopher_49
ID: 17947094
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
Free Webinar: AWS Backup & DR

Join our upcoming webinar with experts from AWS, CloudBerry Lab, and the Town of Edgartown IT to discuss best practices for simplifying online backup management and cutting costs.

 
LVL 51

Expert Comment

by:Netman66
ID: 17950046
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
 

Author Comment

by:gopher_49
ID: 17968254
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
 
LVL 51

Expert Comment

by:Netman66
ID: 17968825
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
 

Author Comment

by:gopher_49
ID: 17968841
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
 

Author Comment

by:gopher_49
ID: 17982046
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
 
LVL 51

Accepted Solution

by:
Netman66 earned 500 total points
ID: 17983159
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
 

Author Comment

by:gopher_49
ID: 18071750
Drive E is local to the box.  It's located in the internal drive bay of the HP ML350.  
0

Featured Post

Announcing the Most Valuable Experts of 2016

MVEs are more concerned with the satisfaction of those they help than with the considerable points they can earn. They are the types of people you feel privileged to call colleagues. Join us in honoring this amazing group of Experts.

Question has a verified solution.

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

I guess it is not common knowledge to most Wintel engineers/administrators: If you have an SNMP-based monitoring system in your environment (and it's common to have SNMP or Syslog) it's reasonably easy to enable monitoring of the Windows Event logs,…
I've always wanted to allow a user to have a printer no matter where they login. The steps below will show you how to achieve just that. In this Article I'll show how to deploy printers automatically with group policy and then using security fil…
With Secure Portal Encryption, the recipient is sent a link to their email address directing them to the email laundry delivery page. From there, the recipient will be required to enter a user name and password to enter the page. Once the recipient …
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …

735 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