B
Brian Kreck
Project: Installed new mirrored SCSI 68GB(formatted)
drives to Dell PowerEdge 2500.
Pre-Existing Drives: mirror 16GB(formatted) partitioned
into 2 drives, 4GB and 12GB
Notes: This server does it all... AD, DNS, DHCP, Exchange,
and File Server. I have plans to split some of these
things off.. but as there are only 5 users the load has
never been that great. System files are found on the 4GB
drive (C
as are the exchange files. Our client data
files were on the 12GB drive (E. We have been tight on
space for quite some time and reached a point of only 200-
400MB free on C: (not including the swapfile... ie: pretty
tight) and 200MB on the data drive (also quite tight).
- I began by initializing the new drive, partitioning it,
and formatting it to NTFS. All seemed to go well. I then
had a new 68GB drive called F.
- I coppied the datafile form E to F The transfer went
well. I re-made the share using the exact same name. The
workstations worked with the new datafile correctly.
- I backed up the contents of E to a networked machine
using MS Backup.
- I removed the data on E.
- Things seemed to work for several hours.
- One user complainded they were unable to log in to the
Exchange Server... but the others could.
- A couple hours later the server was unresponsive.
Exchange and Terminal services was down.
Upon boot, I now get the message:
"Application popup: lsass.exe - System Error : Security
Accounts Manager initialization failed because of the
following error: Directory Service cannot start. Error
Status: 0xc00002e1. Please click OK to shutdown this
system and reboot into Directory Services Restore Mode,
check the event log for more detailed information. "
Microsoft article Q240362 seems to address the issue, but
it does not match the cause. The ntds.dit file is sitting
properly in the c:\winnt\ntds\ folder as it should. I
checked the last time it was accessed and it was modified
at the correct time.
I know I am going to get some heat over this, but I don't
have a backup of the AD. :-(
Any ideas? I'm out.
drives to Dell PowerEdge 2500.
Pre-Existing Drives: mirror 16GB(formatted) partitioned
into 2 drives, 4GB and 12GB
Notes: This server does it all... AD, DNS, DHCP, Exchange,
and File Server. I have plans to split some of these
things off.. but as there are only 5 users the load has
never been that great. System files are found on the 4GB
drive (C
as are the exchange files. Our client datafiles were on the 12GB drive (E
. We have been tight onspace for quite some time and reached a point of only 200-
400MB free on C: (not including the swapfile... ie: pretty
tight) and 200MB on the data drive (also quite tight).
- I began by initializing the new drive, partitioning it,
and formatting it to NTFS. All seemed to go well. I then
had a new 68GB drive called F.
- I coppied the datafile form E to F The transfer went
well. I re-made the share using the exact same name. The
workstations worked with the new datafile correctly.
- I backed up the contents of E to a networked machine
using MS Backup.
- I removed the data on E.
- Things seemed to work for several hours.
- One user complainded they were unable to log in to the
Exchange Server... but the others could.
- A couple hours later the server was unresponsive.
Exchange and Terminal services was down.
Upon boot, I now get the message:
"Application popup: lsass.exe - System Error : Security
Accounts Manager initialization failed because of the
following error: Directory Service cannot start. Error
Status: 0xc00002e1. Please click OK to shutdown this
system and reboot into Directory Services Restore Mode,
check the event log for more detailed information. "
Microsoft article Q240362 seems to address the issue, but
it does not match the cause. The ntds.dit file is sitting
properly in the c:\winnt\ntds\ folder as it should. I
checked the last time it was accessed and it was modified
at the correct time.
I know I am going to get some heat over this, but I don't
have a backup of the AD. :-(
Any ideas? I'm out.