Running CHKDSK on external drive? Where is the log?
in [Windows XP]
|
Prev: turn off use of System Volume Information - SystemProperties.JPG (0/1)
Next: NVIDIA nForce Network Controler say "Cable not connected"
From: J Tinsby on 11 Jul 2010 09:43 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
From: Peter on 11 Jul 2010 10:26 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
From: J Tinsby on 12 Jul 2010 14:03 On Sun, 11 Jul 2010 16:26:15 +0200, Peter <nospam(a)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.
From: Peter on 12 Jul 2010 19:44 On 07/12/2010 08:03 PM, J Tinsby wrote: > On Sun, 11 Jul 2010 16:26:15 +0200, Peter<nospam(a)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
From: Mike S on 12 Jul 2010 21:15
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 |