Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Health Indicator RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I have gotten the "unhealthy" notice again on a WHS which I've not had that long.  Has this truly been linked to a bug or indicative of a real problem?  What's the probability of losing data when I run the "repair" option it's giving? 

    Here are the results from doing CHKDSK:




    Microsoft Windows [Version 5.2.3790]
    (C) Copyright 1985-2003 Microsoft Corp.

    C:\Documents and Settings\Administrator>CHKDSK
    The type of the file system is NTFS.
    Volume label is SYS.

    WARNING!  F parameter not specified.
    Running CHKDSK in read-only mode.

    CHKDSK is verifying files (stage 1 of 3)...
    47808 file records processed.
    File verification completed.
    76 large file records processed.
    0 bad file records processed.
    0 EA records processed.
    3 reparse records processed.
    CHKDSK is verifying indexes (stage 2 of 3)...
    157098 index entries processed.
    Index verification completed.
    5 unindexed files processed.
    CHKDSK is verifying security descriptors (stage 3 of 3)...
    47808 security descriptors processed.
    Security descriptor verification completed.
    3853 data files processed.
    CHKDSK is verifying Usn Journal...
    37013104 USN bytes processed.
    Usn Journal verification completed.

      20972825 KB total disk space.
       8105024 KB in 37451 files.
         11676 KB in 3854 indexes.
             0 KB in bad sectors.
        152613 KB in use by the system.
         65536 KB occupied by the log file.
      12703512 KB available on disk.

          4096 bytes in each allocation unit.
       5243206 total allocation units on disk.
       3175878 allocation units available on disk.

    C:\Documents and Settings\Administrator>


    ****************************



    D:\>CHKDSK
    The type of the file system is NTFS.
    Volume label is DATA.

    WARNING!  F parameter not specified.
    Running CHKDSK in read-only mode.

    CHKDSK is verifying files (stage 1 of 3)...
    655920 file records processed.
    File verification completed.
    129 large file records processed.
    0 bad file records processed.
    0 EA records processed.
    222980 reparse records processed.
    CHKDSK is verifying indexes (stage 2 of 3)...
    2314823 index entries processed.
    Index verification completed.
    5 unindexed files processed.
    CHKDSK is verifying security descriptors (stage 3 of 3)...
    655920 security descriptors processed.
    Security descriptor verification completed.
    173331 data files processed.
    CHKDSK is verifying Usn Journal...
    34192704 USN bytes processed.
    Usn Journal verification completed.
    Windows found problems with the file system.
    Run CHKDSK with the /F (fix) option to correct these.

     711591142 KB total disk space.
     344782760 KB in 454601 files.
        143816 KB in 173332 indexes.
             0 KB in bad sectors.
        777558 KB in use by the system.
         65536 KB occupied by the log file.
     365887008 KB available on disk.

          4096 bytes in each allocation unit.
     177897785 total allocation units on disk.
      91471752 allocation units available on disk.

    D:\>

     

    >

    • Edited by JSHollis Thursday, December 31, 2009 12:56 AM correction
    Wednesday, December 30, 2009 3:02 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    will try that.  If there is damage (which the CHKDSK results seem to report all clear on any sector errors) why does a reboot of the server make the yellow reporting go away?

    It would seem true damage could not be swept away by just rebooting to get a green light.


    • Marked as answer by JSHollis Saturday, February 13, 2010 4:25 PM
    Thursday, December 31, 2009 2:25 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Please make sure you check all the drives in your server for errors. Checking only C: and D: isn't sufficient if you have more than one drive installed. Reboot your server after all checks have completed, and don't be surprised if it takes a very long time to boot (as it will doubtless run the check and repair on C: on reboot). After your server has finished rebooting, you'll find the results in the Application event log on your server, source = winlogon.
    I'm not on the WHS team, I just post a lot. :)
    Wednesday, December 30, 2009 6:29 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    I only have a C and D drive.  What is the percentage of risk in running the repair function?
    Wednesday, December 30, 2009 7:25 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Do you have more than a single physical drive in your server? I seem to recall you posting in the past that you do. If so, use the batch file in the linked FAQ to run chkdsk against all of your drives. Also, I just noticed that both of those chkdsk reports are from the C: drive. You haven't even run it on D: yet...

    The risk in using the repair function is that chkdsk will find an uncorrectable error in a sector and you will lose data. If that happens, it's actually already happened (the uncorrectable error already exists) and you just don't know the extent of the problem yet. So if you'd rather, go ahead and use the repair function in the console (that's what you're talking about, I assume).

    I'm not on the WHS team, I just post a lot. :)
    Wednesday, December 30, 2009 7:35 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    I have a HP 485 single drive.  I am editing the above post with CHSKDSK results.  They were not from the server but from my desktop!    
    Thursday, December 31, 2009 12:50 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    heh. We've all had days like that. :)

    Use the repair function in the console on D:; hopefully that will take care of any problems on the drive.
    I'm not on the WHS team, I just post a lot. :)
    Thursday, December 31, 2009 1:25 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    will try that.  If there is damage (which the CHKDSK results seem to report all clear on any sector errors) why does a reboot of the server make the yellow reporting go away?

    It would seem true damage could not be swept away by just rebooting to get a green light.


    • Marked as answer by JSHollis Saturday, February 13, 2010 4:25 PM
    Thursday, December 31, 2009 2:25 AM