I'd also look at running hardware diagnostics, particularly on the disk subsystem and controller. No point in restoring or repromoting if there is an unresolved hardware problem.
-----Original Message-----
From: [EMAIL PROTECTED] on behalf of Steve Linehan
Sent: Fri 8/19/2005 8:18 PM
To: ActiveDir@mail.activedir.org
Cc:
Subject: RE: [ActiveDir] Database Corruption
Well the first thing I always recommend is to try an offline defrag as
it is possible that the corruption is in an index, i.e. metadata, that can be
rebuilt. If the offline defrag fails then restoring from backup or repromoting
will be your next step.
Thanks,
-Steve
_____
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ayers,
Diane
Sent: Friday, August 19, 2005 6:43 PM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] Database Corruption
My preferred approach would be to demote the box to member server and
re-promote to a domain controller to ensure a good fresh copy of the DIT. YMMV
as the specific requirements at your location may prevent this. We have only
run into this once early in our AD days and this was the approach we used with
good success.
Diane
_____
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alex
Fontana
Sent: Friday, August 19, 2005 3:29 PM
To: ActiveDir@mail.activedir.org
Subject: [ActiveDir] Database Corruption
Started getting the error below a few weeks ago on one of our DCs. My
first reaction is to run a non-auth restore from a day before this started
happening and let replication take care of everything else. Any reason NOT to
do this? I’m concerned that this may happen again and wasn’t able to find
anything specific to the error below. Besides calling PSS any thing else I
should look into before restoring? This box holds all FSMO roles, Win2k3,
server for NIS.
TIA
-alex
Event Type: Error
Event Source: NTDS ISAM
Event Category: Database Page Cache
Event ID: 475
Date: 8/19/2005
Time: 2:00:24 PM
User: N/A
Computer: DC
Description:
NTDS (528) NTDSA: The database page read from the file
"C:\WINNT\NTDS\ntds.dit" at offset 665067520 (0x0000000027a42000) for 8192
(0x00002000) bytes failed verification due to a page number mismatch. The
expected page number was 81184 (0x00013d20) and the actual page number was
2349964126 (0x8c119b5e). The read operation will fail with error -1018
(0xfffffc06). If this condition persists then please restore the database from
a previous backup. This problem is likely due to faulty hardware. Please
contact your hardware vendor for further assistance diagnosing the problem.
<<winmail.dat>>
