windows 2008 crashed, cannot access directory services restore

fstinc
fstinc used Ask the Experts™
on
my server 2008 r2 had an abrupt power outage (user error).

i get a blue screen that says "STOP: c00002e2 Directory Services could not start because of the following error: A device attached to the system is not functioning. - Error Status: 0xc0000001"

I can't go into safe mode, last known good config, nothing! and i don't know the dam* AD restore password.  I can login load the perc 100 drivers (raid 1) and see the files on the OS.  

any ideas? this is drive me crazy.

btw: if i go to AD restore mode, i can get to the login screen but i don't know the pw.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®

Author

Commented:
another note: I had an external HD pluggin working as a backup. and i have the windows image backup which is like 135GB, assuming it's a good backup. but I can't even load that by going into the system repair. I can't see the drive. is it because windows does that hidden drive backup thing? how can i reimage/restore my system using that? as last resort.
Kent DyerIT Security Analyst Senior

Commented:
If you cannot bring it up on the original server..  Why not try a different one?  You may have to choose a different LUN for your PERC drive, but you should be able to get to your data on the drive.

HTH,

Kent
Commented:
Found the password and followed these steps to fix it.

.  Restart the server and press F8 key, select Directory Services restore mode.
2.  Log in with the local administrator username and password (hope you remember what you set it to!).
3.  Type cd \windows\system32
4.  type NTDSUTIL
5.  type activate instance NTDS
6.  type files
7.  If you encounter an error stating that the Jet engine could not be initialized exit out of ntdsutil.
8.  type cd\
9.  type md backupad
10. type cd \windows\ntds
11. type copy ntds.dit c:\backupad
12. type cd \windows\system32
13. type esentutl /g c:\windows\ntds\ntds.dit
14. This will perform an integrity check, (the results indicate that the jet database is corrupt)
15. Type esentutl /p   c:\windows\ntds\ntds.dit
16. Agree with the prompt
17. type cd \windows\ntds
18. type move *.log c:\backupad   (or just delete the log files)
This should complete the repair.  To verify that the repair has worked successfully:
1.  type cd \windows\system32
2.  type ntdsutil
3.  type activate instance ntds
3.  type files        (you should no longer get an error when you do this)
4.  type info       (file info should now appear correctly)
One final step, now sure if it's required:
From the NTDSUTIL command prompt:
1.  type Semantic Database Analysis
2.  type Go

Author

Commented:
found password

Commented:
I had this problem this morning after a RAID rebuild, was in DSRM, but was having the Jet engine error.

Thanks fstinc: Saved my bacon!

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial