CHKDSK logs for non-system drives

[Guest]

When I run CHKDSK on non-system drive (for system drive I have C), seems
like CHKDSK doesn't log check results in Event Viewer. Is there any way to
force CHKDSK to log it's activity for any drive?

 

[Kelly]

Hi,

Session Manager typically launches Chkdsk (autocheck.exe), which is
specified in the Session Manager's BootExecute value along with direction to
run other boot-time native applications. After Autocheck finishes Session
Manager starts Winlogon and the Win32 subsystem (CSRSS.EXE). Both of these
generate interleaved Registry accesses as they start up concurrently.
Winlogon can be seen querying the .Default key's display settings, including
colors and mouse settings under HKU\.Default\Control Panel. The .Default
key's contents are user preferences that are active when no one is logged
in, and Winlogon uses them for the screen on which it displays the logon
dialog box.

More info here:
http://www.sysinternals.com/Information/BootTimeRegistryActivity.html

Make note: The log files have a finite size, and the system overwrites
events according to the log's configuration options. Changes you make to the
configuration settings depend on your situation.

Suggestion:

Event Log Explorer (Line 375)
http://www.kellys-korner-xp.com/xp_tweaks.htm

Added info:

If Event Viewer reports on startup that one or more of your log files is
corrupt, you can remedy the situation as follows:

Disable the Event Log service by going to Start/Run: services.msc
Once done, restart Windows.

Delete the corrupt log(s)-Appevent.evt, Secevent.evt, and/or
Sysevent.evt-from %SystemRoot%\System32\Config (or wherever they may be).

Your existing event data will be lost, but a new log file will be created
when the service is restarted, and that log will start to accumulate new
events.

Reenable the Event Log service, and start the service.

If the Event Log service doesn't restart successfully, then restart Windows
XP.
Note: You cannot delete or rename the log files while the Event Log service
is running.


--

All the Best,
Kelly (MS-MVP)

Troubleshooting Windows XP
http://www.kellys-korner-xp.com

In memory of those lost during Katrina &
Prayers and Hope for the remaining displaced.

 

[Wesley Vogel]

Look for a Bootex.log in the root of non-system drive(s).



--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

 

[Guest]

Neither is working. I was unable to find Bootex.log file. I'll try to
rephrase my question. Every time CHKDSK runned no C drive, there is a log
entry in Event Viewer:

Small incostistincies was found and repaired (when errors are found,but that
is rare)
XX entries was removed in INDEX$ (not exact text, just for example)


Every time I CHKDSK any OTHER THAN C: disk (E; F; G) there are no entries
concerning this drives. All I want is the same logging as for C: .

Thanks in advance

 

[Wesley Vogel]

I thought that looking for Bootex.logs would be worth a shot.

Normally...
[[When Autochk runs against a volume at boot time it records its output to a
file called Bootex.log in the root of the volume being checked. The Winlogon
service then moves the contents of each Bootex.log file to the Application
Event log.]]

[[This file states whether Chkdsk encountered any errors and, if so,
whether they were fixed.]]

Bootex.log is then deleted. The Application Event log is AppEvent.Evt and
is viewed in the Event Viewer, under Application.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In