Question : DSREPAIR error after schema extend

In process of upgrading from NW6SP5 to NW65SP6.  I ran the Deploymet Manager and extended the schema successfully.  Ran DSREPAIr on this server that has R/W replica, and this aborted.  DSREPAIR on Master Replica completed with zero errors.  I've not been able to find any TID on this, so hoping for some help.  thank you in advance *

/****************************************************************************/
NetWare 6.00 Directory Services Repair 10250.42, DS 10350.30
Log file for server ".AUBURN.ENTERPRISE" in tree "ENTERPRISE"

** Automated Repair Mode **
Repairing Local Database
Start:  Friday, April 20, 2007  10:25:02 am Local Time

** All disk amounts are approximations **
->Current available disk space: 6509 MB
->DSRepair may need to use: 6 MB
->Disk space remaining after operation: 6509 MB

Physical Check
Creating Temporary Files
Repair Trees - Scan Values
Repair Trees - Sorting Values
Repair Trees - Scan Entries
Repair Trees - Sorting Entries
Repair Trees - Check Values
Repair Trees - Check Entries
Total Objects in Database:       1877
Total Objects in Schema  :       1455
Total External References:          1
Total Objects in Replicas:        412
Schema Check

Repairing objects in a replica
Start:  Friday, April 20, 2007  10:25:10 am Local Time
[1 of 1] Read Write : T=ENTERPRISE
Total Objects = 412, UNKNOWN class objects = 0, Total Values = 12918
Total partition and object events rejected during repair = 52

Checking local references
Start:  Friday, April 20, 2007  10:25:11 am Local Time
Repairing single object:

Object ID: 0000801C, [Pseudo Server]

Total Objects = 1, UNKNOWN class objects = 0, Total Values = 34
Total partition and object events rejected during repair = 52
Temporary DIB set replacing NDS working DIB set.
ERROR: Operation or update failed with Error: -6008

WARNING: The current dib set name is set to: NDT
NOTICE: Successfully set current dib set to: NDS

Repair process aborted

** Automated Repair Mode **
Finish:  Friday, April 20, 2007  10:25:13 am Local Time
Total repair time: 0:00:11

Answer : DSREPAIR error after schema extend

After you extended the schema on the Master of [Root] did you make sure to allow the changes to completely replicate before trying DSREPAIR?

I noticed that a lot of events were rejected during repair.

The -6008 error means it couldn't delete a file.

At this point,*if all else fails,* I'd make sure the replication has completed, and then go into dsrepair on this server, Advanced Options, Global Schema Options and do a "Request schema from Tree."  This will ask the Master of [Root] for a sync of the schema.

If that fails to produce results try "Reset Local Schema." This will clear the local DB's schema and request to receive all of the schema fresh, from the Master of [Root].

Before you do that though, I'd suggest you go into dsrepair, advanced options on the Master of [Root] server, and run through the replica ring options, to make sure the replica ring is healthy and in sync.  Maybe just forcing a sync of the replica will do the trick.