Tell me more ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.
up vote 5 down vote favorite

Is there a way to get the results of chkdsk with the /f switch to a .txt file instead of having to go to the event viewer?

EDIT: I want to get the output of what chkdsk fixed, not just what errors have been shown.

PS: Im using Windows XP.

share|improve this question

2 Answers

up vote 7 down vote

You can use redirection.

Run chkdsk over a command window(cmd):

  1. Click on Windows Start buttom / type "cmd" and open a new cmd window.

  2. Type the following comand(without the ""):

    "chkdsk > log.txt"

Then all the content shown on cmd output will be written to the log.txt file.

Here is the print screen of the results performed with this command at my system(Portuguese Windows version):

enter image description here

share|improve this answer
If the machine was on and running, and you run chkdsk /f in cmd, it will ask to restart the machine to run chkdsk. When you go to restart the machine, the session is killed. If I understand correctly, won't doing chkdsk >> log.txt only output the message prior to the actual chkdsk application running? – Mechaflash Aug 24 '11 at 18:16
On boot time you cannot schedule to pipe to a txt or even save the results, but you can add the command chkdsk > log.txt to a script and run it everytime you boot the system. – Diogo Aug 24 '11 at 18:26
1  
Sorry, I think I misunderstood your first comment. If you run chkdsk with /f argument it will ask you for schedule the chkdsk task to the next boot in order to correct defective clusters. chkdsk without arguments will verify your disk for errors and give a error report. If you got erros on report you can run /f argument, if dont, you can use chkdsk without arguments piping to the .txt log to see if there are errors, you will get the same information that would have if was on boot time. – Diogo Aug 24 '11 at 18:51
5  
Just a minor point on terminology, what you are demonstrating is 'output redirection' using the > operator, not strictly a pipe. A pipe is when the output of one program is used as the input to another, as in 'piped from one program to another' using the | operator. – w3d Aug 24 '11 at 19:05
1  
@Diogo_Rocha, it is /r, not /f that scans for bad clusters. – psusi Aug 24 '11 at 19:18
show 6 more comments
up vote 2 down vote accepted

I found where Windows XP stores the output of the chkdsk run on boot. It stores the output in C:\Bootex.log

http://support.microsoft.com/kb/218461

EDIT: On a side note. I'll share this with everyone

To automate chkdsk via batch file, you can use the following commands:

echo y|chkdsk /f
shutdown -r -t 00

then you can retrieve the Bootex.log from C:\ afterwards.

EDIT2: Not sure what the default behavior is but it seems that it is hit and miss with whether or not a bootex.log exists. I saw a post on another website stating that bootex.log is supposed to be erased before login, unless autochk.exe encounters an error or if autochk.exe is canceled before it is finished. But I've seen the log there without either conditions being met.

share|improve this answer
The link is broken("Sorry, but we couldn't find the page that you requested."). Can you verify if it is right? – Diogo Aug 24 '11 at 19:58
cut off a number at the end =/ it should work now – Mechaflash Aug 24 '11 at 20:14
and yes yes I know it says "IN windows 2000" but it still applies to windows xp. tested and found it with the output file after the system reboot. – Mechaflash Aug 24 '11 at 20:14

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.