-
1
- #1
Ran into this for the first time, made me sweat and hopefully someone can get some use for it...
This error occurred after a mirrored hard drive failed and was replaced. Corruption was a result on the good hard drive. It’s not a good thing when chkdsk whips through hundreds of system files deleting orphaned files
Couldn't find the system state backups, time to sweat.
Reboot to AD restore mode and run a bunch of commands from every website posting I could find. Well, none of it worked for me. According to Microsoft and many other users, if all else fails, rebuild the domain from scratch. Uh, no, not an option here folks. The server is a dual xeon (dual core) with a mirror and raid5 setup on scsi hard drives. SRCZCRX raid controller from intel.
Anyhow, ran through everything I could think of (and every post I could find) with ntdsutil, no luck (would always come back with JET errors). Then I came across this (and it didn’t work by the way) BUT…
I ran the following commands:
esentutl /g “c:\windows\ntds\ntds.dit” /!10240 /8 /o
might fail, but do next step anyway
esentutl /p “c:\windows\ntds\ntds.dit” /!10240 /8 /o
Delete log files
Reboot server normally
This got me to thinking, why not move the ntds.dit to another location.
In Directory Restore mode, create a folder called c:\ntds and move the ntds.dit to the folder. Run the following commands in an offline situation..
esentutl /g “c:\ntds\ntds.dit” /!10240 /8 /o
esentutl /p “c:\ntds\ntds.dit” /!10240 /8 /o
The results came back fine!!
Important: Move the ntds.dit back to the c:\windows\ntds directory (move all the other files to a backup location).
Run the integrity check:
ntdsutil files integrity (should now come back ok)
Run the command:
ntdsutil “sem d a” “go f” (should now come back ok)
Follow the offline defrag here:
Transfer the ntds.dit back to c:\windows\ntdts folder, remove any log files and reboot the server.
My God, it worked for me!!! The domain is back online )
Quick, get a system state backup!!!
~ K.I.S.S - Don't make it any more complex than it has to be ~
This error occurred after a mirrored hard drive failed and was replaced. Corruption was a result on the good hard drive. It’s not a good thing when chkdsk whips through hundreds of system files deleting orphaned files
Couldn't find the system state backups, time to sweat.Reboot to AD restore mode and run a bunch of commands from every website posting I could find. Well, none of it worked for me. According to Microsoft and many other users, if all else fails, rebuild the domain from scratch. Uh, no, not an option here folks. The server is a dual xeon (dual core) with a mirror and raid5 setup on scsi hard drives. SRCZCRX raid controller from intel.
Anyhow, ran through everything I could think of (and every post I could find) with ntdsutil, no luck (would always come back with JET errors). Then I came across this (and it didn’t work by the way) BUT…
I ran the following commands:
esentutl /g “c:\windows\ntds\ntds.dit” /!10240 /8 /o
might fail, but do next step anyway
esentutl /p “c:\windows\ntds\ntds.dit” /!10240 /8 /o
Delete log files
Reboot server normally
This got me to thinking, why not move the ntds.dit to another location.
In Directory Restore mode, create a folder called c:\ntds and move the ntds.dit to the folder. Run the following commands in an offline situation..
esentutl /g “c:\ntds\ntds.dit” /!10240 /8 /o
esentutl /p “c:\ntds\ntds.dit” /!10240 /8 /o
The results came back fine!!
Important: Move the ntds.dit back to the c:\windows\ntds directory (move all the other files to a backup location).
Run the integrity check:
ntdsutil files integrity (should now come back ok)
Run the command:
ntdsutil “sem d a” “go f” (should now come back ok)
Follow the offline defrag here:
Transfer the ntds.dit back to c:\windows\ntdts folder, remove any log files and reboot the server.
My God, it worked for me!!! The domain is back online )
Quick, get a system state backup!!!
~ K.I.S.S - Don't make it any more complex than it has to be ~
