219com
asked on
FRS causes NTFS corruption
I have one of my domain controllers that when FRS begins replicating the Sysvol file I get NTFS event 55 corruption errors until the server locks up and needs re-booting. As soon as I take FRS back off line the errors stop. The two servers are in different location supplied by a wireless link, but all other filesharing and internet services work just fine. When I perfrom a CHKDSK it claims to have fixed corrupt issues and that all is fine. Then, bam, dozens of event 55 errors. Any ideas?
ASKER
I installed that hotfix. It looked like it might have been the problem, but it did not solve the issue. I am not 100% sure it is a FRS or DFS-R issue, I just noticed when I shut off those services, the server didn't lock up over night. It might just be a coincidence.
Did you run chkdsk on the drives?
ASKER
Yes, I ran CHKDSK and it claims to have fixed errors. As soon as I logon and open event viewer the event 55 errors start up again. They occur in clusters. I might get 6 or 7 and then they stop for maybe an hour or so. Then they continue again, until it eventually locks up. I was going to demote the server from a BDC to a application server and see if it is corruption in the Sysvol file or in the replication of it somehow.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I defragged it when the issue frirst arose. There is plenty of free space on the C:, 150GB as a matter of fact.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
As far as I know there is no 55 event id in the file replication service logs.If you are talking about event id 55 source ntfs,it is related to the disk and there is a hotfix for windows 2003 server:
http://support.microsoft.com/kb/932578
=or run chkdsk in read only mode on the drive.