Page 1 of 2 12 LastLast
Results 1 to 15 of 22
  1. #1
    Lounger
    Join Date
    Apr 2010
    Location
    Alabama
    Posts
    44
    Thanks
    1
    Thanked 2 Times in 2 Posts

    Exclamation File system structure on the disk is corrupt

    I recently checked my Event Viewer and found the following errors. This is repeated 14 times about 2 seconds apart about an hour after bootup. The error sounds serious but there does not seem to be any ill effects on performance. This is on the same drive that I replaced here http://windowssecrets.com/forums/sho...to-a-new-drive


    Code:
    Log Name:      System
    Source:        Ntfs
    Date:          3/27/2011 09:19:20
    Event ID:      55
    Task Category: (2)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      schuckman-desk
    Description:
    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume OS.
    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-03-27T14:19:20.101687300Z" />
        <EventRecordID>119127</EventRecordID>
        <Channel>System</Channel>
        <Computer>xxxxxxxx-desk</Computer>
        <Security />
      </System>
      <EventData>
        <Data>
        </Data>
        <Data>OS</Data>
        <Binary>00000C000200380002000000370004C000000000020100C000000000000000000000000000000000EE0C14002209000000000100</Binary>
      </EventData>
    </Event>
    OS: WIN7 Ultimate 64 bit
    Dell Studio XPS with 12 gig RAM and dual 1 TB drives.

    I ran chkdsk /f but the errors persist. Results (errors and warnings) of chkdsk are as follows:

    Cleaning up 848 unused index entries from index $SII of file 0x9.
    Cleaning up 848 unused index entries from index $SDH of file 0x9.
    Cleaning up 848 unused security descriptors.
    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.

    Should I be concerned or just ignore these errors?

  2. #2
    Super Moderator bbearren's Avatar
    Join Date
    Dec 2009
    Location
    Polk County, Florida
    Posts
    3,760
    Thanks
    26
    Thanked 424 Times in 338 Posts
    Try chkdsk /r

    /r implies /f, and attempts to recover any data.

    I would also make a drive image if the drive is rescusitated, and start saving up for a new drive...
    Last edited by bbearren; 2011-03-27 at 13:46.
    Create a fresh drive image before making system changes, in case you need to start over!

    "The problem is not the problem. The problem is your attitude about the problem. Savvy?"—Captain Jack Sparrow "When you're troubleshooting, start with the simple and proceed to the complex."—M.O. Johns "Experience is what you get when you're looking for something else."—Sir Thomas Robert Deware.
    Unleash Windows

  3. #3
    Lounger
    Join Date
    Apr 2010
    Location
    Alabama
    Posts
    44
    Thanks
    1
    Thanked 2 Times in 2 Posts
    Quote Originally Posted by bbearren View Post
    ...I would also make a drive image if the drive is rescusitated,...
    Not a problem making a drive image as the computer seems to be running fine, (not running slow or hanging up). If I wouldn't have reviewed the event log, I wouldn't have known I had a problem.

    On your advice from my last problem, I had already purchased a new drive, made an image and verified it booted OK. That new drive is not installed but is available for installation. I am in the process of running chkdsk /r but it will most likely take in excess of an hour to complete.

  4. #4
    Super Moderator bbearren's Avatar
    Join Date
    Dec 2009
    Location
    Polk County, Florida
    Posts
    3,760
    Thanks
    26
    Thanked 424 Times in 338 Posts
    Sounds like you have the situation well in hand.

    I have had chkdsk /r take a number of hours to complete on occaission. Just don't stop it; let it run to completion.
    Create a fresh drive image before making system changes, in case you need to start over!

    "The problem is not the problem. The problem is your attitude about the problem. Savvy?"—Captain Jack Sparrow "When you're troubleshooting, start with the simple and proceed to the complex."—M.O. Johns "Experience is what you get when you're looking for something else."—Sir Thomas Robert Deware.
    Unleash Windows

  5. #5
    Lounger
    Join Date
    Apr 2010
    Location
    Alabama
    Posts
    44
    Thanks
    1
    Thanked 2 Times in 2 Posts
    It took 3 hours to complete. No errors were found. Sure enough, 1 hour and twenty minutes after bootup, I got the same 14 errors. It does seem odd that the errors are not reported immediately. I wonder what runs 1 to 1 1/2 hours after boot to cause these errors?

  6. #6
    Super Moderator bbearren's Avatar
    Join Date
    Dec 2009
    Location
    Polk County, Florida
    Posts
    3,760
    Thanks
    26
    Thanked 424 Times in 338 Posts
    Quote Originally Posted by Steve1951 View Post
    It took 3 hours to complete. No errors were found. Sure enough, 1 hour and twenty minutes after bootup, I got the same 14 errors. It does seem odd that the errors are not reported immediately. I wonder what runs 1 to 1 1/2 hours after boot to cause these errors?
    Windows 7 by default has a number of tasks scheduled through the Task Scheduler; defrag is one of those. You might run though that list to see if anything is coming up within that time frame.

    I have deleted the defrag from Task Scheduler on my machine, since I prefer MyDefrag.
    Create a fresh drive image before making system changes, in case you need to start over!

    "The problem is not the problem. The problem is your attitude about the problem. Savvy?"—Captain Jack Sparrow "When you're troubleshooting, start with the simple and proceed to the complex."—M.O. Johns "Experience is what you get when you're looking for something else."—Sir Thomas Robert Deware.
    Unleash Windows

  7. #7
    Super Moderator bbearren's Avatar
    Join Date
    Dec 2009
    Location
    Polk County, Florida
    Posts
    3,760
    Thanks
    26
    Thanked 424 Times in 338 Posts
    It just occurred to me that you might give MyDefrag a run at your drive. One of the things MyDefrag does is relocate ordinary files out of the MFT. The NTFS file system can and will put ordinary data files in the MFT along with the metadata files that are normally filed there.

    MyDefrag removes these ordinary files and places them elsewhere on the disk, defrags the MFT and leaves only MFT-relevent files within the MFT.
    Create a fresh drive image before making system changes, in case you need to start over!

    "The problem is not the problem. The problem is your attitude about the problem. Savvy?"—Captain Jack Sparrow "When you're troubleshooting, start with the simple and proceed to the complex."—M.O. Johns "Experience is what you get when you're looking for something else."—Sir Thomas Robert Deware.
    Unleash Windows

  8. #8
    Lounger
    Join Date
    Apr 2010
    Location
    Alabama
    Posts
    44
    Thanks
    1
    Thanked 2 Times in 2 Posts
    It wasn't the defrag program. It runs 1 time per week and last executed 2 days ago.

    I plan to let the computer run for a couple of days (without rebooting) to see if the errors repeat. I'll check out MyDefrag.

    If all else fails, I can revert to the last image to the new drive. The only changes since the image have been the Microsoft patches.

  9. #9
    Lounger
    Join Date
    Apr 2010
    Location
    Alabama
    Posts
    44
    Thanks
    1
    Thanked 2 Times in 2 Posts
    I pulled out the current OS drive and installed the new drive that I had imaged last week and so far the system has been up for 7 hours with no ntfs errors. It was either the drive was physically bad or something was corrupted. I still get the CAPI2 errors, but those have been there for a few months.

    SFC /VERIFYONLY reports inconsistencies but I don't plan to execute the /SCANNOW option until I get another image completed. (The old drive also reported errors).

  10. #10
    Lounger
    Join Date
    Apr 2010
    Location
    Alabama
    Posts
    44
    Thanks
    1
    Thanked 2 Times in 2 Posts
    The ntfs errors are back. Fourteen in a row, just as before. This is with a different disk drive so it can't be the drive.

    Are there any "hidden" options that will tell me what program was executing when these errors are generated?
    Last edited by Steve1951; 2011-03-29 at 08:45.

  11. #11
    Super Moderator Deadeye81's Avatar
    Join Date
    Dec 2009
    Location
    North Carolina, USA
    Posts
    2,654
    Thanks
    7
    Thanked 113 Times in 97 Posts
    Hi Steve,

    You might consider running the SFC /SCANNOW option now to hopefully find and replace whatever system files that may be corrupt. I take it the image on your new disk was taken from the older disk Windows 7 installation, thus transferring the problem from the old disk to the new. If SFC does not correct the problem it may require a repair installation to fix the OS.

    In thinking of Windows 7 operations that run occasionally besides the defrag routine, I wonder about the Search Indexing Service. If Windows detects something wrong in the indexing, it may be starting up in an attempt to perform a fix. If you want to look at that possibility, go to Control Panel>Indexing Options, click the Advanced button and then the Rebuild button, which will delete and rebuild the index. There is also an option below Rebuild to relocate the index. Just a thought.

    Other possibilities could be corruption in the paging file or in the creation of restore points.

  12. #12
    2 Star Lounger
    Join Date
    Jun 2010
    Location
    philippines
    Posts
    185
    Thanks
    0
    Thanked 0 Times in 0 Posts
    You might want to download and install HD tune, I used it to look at the health status of my drives. http://www.hdtune.com/

  13. #13
    Super Moderator bbearren's Avatar
    Join Date
    Dec 2009
    Location
    Polk County, Florida
    Posts
    3,760
    Thanks
    26
    Thanked 424 Times in 338 Posts
    I would boot to the installation DVD, choose repair and open the command prompt. I would first run chkdsk /r to completion, and then I would run sfc /scannow to completion, both from the DVD repair option rather than from your hard drive.
    Create a fresh drive image before making system changes, in case you need to start over!

    "The problem is not the problem. The problem is your attitude about the problem. Savvy?"—Captain Jack Sparrow "When you're troubleshooting, start with the simple and proceed to the complex."—M.O. Johns "Experience is what you get when you're looking for something else."—Sir Thomas Robert Deware.
    Unleash Windows

  14. #14
    Lounger
    Join Date
    Apr 2010
    Location
    Alabama
    Posts
    44
    Thanks
    1
    Thanked 2 Times in 2 Posts
    Quote Originally Posted by bbearren View Post
    I would boot to the installation DVD, choose repair and open the command prompt. I would first run chkdsk /r to completion, and then I would run sfc /scannow to completion, both from the DVD repair option rather than from your hard drive.
    I'm curious as to why you are suggesting running from the installation DVD rather from the hard drive. I may give that a try.

    I have already performed a SFC /SCANNOW (executed from the hard drive). Here are the results:

    Code:
    Beginning system scan.  This process will take some time.
    
    Beginning verification phase of system scan.
    Verification 100% complete.
    Windows Resource Protection found corrupt files but was unable to fix some of them.
    Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
    C:\Windows\Logs\CBS\CBS.log

    I looked at the CBS.log file, but I'm not sure how to interpret the data.

    Also previously I performed a chkdsk /r and found no errors.

    I have also deleted and rebuilt the indexing file.

    I just finished implementing Microsoft KB2498472 but that did not fix the problem on the original drive. I'll need to wait for up to 12 hours before I can verify if this fixed the problem.

    Last edited by Steve1951; 2011-03-30 at 16:47.

  15. #15
    Super Moderator bbearren's Avatar
    Join Date
    Dec 2009
    Location
    Polk County, Florida
    Posts
    3,760
    Thanks
    26
    Thanked 424 Times in 338 Posts
    Quote Originally Posted by Steve1951 View Post
    I'm curious as to why you are suggesting running from the installation DVD rather from the hard drive. I may give that a try.
    When you boot from the DVD and select the Command Prompt, you are loading a complement of tools from the DVD into a RAM drive, bypassing any posssibly corrupted tools from the hard drive.
    Create a fresh drive image before making system changes, in case you need to start over!

    "The problem is not the problem. The problem is your attitude about the problem. Savvy?"—Captain Jack Sparrow "When you're troubleshooting, start with the simple and proceed to the complex."—M.O. Johns "Experience is what you get when you're looking for something else."—Sir Thomas Robert Deware.
    Unleash Windows

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •