Where is log file for chkdsk for Windows XP?

Discussion in 'Computer Support' started by Rocky, Jul 9, 2003.

  1. Rocky

    Rocky Guest

    Supposedly chkdsk writes to a log file but I cannot find it. If I run
    chkdsk /L it reports that this log file is 65536 KB in size but it is
    nowhere to be found. How do you view it.

    Rocky, Jul 9, 2003
    1. Advertisements

  2. Rocky

    Rocky Guest

    Tried that and still cannot find it?
    Rocky, Jul 9, 2003
    1. Advertisements

  3. Rocky

    Rocky Guest

    Well thats just it. The screen showed a bad cluster and that chkdsk
    was correcting it by moving a file and then it said that said cluster
    was going to be logged in the "bad cluster file". I ran chkdsk /f
    again and the error was gone. I just want to look at the darn log file
    as it is supposed to have logged everything including previous scans I
    assume. Where is it hiding? I even tried looking in the registry to no

    Rocky, Jul 9, 2003
  4. Rocky

    Shep© Guest

    Shep©, Jul 9, 2003
  5. Rocky

    Rocky1138 Guest

    Thanks I found it in the event viewer under the Winlogon as the
    article said.

    Here is what happened:

    Event Type: Information
    Event Source: Winlogon
    Event Category: None
    Event ID: 1001
    Date: 7/9/2003
    Time: 11:43:17 AM
    User: N/A
    Computer: WINDOWSXP
    Checking file system on C:
    The type of the file system is NTFS.
    Volume label is CHEETAH.

    A disk check has been scheduled.
    Windows will now check the disk.
    Cleaning up minor inconsistencies on the drive.
    Cleaning up 34 unused index entries from index $SII of file 0x9.
    Cleaning up 34 unused index entries from index $SDH of file 0x9.
    Cleaning up 34 unused security descriptors.
    CHKDSK is verifying file data (stage 4 of 5)...
    Read failure with status 0xc000009c at offset 0x582c5ca00 for 0x10000
    Read failure with status 0xc000009c at offset 0x582c66200 for 0x200
    Windows replaced bad clusters in file 121
    of name \WINNT\MEMORY.DMP.
    File data verification completed.
    CHKDSK is verifying free space (stage 5 of 5)...
    Free space verification is complete.
    Adding 1 bad clusters to the Bad Clusters File.
    Correcting errors in the Volume Bitmap.
    Windows has made corrections to the file system.

    28290433 KB total disk space.
    27244554 KB in 56921 files.
    18524 KB in 3876 indexes.
    0 KB in bad sectors.
    135639 KB in use by the system.
    65536 KB occupied by the log file.
    891715 KB available on disk.

    512 bytes in each allocation unit.
    56580866 total allocation units on disk.
    1783430 allocation units available on disk.

    Windows has finished checking your disk.
    Please wait while your computer restarts.

    Now my question is this. What happened the bad cluster? Once it is
    marked bad is it then ignored on subsequent test thereby causing later
    test to report no bad clusters, if so how do you clear the cluster for
    retesting and recovery? I know scandisk for win98 is notorious for
    marking good clusters bad when in fact often they are ok. It is then
    possible to clear them and retest to be sure. Chkdsk said it added one
    bad cluster to the "Bad Clusters File".... Well where is that one?
    Note that in the final summary that chkdsk reported 0 KB in bad
    sectors. How do I find out the meaning of the read failure with status
    0xc0000009c return code?

    Thanks for the help. I am just trying to get to the bottom of this.

    Rocky1138, Jul 10, 2003
  6. Rocky

    Shep© Guest

    I turn off the memory dump in XP.Not found a use for it :/
    Shep©, Jul 10, 2003
  7. Rocky

    Ron Martell Guest

    Drives are built with a number of spare clusters. Normally the drive
    firmware will automatically substitute a spare cluster for one that is
    found bad and the process will be totally transparent to the user.

    I am not certain if that scenario comes into play with the XP version
    of CHKDSK or not.

    In any event, with a reported instance of a bad cluster I would
    immediately put the entire drive onto the suspect list and proceed
    accordingly. Bad sectors are very often a indicator of the pending
    failure of the drive.

    Specifically I would make certain that I always had a current backup
    of everything important on the drive. I would also make sure that
    S.M.A.R.T. monitoring was active in the computer BIOS. And finally I
    would download the diagnostic utility from the hard drive
    manufacturer's web site and run it.

    Good luck

    Ron Martell Duncan B.C. Canada
    Microsoft MVP
    On-Line Help Computer Service

    "The reason computer chips are so small is computers don't eat much."
    Ron Martell, Jul 10, 2003
  8. Rocky

    Rocky Guest

    I ran Seagate's Seatools diagnostics several times and there is
    nothing wrong with the drive. It may have been a controller glitch or
    more likely the usual unreliability of Microsoft software. At this
    time I am trying to figure out how to clear and/or retest the marked
    bad sector. The file I have found out to be the "bad cluster file" is
    $BadClus and is a hidden file that is part of the metafile group. In
    Windows XP I can't seem to find a way to view it, even in the command
    prompt. Does anybody know how to edit this file and clear the bad
    sector? I may start another thread asking about clearing and retesting
    a bad sector in Windows XP with NTFS. The determination of a bad
    sector is at the whim of the Windows XP operating system (chkdsk) and
    not at the hard disks level and its management scheme.

    Rocky, Jul 10, 2003
  9. Rocky


    May 13, 2009
    Likes Received:
    what about "CHKDSK <Volume:> /R"?. Always have a look at "<command> /?"!
    hacklestone, May 13, 2009
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.