If you run chkdsk /f, does it leave a log of what it did? If so, what
is it?

I ran chkdsk yesterday and it just displayed something and I think it
left no log.

"Richard Fangnail" <(E-Mail Removed)> wrote in message
news:f144eabe-a405-4657-bacd-(E-Mail Removed)...
> If you run chkdsk /f, does it leave a log of what it did? If so, what
> is it?
>
> I ran chkdsk yesterday and it just displayed something and I think it
> left no log.

You will find the chkdsk log in the Event Viewer (eventvwr.exe).

On Jul 12, 3:15*pm, Richard Fangnail <richardfangn...@excite.com>
wrote:
> If you run chkdsk /f, does it leave a log of what it did? *If so, what
> is it?
>
> I ran chkdsk yesterday and it just displayed something and I think it
> left no log.

Also: I once booted from the Windows CDROM and it ran chkdsk.
However, I just did it again and I think it did not run chkdsk - do
you know how I could run it again?

Was I supposed to use safe mode?

On Jul 12, 3:19*pm, "Pegasus [MVP]" <n...@microsoft.com> wrote:
> "Richard Fangnail" <richardfangn...@excite.com> wrote in message
>
> news:f144eabe-a405-4657-bacd-(E-Mail Removed)...
>
> > If you run chkdsk /f, does it leave a log of what it did? *If so, what
> > is it?
>
> > I ran chkdsk yesterday and it just displayed something and I think it
> > left no log.
>
> You will find the chkdsk log in the Event Viewer (eventvwr.exe).

What part of the Event Viewer would have the log?
Mine has Appplication, System, Security and IE and I see no sign of a
chkdsk log.
Thanks

Richard Fangnail wrote:
> If you run chkdsk /f, does it leave a log of what it did? If so,
> what is it?
>
> I ran chkdsk yesterday and it just displayed something and I think
> it left no log.

Richard Fangnail wrote:
> Also: I once booted from the Windows CDROM and it ran chkdsk.
> However, I just did it again and I think it did not run chkdsk - do
> you know how I could run it again?
>
> Was I supposed to use safe mode?

Now is a great time to point you to one of the easiest ways to find
information on problems you may be having and solutions others have found:

Search using Google!
http://www.google.com/
(How-to: http://www.google.com/intl/en/help/basics.html )

Example:
http://www.google.com/search?q=%22Wi...%22+chkdsk+log

Hits (from the first/down) with your answer:
http://www.computing.net/answers/win...ts/132863.html
http://www.velocityreviews.com/forum...indows-xp.html
http://forums.techarena.in/windows-xp-support/42429.htm


Simplistic direct answer:
Start Button --> Run --> type in:
eventvwr.msc /s
--> Click OK.

When Event Viewer opens, click on "Application", then scroll
down to "Winlogon" and double-click on it. This should be the
log created after running CHKDSK.

As for your 'also' - what?

Please provide more details/insight into what it is you have done/are
trying to do and why...

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

Thanks, it took about 30 minutes and here is the result. Regarding
minor inconsistencies on the drive - are those things that could
actually cause problems or crashes of programs?

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 802 unused index entries from index $SII of file 0x9.
Cleaning up 802 unused index entries from index $SDH of file 0x9.
Cleaning up 802 unused security descriptors.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.

40146403 KB total disk space.
17897292 KB in 74275 files.
37388 KB in 6697 indexes.
0 KB in bad sectors.
152455 KB in use by the system.
65536 KB occupied by the log file.
22059268 KB available on disk.

4096 bytes in each allocation unit.
10036600 total allocation units on disk.
5514817 allocation units available on disk.

Richard Fangnail wrote:
> Thanks, it took about 30 minutes and here is the result. Regarding
> minor inconsistencies on the drive - are those things that could
> actually cause problems or crashes of programs?
>
> Checking file system on C:
> The type of the file system is NTFS.
>
> A disk check has been scheduled.
> Windows will now check the disk.
> Cleaning up minor inconsistencies on the drive.
> Cleaning up 802 unused index entries from index $SII of file 0x9.
> Cleaning up 802 unused index entries from index $SDH of file 0x9.
> Cleaning up 802 unused security descriptors.
> CHKDSK is verifying file data (stage 4 of 5)...
> File data verification completed.
> CHKDSK is verifying free space (stage 5 of 5)...
> Free space verification is complete.
>
> 40146403 KB total disk space.
> 17897292 KB in 74275 files.
> 37388 KB in 6697 indexes.
> 0 KB in bad sectors.
> 152455 KB in use by the system.
> 65536 KB occupied by the log file.
> 22059268 KB available on disk.
>
> 4096 bytes in each allocation unit.
> 10036600 total allocation units on disk.
> 5514817 allocation units available on disk.

I seldom find *anything* wrong with drives that are working properly.

If you have found anything - you may want to follow up with a hard disk
drive dignostics run with the utility found usually in the support/downloads
section of the manufacturer's (of your hard disk drive) web page.


--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

For your interest; CHKDSK is actually called on every boot (by default)
and, if a major file system error is detected, runs automatically before
Windows starts *without* you having to specify it to run on next boot.

(This auto-checking is as a result of a registry value called
"BootExecute" under the key :
"HKLM\System\CurrentControlSet\Control\Session Manager" )

If it runs in this way (automatically - without you having to ask it to)
then it *will* leave a logfile in the root of any drives checked called
: "BOOTEX.LOG"

Otherwise, as a few have said in this thread, the only log you will get
will be in the 'Event Viewer' under the 'Application' item with
'Winlogon' written in the 'source' column.

==

Cheers, Tim Meddick, Peckham, London. :-)




"Richard Fangnail" <(E-Mail Removed)> wrote in message
news:7387570c-f0f8-4143-887b-(E-Mail Removed)...
> Thanks, it took about 30 minutes and here is the result. Regarding
> minor inconsistencies on the drive - are those things that could
> actually cause problems or crashes of programs?
>
> Checking file system on C:
> The type of the file system is NTFS.
>
> A disk check has been scheduled.
> Windows will now check the disk.
> Cleaning up minor inconsistencies on the drive.
> Cleaning up 802 unused index entries from index $SII of file 0x9.
> Cleaning up 802 unused index entries from index $SDH of file 0x9.
> Cleaning up 802 unused security descriptors.
> CHKDSK is verifying file data (stage 4 of 5)...
> File data verification completed.
> CHKDSK is verifying free space (stage 5 of 5)...
> Free space verification is complete.
>
> 40146403 KB total disk space.
> 17897292 KB in 74275 files.
> 37388 KB in 6697 indexes.
> 0 KB in bad sectors.
> 152455 KB in use by the system.
> 65536 KB occupied by the log file.
> 22059268 KB available on disk.
>
> 4096 bytes in each allocation unit.
> 10036600 total allocation units on disk.
> 5514817 allocation units available on disk.
>