Why do you say it is not hardware?  If by replacing the
backplane/harddrive, they had to copy the database / drive contents, then
it's too late the old hardware may have already corrupted the ntds.dit
file, copying a corrupted file, leaves _a corrupted file_.

When the event shows up again, is the event always listing the same
22216704 offset?  That would be further evidence the file contents are the
same, and they are corrupted contents.  We can tell this because we
checksum every 8KBs of data.

Sounds like you have replicas of that domain, consider yourself lucky,
and go take backups of any single replica domains (or better yet,
ensure you have replicas). ;)

If you call Msft PSS with a corrupted bit in your database, that doesn't
happen to be in secondary index (as Steve mentioned), you will not like
the answer.

Cheers,
Brett Shirley



On Thu, 30 Jun 2005, Steve Linehan wrote:

> You could try an offline defrag first.  If the corruption is in an index
> then this would correct the problem without a rebuild of the server.  If
> the offline defrag fails then I would blow it away and rebuild.
> 
> Thanks,
> 
> -Steve
> 
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of joe
> Sent: Thursday, June 30, 2005 6:13 PM
> To: [email protected]
> Subject: RE: RE: [ActiveDir] Corrupted NTDS.dit
> 
> I would say blow it away and re-promo it.
> 
>    joe 
> 
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> [EMAIL PROTECTED]
> Sent: Thursday, June 30, 2005 6:39 PM
> To: [email protected]
> Subject: Re: RE: [ActiveDir] Corrupted NTDS.dit
> 
> I'm getting this error running replmon:
> 
> Domain Controller Name:                   DCHIG1
>               Directory Partition:        DC=co,DC=slo,DC=ca,DC=us
>               Replication Partner:        DSSPR\DCPR
>               Failure Code:                1127
>               Failure Reason:             While accessing the hard disk,
> a
> disk operation failed even after retries.
> 
> ....And I'm getting this in the application section of the event
> viewer....
> 
> Event ID 474
> Source: ESENT
> 
> lsass (1184) The database page read from the file
> "X:\WINDOWS\NTDS\ntds.dit"
> at offset 22216704 (0x0000000001530000) for 8192 (0x00002000) bytes
> failed
> verification due to a page checksum mismatch.  The expected checksum was
> 730343452 (0x2b88281c) and the actual checksum was 3032224511
> (0xb4bc12ff).
> 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.
> 
> I had IBM come in and swap out the BackPlane and a hard drive, so I'm
> fairly
> sure it's not hardware based.  And my objects are being replicated from
> this
> DC.  I'm just not sure what's not working so I want to just rebuild the
> NTDS.dit
> 
> Thanks.  Kevin
> > 
> > From: "Almeida Pinto, Jorge de" <[EMAIL PROTECTED]>
> > Date: 2005/06/30 Thu PM 03:59:22 EDT
> > To: <[email protected]>,  <[email protected]>
> > Subject: RE: [ActiveDir] Corrupted NTDS.dit
> > 
> > why do you say "it partially replicates"? what errors (event ids and
> sources) are being logged in the event viewer? 
> >  
> > #JORGE#
> > 
> > ________________________________
> > 
> > From: [EMAIL PROTECTED] on behalf of 
> > [EMAIL PROTECTED]
> > Sent: Thu 6/30/2005 6:17 PM
> > To: [email protected]
> > Subject: [ActiveDir] Corrupted NTDS.dit
> > 
> > 
> > 
> > Hi, 
> >         I have a corrupt NTDS.dit file with no backup, although the 
> > windows 2003 DC starts up fine and partially replicates to my other 4 
> > DC's.  Can someone tell me the best steps to restore this file.  This 
> > particular DC is also the FSMO holder.  I was considering transferring
> 
> > the role temporarily, demoting and then promoting this DC and having 
> > DCPROMO rewrite the NTDS.dit.  Is this suicide?  Thanks in advance
> > 
> > Kevin Atnip 
> > List info   : http://www.activedir.org/List.aspx 
> > List FAQ    : http://www.activedir.org/ListFAQ.aspx 
> > List archive: 
> > http://www.mail-archive.com/activedir%40mail.activedir.org/
> > 
> > 
> > 
> > This e-mail and any attachment is for authorised use by the intended
> recipient(s) only. It may contain proprietary material, confidential
> information and/or be subject to legal privilege. It should not be
> copied,
> disclosed to, retained or used by, any other party. If you are not an
> intended recipient then please promptly delete this e-mail and any
> attachment and all copies and inform the sender. Thank you.
> > List info   : http://www.activedir.org/List.aspx
> > List FAQ    : http://www.activedir.org/ListFAQ.aspx
> > List archive: 
> > http://www.mail-archive.com/activedir%40mail.activedir.org/
> > 
> List info   : http://www.activedir.org/List.aspx
> List FAQ    : http://www.activedir.org/ListFAQ.aspx
> List archive:
> http://www.mail-archive.com/activedir%40mail.activedir.org/
> 
> List info   : http://www.activedir.org/List.aspx
> List FAQ    : http://www.activedir.org/ListFAQ.aspx
> List archive:
> http://www.mail-archive.com/activedir%40mail.activedir.org/
> List info   : http://www.activedir.org/List.aspx
> List FAQ    : http://www.activedir.org/ListFAQ.aspx
> List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
> 

List info   : http://www.activedir.org/List.aspx
List FAQ    : http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/

Reply via email to