Announcement

Collapse
No announcement yet.

Disk corruption reported (Event 55) frequently

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Disk corruption reported (Event 55) frequently

    We have Western Digital Lifebook Pro external hard-drives connected to a
    Windows Server 2003 machine for back-up. We get frequent reports of
    corruption in the System Event Log:

    Event Type: Error
    Event Source: Ntfs
    Event Category: Disk
    Event ID: 55
    Date: 17/01/2008
    Time: 02:36:39
    User: N/A
    Computer: <ComputerName>
    Description:
    The file system structure on the disk is corrupt and unusable. Please run
    the chkdsk utility on the volume J:.


    This has happened on several such drives, and I'm becoming suspicious that
    it isn't a physical problem with the drives at all. Having said that, running
    chkdsk does typically report the following (for example):

    The type of the file system is NTFS.
    Volume label is BU1.

    CHKDSK is verifying files (stage 1 of 5)...
    864960 file records processed.
    File verification completed.
    6 large file records processed.
    0 bad file records processed.
    0 EA records processed.
    0 reparse records processed.
    CHKDSK is verifying indexes (stage 2 of 5)...
    3029455 index entries processed.
    Index verification completed.
    5 unindexed files processed.
    CHKDSK is verifying security descriptors (stage 3 of 5)...
    864960 security descriptors processed.
    Cleaning up 164 unused index entries from index $SII of file 9.
    Cleaning up 164 unused index entries from index $SDH of file 9.
    Cleaning up 164 unused security descriptors.
    Fixing mirror copy of the security descriptors data stream.
    Security descriptor verification completed.
    58113 data files processed.
    CHKDSK is verifying file data (stage 4 of 5)...
    864944 files processed.
    File data verification completed.
    CHKDSK is verifying free space (stage 5 of 5)...
    33821987 free clusters processed.
    Free space verification is complete.
    CHKDSK discovered free space marked as allocated in the
    master file table (MFT) bitmap.
    Windows has made corrections to the file system.

    366290000 KB total disk space.
    229851596 KB in 806809 files.
    207712 KB in 58115 indexes.
    0 KB in bad sectors.
    942744 KB in use by the system.
    65536 KB occupied by the log file.
    135287948 KB available on disk.

    4096 bytes in each allocation unit.
    91572500 total allocation units on disk.
    33821987 allocation units available on disk.


    1. It always seems to cite 'file 9'. We have some large BKFs; one, for
    example, is over 20 GB. Are such large files likely to be problematic?

    2. The drives that have reported errors are connected to a Belkin Firewire
    800 card. I realise that Windows doesn't implement Firewire 800 correctly,
    but might the card be a problem?

    3. Does anyone know the mechanism by which Windows detects such errors?
    Might the problem be one of communication rather than a disk defect? (We also
    get the following in the Event Log:

    Event Type: Error
    Event Source: sbp2port
    Event Category: None
    Event ID: 9
    Date: 17/01/2008
    Time: 02:36:48
    User: N/A
    Computer: <ComputerName>
    Description:
    The device, \Device\Sbp2\WD&External HDD Device&0&009, did not respond
    within the timeout period.)

    4. I have replaced such a drive with a new one, but that is behaving in the
    same way.

    5. There's a documented issue with cluster sizes smaller than 4096 bytes
    (kb93257 that's mentioned elsewhere on this forum, but that would seem not
    to apply here (see above chkdsk report).


    Any thoughts would be appreciated.

  • #2
    Re: Disk corruption reported (Event 55) frequently

    Run FSUTIL (from CMD Prompt) using the DIRTY switch and see if you have any corruption at that level.

    eg. >fsutil dirty query f:
    1 1 was a racehorse.
    2 2 was 1 2.
    1 1 1 1 race 1 day,
    2 2 1 1 2

    Comment


    • #3
      Re: Disk corruption reported (Event 55) frequently

      Thanks for the suggestion.

      I've scripted a check on all disks, the results of which I can compare with any further Event Log reports of corruption.

      The 'chkntfs' command will do a similar thing, and can also set whether a chkdsk will be run on dirty drives on next boot. Does anyone know how persistent the 'chkntfs /x' command is? I realise that a subsequent 'chkntfs /x' will undo the effects of a previous invocation, but will such a command persist beyond a reboot?

      It would still be useful to know how a drive is marked as dirty, and whether there are alternative explanations to a physical corruption.

      Comment


      • #4
        Re: Disk corruption reported (Event 55) frequently

        I've just had a potentially promising reply from another forum.

        "It appears that the disk is under stress and at times does not respond. If
        you cache writes, this is sure to cause corruption."

        The drive that I'm particularly concerned about was indeed configured for write-caching, whereas a drive that hasn't caused such problems was not. I strongly suspect that a replaced drive was also configured in such a way.

        I've disabled write-caching, and will report on progress.

        Comment


        • #5
          Re: Disk corruption reported (Event 55) frequently

          I think I was mistaken when reporting that the drive was configured for write-caching.

          And the Event Log reported another drive corruption (also detected by 'fsutil dirty') over the weekend. So, the problem remains...

          Comment


          • #6
            Re: Disk corruption reported (Event 55) frequently

            Did you repair the corruption?
            If yes, does it corrupt again?
            Does a different drive also corrupt?
            If you put the original drive in a different machine, does it also corrrupt in that machine?
            Trying to assertain if the drive is the problem or the controller on the device it is connected to.
            1 1 was a racehorse.
            2 2 was 1 2.
            1 1 1 1 race 1 day,
            2 2 1 1 2

            Comment


            • #7
              Re: Disk corruption reported (Event 55) frequently

              I repaired the corruption, but another was reported this morning. This happens frequently.

              It has happened with other such external drives; hence my suspicion that there's an issue with something other than the drive itself.

              I'm going to connect it via USB and see what happens. I have another such drive connected via USB, and that hasn't reported such corruptions. However, I have another such drive connected to the Firewire 800 controller that seems to working reliably too.

              Comment


              • #8
                Re: Disk corruption reported (Event 55) frequently

                The problem seems to be with using more than one drive connected through Firewire 800.

                I have one drive working successfully, but a second drive connected in this way will frequently report corruptions. I've tried different a port on the card, different cables, chaining the drive via a port on the other drive, none of which solves the problem. I've updated the firmware which was reported to deal with an issue using multiple drives connected through Firewire, but that didn't make a difference. Perhaps my issue is a further symptom of such problems.

                I've since reverted to USB, and have had no further problems (for a week or two, at least). It's a shame I'm unable to use the advantages offered by Firewire 800.

                I've raised it with Western-Digital support.

                Comment

                Working...
                X