Question

Locked

Is it the RAID or Hard drive?

By rpetrie ·
Hi all,
I think I have a server that is about to die unless I intervene.

I am getting frequent server reboots and the following messages in event logs - see below.

Any help you can offer in diagnosing the root cause of the problem and what I should do to rectify this is much appreciated.

I suspect a failing hard drive or the RAID but I am unsure what to do next.The servr is HP ML150 G3 running SBS premium.

1. Message in file Replication Service log is

NTFRS event ID 13568

The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.

Replica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Replica root path is : "c:\windows\sysvol\domain"
Replica root volume is : "\\.\C:"
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 "\\.\C:" has been formatted.
[2] The NTFS USN journal on volume "\\.\C:" has been deleted.
[3] The NTFS USN journal on volume "\\.\C:" 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 "\\.\C:".
Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state.
[1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication Service.
[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.

WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again.

To change this registry parameter, run regedit.

Click on Start, Run and type regedit.

Expand HKEY_LOCAL_MACHINE.
Click down the key path:
"System\CurrentControlSet\Services\NtFrs\Parameters"
Double click on the value name
"Enable Journal Wrap Automatic Restore"
and update the value.

If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above.
-------------------------------------


2 Message in File system log VolSnap - The shadow copies of volume C: were aborted because of an IO failure on volume C:. Event ID 14.
------------------------------------

3. My backups keep failing on the same files.

This conversation is currently closed to new comments.

1 total post (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Collapse -

Some thoughts

by BFilmFan In reply to Is it the RAID or Hard dr ...

The first thing to do is to go to HP's support site at http://h20000.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp?prodNameId=3279687&lang=en&cc=us&taskId=135&prodTypeId=15351&prodSeriesId=1163831 and download the latest firmware and Windows drivers and install them.

Once you have those on, you can use the drive array analysis tool to check for any issues in the array.

Once the hardware has been checked, try the registry punch. In most of the threads I've seen, it resovles the issue.

Back to Networks Forum
1 total post (Page 1 of 1)  

Related Discussions

Related Forums