Multiple DC problems

[ison67]

I have serveral DC problems at the moment. I could really use some help. As I'm somewhat new to this.

I believe it all started with a DC that crashed earlier this week. It been having some hard drive issues anytime it was rebooted. You would have to rebuild one of them (you would get the F1 or F2 options). I put off working on it because it was one of 5 DC's I was planning to demote in August. The guy before me set them all up a DC's and we not need them. We will have 3 left. The one's being demoted are at remote locations.

Ok, back to the problems, as I stated one of the remoted ones crashed (server-41), the schema owner (server-2) is running so slow that it's hard to troubleshoot. There are many DFS replacation errors and File replacation service errors in the event veiwer. One of them was a hard drive space issue. I took care of that. A lot of them are because of the crashed server. I'm just not sure where to start. I'm thinking, I should take care of the crashed DC first. To see if that fixes the problems on server 2.

Didn't mean to write a book. My mind is just running in so many directions.

Thanks in advance for your input. Please free free to ask any questions.

Regards,
Donna

 

[58sniper]

I'd start by looking at the logs on each of the servers.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[pagy]

Did the crashed server hold any fsmo roles?, check by using
netdom query fsmo
from a command prompt.

As Pat says review and post some event logs if applicable.

What state is the crashed server in now? Is it operating albeit badly or is it dead?

Paul
MCSE 2003
MCSA 2003
MCITP Enterprise Administrator

If there are no stupid questions, then what kind of questions do stupid people ask? Do they get smart just in time to ask questions?
Scott Adams

 

[ison67]

Which logs and where are they located?

The DC that crashed will not come up so you can login. However, when it boots up, you get the F1 and F2 option. I choose to try to rebuild. I can get in using run \\servername\c$ from another pc on the newtwork. I'm not sure what this means. I should be able to get to the log file and copy them.

The DC that crashed is at a remote location. So, I haven't been able to do much with it and I'm waiting till I get the new hard drives that I order before I go. I already know that one of the drives needs to be replace.

It doesn't does hold any of the fsmo roles.

The other server that has been running slow and having dfsr errors is the schema owner.

I'll post the log file as soon as you tell me where they are. Thanks!

DJ

 

[pagy]

The DC that crashed will not come up so you can login. However, when it boots up, you get the F1 and F2 option. I choose to try to rebuild. I can get in using run \\servername\c$ from another pc on the newtwork.

Huh?? Will not come up so can login does not make any sense, or should that read can come up so you can login?

The windows event logs, use event viewer to view those logs on your domain controllers

Paul
MCSE 2003
MCSA 2003
MCITP Enterprise Administrator

If there are no stupid questions, then what kind of questions do stupid people ask? Do they get smart just in time to ask questions?
Scott Adams

 

[ison67]

It doesn't ever get to the log on prompt once you chose to rebuild it. I can't remote into it. It has two hard drives that are having problems. They are 0 and 4. I plan on going to the remote location where this server is located once I get the new hard drives. I am working with one of the employees there to get more info. This is what she gets when it boots up.

This is the message that came up on the server.
Slot 2 HP Smart Array 641 Controller (64MB, v2.48) 1 logical Drive

787 Slot 2 Drive Array Operating in Interim Recovery Mode
The following SCSI Drive(s) should be replaced: SCSI ID 0

786 Slot 2 Drive Array Recovery Needed
The following SCSI drive(s) need automatic Data Recovery (Rebuild): SCSI ID 3

Automatic Data Recovery previously aborted!
Run Array Diagnostics utility (ADU) for more info

Select "F1" to retry Automatic Data Recovery
Select "F2" to continue without starting Automatic Data Recovery

I selected F1 and the following message came up in a box:

At least one service or driver failed during system startup. Use Event viewer to examine the event log for details.

I had her select F1. It now has a blue screen, but no message box like usual(usually at this point it would have a message box that says loading setting, ect) Oh yea, disk 0 still has a red X. However, I can get to the files on the server using \\servername\c$????

As for the logs, I was wondering if there is any where these are store. So, I could copy the like a file.

UPdate: The The other server I was having trouble with is working normal now. The only problem events, since last week when I cleaned off the hard drive, are under DFS Replication. Most of these have to do with server 41.

Regards,
DJ

 

[ison67]

I coundn't get it to build the new drive or get in it. So, I have removed it from the network. I will work on recoving it when I have time. Now I have to remove it in AD, DNS, and DHCP. It didn't hold any fmso roles, but it was a DNS and DHCP server. Any info or tip would be most appreciated. I'll check back later for info and to update you.

Thanks,
DJ