Event ID: 13561
Event Type: Error
Rule: Alert suppressed based on ID, source, computer - state to look for event ID 13560 to indicate that the error is auto recover
Message Text:
The File Replication Service has detected that the replica set "%1" is in JRNL_WRAP_ERROR. Replica set name is : "%1" Replica root path is : "%2" Replica root volume is : "%3" A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. This can occur because of one of the following reasons.
[1] Volume "%3" has been formatted.
[2] The NTFS USN journal on volume "%3" has been deleted.
[3] The NTFS USN journal on volume "%3" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal.
[4] File Replication Service was not running on this computer for a long time.
[5] File Replication Service could not keep up with the rate of Disk IO activity on "%3".
Following recovery steps will be taken to automatically recover from this error state.
[1] At the first poll which will occur in %4 minutes this computer will be deleted from the replica set.
[2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.
Event Type: Error
Rule: Alert suppressed based on ID, source, computer - state to look for event ID 13560 to indicate that the error is auto recover
Message Text:
The File Replication Service has detected that the replica set "%1" is in JRNL_WRAP_ERROR. Replica set name is : "%1" Replica root path is : "%2" Replica root volume is : "%3" A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. This can occur because of one of the following reasons.
[1] Volume "%3" has been formatted.
[2] The NTFS USN journal on volume "%3" has been deleted.
[3] The NTFS USN journal on volume "%3" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal.
[4] File Replication Service was not running on this computer for a long time.
[5] File Replication Service could not keep up with the rate of Disk IO activity on "%3".
Following recovery steps will be taken to automatically recover from this error state.
[1] At the first poll which will occur in %4 minutes this computer will be deleted from the replica set.
[2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.