EVENT ID 55: When Good Bits Go Bad

re: EVENT ID 55: When Good Bits Go Bad

Thomas — Fri, 22 Feb 2013 03:41:21 GMT

William article is great help in understanding but i want to know even after run chkdsk or chkdsk/r with no errors, if we keep on getting the event id generated. Does that mean sth wrong?

re: EVENT ID 55: When Good Bits Go Bad

Luke — Wed, 09 Jan 2013 13:46:32 GMT

I am seeing the same problem as RobK - no drive letter listed, just a blank space and then the full stop. I ran chkntfs on both of the volumes in the server and neither were dirty.

Has anyone found the cause / solution for this?

re: EVENT ID 55: When Good Bits Go Bad

SluggoMagoo — Mon, 17 Dec 2012 16:29:22 GMT

This is the long version of "I Don't Know".

re: EVENT ID 55: When Good Bits Go Bad

RobK — Tue, 17 Jul 2012 15:42:17 GMT

Nice article. the only problem is that on my windows 2003 server it only says

The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume . as you can see it only gives a dot and not drive letter. what are my options?

thanks

re: EVENT ID 55: When Good Bits Go Bad

Jeffrey S. Patton — Fri, 11 May 2012 15:34:58 GMT

Agred, and does this logic move forward into windows 2012?

re: EVENT ID 55: When Good Bits Go Bad

Prabhash — Fri, 11 May 2012 03:06:13 GMT

Nice blog William, "NTFS instead has a logic that checks some reads for congruence", it would have been great if you would have had expaliend that logic.