Event Log says disk is corrupt and unreadable but WHS says all is ok RRS feed

  • Question

  • I'm getting three events like this (each with three different volume ids) :


    Source : Application Popup

    Event : 26

    Application popup: Windows - Corrupt File :

    The file or directory \System Volume Information\{b6b2371b-76a0-11dc-8e46-0016e6dd0f20}{3808876b-c176-4e48-b7ae-04046e6cc752} is corrupt and unreadable. Please run the Chkdsk utility.


    Followed by :


    Source : ntfs

    Event : 26

    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume DATA.


    I've three physical disks - one D: "DATA" and two with no drive letter "DATA"s.


    The WHS console says everything is fine - Network ok, storage ok etc.


    I've run Server Storage Diagnostics from the just released Toolkit and that hasn't come up with any errors as far as I can see (though it may be a case of a needle in a haystack as the output is pretty vast).


    Why does the WHS console says everything is fine when the event log looks so bad ?


    How can I find out which drive the errors are related to ?


    Is it safe to assign drive letters to the pool "DATA" drives and run chkdsk or will it break things ?

    Wednesday, October 10, 2007 8:24 AM