Chkdsk Results

[joshuaW]

I am looking for my chkdsk results and can't find them. They are not placed in the application log on my system. In fact, an entry with the source Winlogon is not even created. Unfortunately, I am running this on a remote machine, so I do not have the luxury of watching the display.

I am looking for a log file that the results may be dumped in. Or, a reason that my machines are not showing the results in the event viewer. This isn't specific to one machine, it happens to the balance of my chain (close to 400 boxes)

Machine = Dell PowerEdge 840
Windows version = Server 2003, SP2


Any help would be appreciated... Josh

[Humberto]

Try this, it will create a chkdsk log.

Paste this into a command prompt...

CHKDSK C: /F > C:\CHKDISKLOG.TXT

Hit your Enter key.

Click YES on the popup to reboot.

After CHKDSK has run paste this in Start | Run...

C:\CHKDISKLOG.TXT

Click OK.

Main thing is that you should get past scans results

[karunakar]

You can either view the events in eventvwr, or 'without' correcting them, see what needs attention, if anything using:

chkdsk c: >> C:\Chkdsk.txt <Enter>

Check the contents of the text file

[Calvin K]

one thing to remember is that windows 2003's checkdisk puts the results in the event log, not in a text file -so be sure to check the log afterwards.

[Solomon]

There might be some error or virus running in your chkdsk application.
You can better uninstall and the delete that application and install the new one.There are many freeware chkdsk available.

Windows Mess Cleaner is a decent little tool that has the potential to clean quite a bit from your system. It offers you an expanded selection of cleanup choices including :
Temp Setup Files,
Downloaded Program Files,
Temp Internet Files,
Debug Dump Files,
Office Setup Files,
old Chkdsk files,
Recycle Bin,
Temp Remote Desktop Files,
Setup Log Files,
Temp Files,
WebClient temp files,
Catalog files.

[joshuaW]

Thanks Humberto, that is what I was looking for.

But it didn't exactly work correctly. It wrote to the log file until the system rebooted. After the reboot, it didn't write to the log. I am guessing it displayed it on the screen again.

It also didn't prompt me to reboot since the output was being placed in the log file. Once I looked at the log file I realized this. I simply pressed y at the pause in my command window and it scheduled it to run after the next reboot.


Anyways... thanks for all the help - Josh