Announcement

Collapse
No announcement yet.

File System Corrupt? Unlikely...

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

  • File System Corrupt? Unlikely...

    Hi, folks

    One of our domain controllers uses Windows Server 2008 Standard Edition installed on a Dell PowerEdge R410. The machine has two drives in RAID 1, set up by Dell.

    I have scheduled a system state backup to run every 12 hours. This runs a cmd file that contains the following:

    wbadmin start systemstatebackup -backuptarget: -quiet

    The system state backup runs fine and I have no problems with that. However, the System Log occassionally contains eventid 55 stating that chkdsk needs to be run as follows:

    Code:
    Log Name:      System
    Source:        Ntfs
    Date:          01/01/2011 06:12:42
    Event ID:      55
    Task Category: (2)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Phobos.htlincs.local
    Description:
    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume .
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Ntfs" />
        <EventID Qualifiers="49156">55</EventID>
        <Level>2</Level>
        <Task>2</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2011-01-01T06:12:42.939Z" />
        <EventRecordID>41870</EventRecordID>
        <Channel>System</Channel>
        <Computer>Phobos.htlincs.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>
        </Data>
        <Data>
        </Data>
        <Binary>0D000C000200380002000000370004C000000000020100C000000000000000000000000000000000BB0117000300000000000300</Binary>
      </EventData>
    </Event>
    and

    Code:
    Log Name:      System
    Source:        Ntfs
    Date:          31/12/2010 18:12:49
    Event ID:      55
    Task Category: (2)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Phobos.htlincs.local
    Description:
    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume VHD.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Ntfs" />
        <EventID Qualifiers="49156">55</EventID>
        <Level>2</Level>
        <Task>2</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2010-12-31T18:12:49.517Z" />
        <EventRecordID>41834</EventRecordID>
        <Channel>System</Channel>
        <Computer>Phobos.htlincs.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>
        </Data>
        <Data>VHD</Data>
        <Binary>0D000C000200380002000000370004C000000000020100C0000000000000000000000000000000007E0C14000900000000000900</Binary>
      </EventData>
    </Event>
    When these errors are logged, they coincide with the system state backup. They have only been logged with 10 backups in the last 6 months since I scheduled the task. Usually, four entries are logged with the same date/time - nothing is different apart from the volume identifier.

    I have no idea why they state '... run the chkdsk utility on the volume VHD.' and '... run the chkdsk utility on the volume .'

    I have had a look at a similar request that was not resolved here. The link provided would not seem pertinent to my setup.

    The system is 7 months old and I regularly monitor the logs. The system works fine without any issues. No other events relating to hardware issues are logged.

    I guess I must be missing something. Can someone help me understand this, please?

    Thanks!
    A recent poll suggests that 6 out of 7 dwarfs are not happy

  • #2
    Re: File System Corrupt? Unlikely...

    Hi,

    is there a log generated for your system state backup. May be we can co relate them with events generated
    meanwhile
    can you try running chkdsk /R (just in case)
    try sfc /scannow : to check if there is any system file corruption

    additionally
    Empty you recycle bin and run disk cleanup
    Thanks & Regards
    v-2nas

    MCTS 2008, MCTIP, MCSE 2003, MCSA+Messaging E2K3, MCP, E2K7
    Sr. Wintel Eng. (Investment Bank)
    Independent IT Consultant and Architect
    Blog: http://www.exchadtech.blogspot.com

    Show your appreciation for my help by giving reputation points

    Comment


    • #3
      Re: File System Corrupt? Unlikely...

      Thanks, v-2nas

      I will run chkdsk out of hours.

      What I did not understand was why a drive was not listed. The messages report that chkdsk should be run on

      volume (blank space)

      and

      volume VHD

      Rather than 'volume C' etc

      The log files only go back a couple of days so I don't have one for when event 55 was last logged (Jan 1) but the next time this happens I'll check it out.
      A recent poll suggests that 6 out of 7 dwarfs are not happy

      Comment


      • #4
        Re: File System Corrupt? Unlikely...

        Just running the chkdsk is the safest option - probbaly nothing wrong, but hopefully it'll away the message
        Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

        Comment


        • #5
          Re: File System Corrupt? Unlikely...

          Thanks

          I ran chkdsk last night and it made some changes:

          Code:
          Checking file system on C:
          The type of the file system is NTFS.
          Volume label is OS.
          
          A disk check has been scheduled.
          Windows will now check the disk.                         
          Cleaning up instance tags for file 0x247.
          Cleaning up instance tags for file 0x108f6.
            142400 file records processed.                                    257 large file records processed.                              0 bad file records processed.                                0 EA records processed.                                      78 reparse records processed.                                 169864 index entries processed.                                   0 unindexed files processed.                                 142400 security descriptors processed.                          Cleaning up 4405 unused index entries from index $SII of file 0x9.
          Cleaning up 4405 unused index entries from index $SDH of file 0x9.
          Cleaning up 4405 unused security descriptors.
            13733 data files processed.                                    CHKDSK is verifying Usn Journal...
            537314160 USN bytes processed.                                     Usn Journal verification completed.
          CHKDSK is verifying file data (stage 4 of 5)...
            142384 files processed.                                         File data verification completed.
          CHKDSK is verifying free space (stage 5 of 5)...
            5467322 free clusters processed.                                 Free space verification is complete.
          CHKDSK discovered free space marked as allocated in the
          master file table (MFT) bitmap.
          CHKDSK discovered free space marked as allocated in the volume bitmap.
          Windows has made corrections to the file system.
          
            41943039 KB total disk space.
            19296944 KB in 64852 files.
               38764 KB in 13734 indexes.
                   0 KB in bad sectors.
              738039 KB in use by the system.
               65536 KB occupied by the log file.
            21869292 KB available on disk.
          
                4096 bytes in each allocation unit.
            10485759 total allocation units on disk.
             5467323 allocation units available on disk.
          I have to admit that most of it is gobbledegook to me, but, as tehcamel says, hopefully these events will not recur.

          Still, if anyone knows why the volume is labelled [blank] and [VHD] I'd be grateful if you could post.

          Cheers!
          A recent poll suggests that 6 out of 7 dwarfs are not happy

          Comment

          Working...
          X