CRITICAL: Repair-Volume DESTROYS File Replication Service

after running:

repair-volume c: -offlinescanandfix

ps command (after restart), windows server 2012 standard (domain controller member) is logging following error:

--------------------------------------------------------------

log name:      file replication service
source:        ntfrs
date:          8.10.2013. 1:14:26
event id:      13552
task category: none
level:         error
keywords:      classic
user:          n/a
computer:      dnbdc03.kmbdom.int
description:
file replication service unable add computer following replica set:
    "domain system volume (sysvol share)"
 
caused number of problems such as:
  --  invalid root path,
  --  missing directory,
  --  missing disk volume,
  --  file system on volume not support ntfs 5.0
 
information below may resolve problem:
computer dns name "dnbdc03.kmbdom.int"
replica set member name "dnbdc03"
replica set root path "c:\windows\sysvol\domain"
replica staging directory path "c:\windows\sysvol\staging\domain"
replica working directory path "c:\windows\ntfrs\jet"
windows error status code is 
frs error status code frserrormismatchedjournalid
 
other event log messages may determine problem.  correct problem , service attempt restart replication automatically @ later time.
event xml:
<event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <system>
    <provider name="ntfrs" />
    <eventid qualifiers="49152">13552</eventid>
    <level>2</level>
    <task>0</task>
    <keywords>0x80000000000000</keywords>
    <timecreated systemtime="2013-10-07t23:14:26.000000000z" />
    <eventrecordid>72</eventrecordid>
    <channel>file replication service</channel>
    <computer>dnbdc03.kmbdom.int</computer>
    <security />
  </system>
  <eventdata>
    <data>domain system volume (sysvol share)</data>
    <data>dnbdc03.kmbdom.int</data>
    <data>dnbdc03</data>
    <data>c:\windows\sysvol\domain</data>
    <data>c:\windows\sysvol\staging\domain</data>
    <data>c:\windows\ntfrs\jet</data>
    <data>
    </data>
    <data>frserrormismatchedjournalid</data>
  </eventdata>
</event>

--------------------------------------------------------------

try yourself!
ms, fix possible.

hi,

try following steps.

 

suggestion

==========

1. perform authoritative restore on sysvol on dc dnbdc03.kmbdom.int:

1) please click start, click run, type cmd, , click ok.

2) @ command prompt, type following command, , press enter:

net stop ntfrs

3) click start -> run, type regedit, , click ok.

4) locate , click following registry subkey:

hkey_local_machine\system\currentcontrolset\services\ntfrs\parameters\backup/restore\process @ startup

 

5) right-click burflags entry, , click modify.

6) in value data box, type d4 , click ok, on file menu, click exit.

7) @ command prompt, type following command, , press enter:

 net start ntfrs

it seems frs journal has problem. on ntfs volumes, persistent log tracks changes on volume, including file creations, deletions, , changes. usn journal has configurable maximum size , persistent across reboots , system crashes. frs uses usn journal monitor changes made in replica tree. when usn journal go earlier number, frs cannot detect changes , stop replicating, need perform nonauthoritative restore on server recover journal wrap.

---

please remember click “mark answer” on post helps you, , click “unmark answer” if marked post not answer question. can beneficial other community members reading thread.

Windows Server  >  Windows PowerShell