Bert said:
XP Pro SP3
Had a power failure last night when both PCs were on, so I ran CHKDSK /F
on all drives, and had to have boot-time checks done on the system
drives.
I looked in the obvious places in \WINDOWS and \WINDOWS\SYSTEM, but
didn't find any logfile.
Anybody know where to find it, if there is one?
[If I'd been thinking more than 5 minutes ahead, I should have done a
CHKDSK /F on the system drives while the machines were up and simply
noted the output before rebooting, but I was too clever for that]
I only know of (but never needed) the event that gets recorded in the
Event Viewer. Open Event Viewer and look under the Application Logs for
WinLogon events. Find a WinLogon event with number 1001. I don't have
an example to see if the info recorded for that event is useful or not.
The following is what I've read. If chkdsk is ran at boot time or from
the recovery console, it creates a bootex.log file in the root folder of
the scanned drive. If there were errors found and corrected that you
click on the "More Info" link to see if it says something like "xxMB
occupied by log file". Alas, this log file is deleted if chkdsk is ran
at boot time and it completes without interruption. So unless you
interrupted a boot-time chkdsk then you won't have a log file. If you
boot into the Recovery Console mode and run chkdsk then the bootex.log
file remains. The log file says nothing about any errors found in
UNallocated space.
See:
http://www.microsoft.com/technet/su...790.1830&EvtID=1001&EvtSrc=Winlogon&LCID=1033
(shorturl:
http://preview.tinyurl.com/nkq7ca2)
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/chkdsk.mspx
There is no command-line switch to pipe chkdsk's stdout to a file.
Unless you interrupt the boot-time chkdsk or run it from the Recovery
Console, you're stuck with whatever gets recorded in Event Viewer.
Since you don't get to define the startup command for autochk, you
cannot pipe chkdsk's output to a file. Unless you run it yourself and
pipe its output to a file, you won't have a log of what happened. I'm
assuming its stdout can be piped into a file. Since I'm interactively
running chkdsk, I see its output in the console and don't need to pipe
its output. If I have to reboot Windows to run it (because it's the OS
partition on which it runs) then I sit there and watch the output and
get ready to hit the Pause key when it is done so its console doesn't
disappear.
Hopefully the event recorded in Event Viewer tells you something.
