Error-Checking (2002 SP1)

Topic

New Reply

Ran “Error-Checking” and it started on reboot. Nice to see they finally figured out a way to get what was called scandisk to run uninterrupted. But upon completion, the system just booted with no results message. Where do I find the results? There must be a log somewhere. TIA, J

Reply | Quote

Replies

No log created that I’ve ever been aware of.

Browse through this thread for some ideas…

Reply | Quote

The log file for chkdsk is displayed in the Event Viewer under “System Events”. To open the Event Viewer go to
Control Panel>Performance and Maintenance> Administrative Tools>Event Viewer.

Oana

Reply | Quote

I had been wondering the same thing as “jaylin” and was awaiting a reply. Your’s seem to provide some inkling but when I went searching in the Event Viewer I could not find anything showing the scan results. Interestingly enough, when I did the scandisk, the results flashed ever so briefly on the screen but the boot process cleared the screen pretty fast.

Any other clues?

Cheers,

Reply | Quote

Errors that have been fixed should show up in Event Viewer as Oana said and they are listed in the Applications section under Autochk. Put “eventvwr.msc” in the run box (no quotes)>(or Programs>Adm. Tools>Event Viewer)>Application>Scroll>Look for Autochk. under Source.

SMBP

Reply | Quote

Errors that have been fixed should show up in Event Viewer as Oana said and they are listed in the Applications section under Autochk. Put “eventvwr.msc” in the run box (no quotes)>(or Programs>Adm. Tools>Event Viewer)>Application>Scroll>Look for Autochk. under Source.

SMBP

Reply | Quote

By the way, what would 2002 be? Whistler ?

I assumed that Error Checker was run on an NTFS partitioned disk. In this case, the old chkdsk is used, and the Event Viewer shows you the results in a more “user-friendly” style (see Attachment, right pane). You can run it also from the command prompt, by typing chkdsk c: /f or, if you want the results written to a file, chkdsk c: /f > c:chkdsk.txt.

Scandisk was used in Windows98 on FAT32-partitioned disks, where scandisk.ini let you choose if you wanted a log file and even customize scandisk.log, by setting SaveLog = Append (appending the log to the previous log, if any), SaveLog = Off (thus not saving the repair log) or SaveLog = Overwrite (replacing the previous log with the new log).

Hope I didn’t confuse you, I’m pretty much confused myself as it’s way past my bedtime,
Oana

Reply | Quote

By the way, what would 2002 be? Whistler ?

I assumed that Error Checker was run on an NTFS partitioned disk. In this case, the old chkdsk is used, and the Event Viewer shows you the results in a more “user-friendly” style (see Attachment, right pane). You can run it also from the command prompt, by typing chkdsk c: /f or, if you want the results written to a file, chkdsk c: /f > c:chkdsk.txt.

Scandisk was used in Windows98 on FAT32-partitioned disks, where scandisk.ini let you choose if you wanted a log file and even customize scandisk.log, by setting SaveLog = Append (appending the log to the previous log, if any), SaveLog = Off (thus not saving the repair log) or SaveLog = Overwrite (replacing the previous log with the new log).

Hope I didn’t confuse you, I’m pretty much confused myself as it’s way past my bedtime,
Oana

Reply | Quote

I went looking for a good explanation of how chdksk writes to log files, and didn’t find much. Of 15-20 of the MSKBs referencing chkdsk in XP and 2K, this one has some info on how the info is transfered to Event Viewer at the bottom under “Note,” and often you will run it and there may not be any actual repairs which may explain the absense of entries. Much of that rapid data you see flashing on your screen is chkdsk carrying out the processes in the second link, and the Technet “sync toc” on the left.

218461: Description of Enhanced Chkdsk, Autochk, and Chkntfs Tools in Windows 2000

The Chkdsk Process on NTFS Volumes

I prefer to run chkdsk /r from the Recovery Console because I think it has the most efficacy there, and that switch implies /f and /p.

SMBP

Reply | Quote

I went looking for a good explanation of how chdksk writes to log files, and didn’t find much. Of 15-20 of the MSKBs referencing chkdsk in XP and 2K, this one has some info on how the info is transfered to Event Viewer at the bottom under “Note,” and often you will run it and there may not be any actual repairs which may explain the absense of entries. Much of that rapid data you see flashing on your screen is chkdsk carrying out the processes in the second link, and the Technet “sync toc” on the left.

218461: Description of Enhanced Chkdsk, Autochk, and Chkntfs Tools in Windows 2000

The Chkdsk Process on NTFS Volumes

I prefer to run chkdsk /r from the Recovery Console because I think it has the most efficacy there, and that switch implies /f and /p.

SMBP

Reply | Quote

I had been wondering the same thing as “jaylin” and was awaiting a reply. Your’s seem to provide some inkling but when I went searching in the Event Viewer I could not find anything showing the scan results. Interestingly enough, when I did the scandisk, the results flashed ever so briefly on the screen but the boot process cleared the screen pretty fast.

Any other clues?

Cheers,

Reply | Quote

Thanks, got it. Shows up under the Winlogin event.

Reply | Quote

Thanks, got it. Shows up under the Winlogin event.

Reply | Quote