1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Running CHKDSK on external drive? Where is the log?

Discussion in 'Windows XP' started by J Tinsby, Jul 11, 2010.

  1. J Tinsby

    J Tinsby Flightless Bird

    Hello all,

    I ran CHKDSK on my 1TB external drive and went to look for a WINLOGON
    log file for that program but there wasn't one for the day I ran the
    test.

    Although it took forever, it appeared everything was running in
    CHKDSK. I was surprised to see it run from Windows and not the blue
    DOS screen I usually get on the C:/ drive..

    Why don't I get a log for this test of the external drive?

    Thank you,

    J Tinsby
     
  2. Peter

    Peter Flightless Bird

    On 07/11/2010 03:43 PM, J Tinsby wrote:
    > I was surprised to see it run from Windows and not the blue
    > DOS screen I usually get on the C:/ drive..


    Think of trying to saw off a tree's branch while you're sitting on it.

    --
    Peter
     
  3. J Tinsby

    J Tinsby Flightless Bird

    On Sun, 11 Jul 2010 16:26:15 +0200, Peter <nospam@nospam.com.invalid>
    wrote:

    >On 07/11/2010 03:43 PM, J Tinsby wrote:
    >> I was surprised to see it run from Windows and not the blue
    >> DOS screen I usually get on the C:/ drive..

    >
    >Think of trying to saw off a tree's branch while you're sitting on it.


    Peter,

    Thank you so much for the wealth of information you provided, it's
    nice to know there are smart asses in every group no matter what the
    topic.

    I hope someday I can repay your kindness by letting you sit under the
    falling branch.
     
  4. Peter

    Peter Flightless Bird

    On 07/12/2010 08:03 PM, J Tinsby wrote:
    > On Sun, 11 Jul 2010 16:26:15 +0200, Peter<nospam@nospam.com.invalid>
    > wrote:
    >
    >> On 07/11/2010 03:43 PM, J Tinsby wrote:
    >>> I was surprised to see it run from Windows and not the blue
    >>> DOS screen I usually get on the C:/ drive..

    >>
    >> Think of trying to saw off a tree's branch while you're sitting on it.

    >
    > Peter,
    >
    > Thank you so much for the wealth of information you provided, it's
    > nice to know there are smart asses in every group no matter what the
    > topic.
    >
    > I hope someday I can repay your kindness by letting you sit under the
    > falling branch.
    >


    Sigh, C: the branch you're sitting on. D: another branch. Get it now?

    --
    Peter
     
  5. Mike S

    Mike S Flightless Bird

    On 7/11/2010 6:43 AM, J Tinsby wrote:
    > Hello all,
    >
    > I ran CHKDSK on my 1TB external drive and went to look for a WINLOGON
    > log file for that program but there wasn't one for the day I ran the
    > test.
    >
    > Although it took forever, it appeared everything was running in
    > CHKDSK. I was surprised to see it run from Windows and not the blue
    > DOS screen I usually get on the C:/ drive..
    >
    > Why don't I get a log for this test of the external drive?
    >
    > Thank you,
    >
    > J Tinsby


    http://www.technologyquestions.com/technology/windows-xp/176163-chkdsk-output-logs.html

    If you run chkdsk without any of the switches that require the volume to
    be locked or unmounted, you can just pipe the output to a text file:

    chkdsk > C:/checkdisklog.txt

    Because you won't see any output, you'll need to wait (in a Command
    Prompt window) until you see the command prompt reappear.

    If you run chkdsk with the /f or /r switches, the volume must be locked.
    Because the system is using the volume (assuming that you're checking
    the partition on which Windows is installed), it can't be locked, so
    chkdsk offers to run at the next reboot. If you OK this, what happens
    is that a module named autochk.exe is scheduled to run at the next
    restart. See http://support.microsoft.com/kb/314835/en-us which
    includes the following:

    <quote>
    However, if CHKDSK is scheduled to run when the computer restarts, the
    binary module that contains the verification code is Autochk.exe, a
    native Windows program. Because Autochk.exe runs early in the computer's
    startup sequence, Autochk.exe does not have the benefit of virtual
    memory or of other Win32 services.

    Autochk.exe generates the same kind of text output that the Chkdsk.exe
    utility DLLs generate. Autochk.exe displays this text output during the
    startup process and also logs an event in the application event log. The
    logged event information includes as much of the text output as can fit
    into the event log's data buffer.
    </quote>

    So, look in Event Viewer Application log for the first event after the
    reboot. The "source" will be "Winlogon" and have Event No. 1001.

    This KB article, although written for Win2K, may also be of interest:
    http://support.microsoft.com/kb/218461

    --
    Lem -- MS-MVP - Networking
     
  6. J Tinsby

    J Tinsby Flightless Bird

    Hello Lem,

    Thanks for the reply to my question. I didn't run chkdsk from a
    command prompt with any of the switches you recommend. That explains
    why I didn't get a log file from it.

    Thank you,

    J Tinsby

    >
    >http://www.technologyquestions.com/technology/windows-xp/176163-chkdsk-output-logs.html
    >
    >If you run chkdsk without any of the switches that require the volume to
    >be locked or unmounted, you can just pipe the output to a text file:
    >
    >chkdsk > C:/checkdisklog.txt
    >
    >Because you won't see any output, you'll need to wait (in a Command
    >Prompt window) until you see the command prompt reappear.
    >
    >If you run chkdsk with the /f or /r switches, the volume must be locked.
    >Because the system is using the volume (assuming that you're checking
    >the partition on which Windows is installed), it can't be locked, so
    >chkdsk offers to run at the next reboot. If you OK this, what happens
    >is that a module named autochk.exe is scheduled to run at the next
    >restart. See http://support.microsoft.com/kb/314835/en-us which
    >includes the following:
    >
    ><quote>
    >However, if CHKDSK is scheduled to run when the computer restarts, the
    >binary module that contains the verification code is Autochk.exe, a
    >native Windows program. Because Autochk.exe runs early in the computer's
    >startup sequence, Autochk.exe does not have the benefit of virtual
    >memory or of other Win32 services.
    >
    >Autochk.exe generates the same kind of text output that the Chkdsk.exe
    >utility DLLs generate. Autochk.exe displays this text output during the
    >startup process and also logs an event in the application event log. The
    >logged event information includes as much of the text output as can fit
    >into the event log's data buffer.
    ></quote>
    >
    >So, look in Event Viewer Application log for the first event after the
    >reboot. The "source" will be "Winlogon" and have Event No. 1001.
    >
    >This KB article, although written for Win2K, may also be of interest:
    >http://support.microsoft.com/kb/218461
     
  7. Jose

    Jose Flightless Bird

    On Jul 14, 5:51 pm, J Tinsby <n...@present.com> wrote:
    > Hello Lem,
    >
    > Thanks for the reply to my question. I didn't run chkdsk from a
    > command prompt with any of the switches you recommend. That explains
    > why I didn't get a log file from it.
    >
    > Thank you,
    >
    > J Tinsby
    >
    >
    >
    > >http://www.technologyquestions.com/technology/windows-xp/176163-chkds...

    >
    > >If you run chkdsk without any of the switches that require the volume to
    > >be locked or unmounted, you can just pipe the output to a text file:

    >
    > >chkdsk > C:/checkdisklog.txt

    >
    > >Because you won't see any output, you'll need to wait (in a Command
    > >Prompt window) until you see the command prompt reappear.

    >
    > >If you run chkdsk with the /f or /r switches, the volume must be locked.
    > >Because the system is using the volume (assuming that you're checking
    > >the partition on which Windows is installed), it can't be locked, so
    > >chkdsk offers to run at the next reboot. If you OK this, what happens
    > >is that a module named autochk.exe is scheduled to run at the next
    > >restart. Seehttp://support.microsoft.com/kb/314835/en-uswhich
    > >includes the following:

    >
    > ><quote>
    > >However, if CHKDSK is scheduled to run when the computer restarts, the
    > >binary module that contains the verification code is Autochk.exe, a
    > >native Windows program. Because Autochk.exe runs early in the computer's
    > >startup sequence, Autochk.exe does not have the benefit of virtual
    > >memory or of other Win32 services.

    >
    > >Autochk.exe generates the same kind of text output that the Chkdsk.exe
    > >utility DLLs generate. Autochk.exe displays this text output during the
    > >startup process and also logs an event in the application event log. The
    > >logged event information includes as much of the text output as can fit
    > >into the event log's data buffer.
    > ></quote>

    >
    > >So, look in Event Viewer Application log for the first event after the
    > >reboot. The "source" will be "Winlogon" and have Event No. 1001.

    >
    > >This KB article, although written for Win2K, may also be of interest:
    > >http://support.microsoft.com/kb/218461


    When chkdsk runs automatically on a reboot because XP thinks it needs
    to or you told it to do so, the results are shown in the Event Viewer
    Application log. You need to look there for problems after running
    chkdsk /r.

    To see the Event Viewer logs, click Start, Settings, Control Panel,
    Administrative Tools, Event Viewer.

    A shortcut to Event Viewer is to click Start, Run and in the box
    enter:

    %SystemRoot%\system32\eventvwr.msc

    Click OK to launch the Event Viewer.

    Look in the Application log for an event sourced by Winlogon,
    something like:

    Event Type: Information

    Event Source: Winlogon

    Event Category: None

    Event ID: 1001

    Description:

    Checking file system on C:

    The type of the file system is NTFS.
    A disk check has been scheduled.
    Windows will now check the disk.
    39070048 KB total disk space.
    25151976 KB in 78653 files.
    48256 KB in 10264 indexes.
    0 KB in bad sectors.
    237080 KB in use by the system.
    65536 KB occupied by the log file.
    13632736 KB available on disk.
    Windows has finished checking your disk.
     

Share This Page