• Welcome to Tux Reports: Where Penguins Fly. We hope you find the topics varied, interesting, and worthy of your time. Please become a member and join in the discussions.

Can't find chkdsk log files

A

Allen

Flightless Bird
I have run chkdsk twice and I have been unable to find the log files
that should have been generated. I know that errors were detected on one
of the runs, and I would really like to see the details.
Allen.
 
D

Dave-UK

Flightless Bird
"Allen" <allent@austin.rr.com> wrote in message
news:ttCdnea7ALpUH-PWnZ2dnUVZ_j6dnZ2d@giganews.com...
> I have run chkdsk twice and I have been unable to find the log files that should have been
> generated. I know that errors were detected on one of the runs, and I would really like to see the
> details.
> Allen.


The log appears, as Chkdsk, in Event Viewer > Windows Logs > Application.
Right-click, Copy, 'Copy details as text' and paste into a text document.
 
A

Allen

Flightless Bird
On 2/19/2010 11:08 AM, Dave-UK wrote:
>
> "Allen" <allent@austin.rr.com> wrote in message
> news:ttCdnea7ALpUH-PWnZ2dnUVZ_j6dnZ2d@giganews.com...
>> I have run chkdsk twice and I have been unable to find the log files
>> that should have been generated. I know that errors were detected on
>> one of the runs, and I would really like to see the details.
>> Allen.

>
> The log appears, as Chkdsk, in Event Viewer > Windows Logs > Application.
> Right-click, Copy, 'Copy details as text' and paste into a text document.
>
>
>

Thanks, Dave. You always come through.
Allen
 
O

Ophelia

Flightless Bird
"Allen" <allent@austin.rr.com> wrote in message
news:Y6qdnbXzhL8kWuPWnZ2dnUVZ_qhi4p2d@giganews.com...
> On 2/19/2010 11:08 AM, Dave-UK wrote:
>>
>> "Allen" <allent@austin.rr.com> wrote in message
>> news:ttCdnea7ALpUH-PWnZ2dnUVZ_j6dnZ2d@giganews.com...
>>> I have run chkdsk twice and I have been unable to find the log files
>>> that should have been generated. I know that errors were detected on
>>> one of the runs, and I would really like to see the details.
>>> Allen.

>>
>> The log appears, as Chkdsk, in Event Viewer > Windows Logs > Application.
>> Right-click, Copy, 'Copy details as text' and paste into a text document.
>>
>>
>>

> Thanks, Dave. You always come through.


Yes, he does:)

--
--
https://www.shop.helpforheroes.org.uk/
 
D

Dave-UK

Flightless Bird
"Allen" <allent@austin.rr.com> wrote in message
news:Y6qdnbXzhL8kWuPWnZ2dnUVZ_qhi4p2d@giganews.com...
> On 2/19/2010 11:08 AM, Dave-UK wrote:
>>
>> "Allen" <allent@austin.rr.com> wrote in message
>> news:ttCdnea7ALpUH-PWnZ2dnUVZ_j6dnZ2d@giganews.com...
>>> I have run chkdsk twice and I have been unable to find the log files
>>> that should have been generated. I know that errors were detected on
>>> one of the runs, and I would really like to see the details.
>>> Allen.

>>
>> The log appears, as Chkdsk, in Event Viewer > Windows Logs > Application.
>> Right-click, Copy, 'Copy details as text' and paste into a text document.
>>
>>
>>

> Thanks, Dave. You always come through.
> Allen


I had to Google to find out :)
I ran Chkdsk to make sure and it ran in a command window and then closed with
no messages on the screen. From what I remember you only get a message if you
have any errors, so if you had errors then it should have displayed something when
it finished it's scan, something you could have copied.
 
T

The poster formerly known as 'The Poster Formerly

Flightless Bird
Allen wrote:
> I have run chkdsk twice and I have been unable to find the log files
> that should have been generated. I know that errors were detected on one
> of the runs, and I would really like to see the details.
> Allen.


Check the event viewer, in the application log.

--
"Software is like sex, it's better when it's free."
- Linus Torvalds

DRM and unintended consequences:
http://blogs.techrepublic.com.com/security/?p=435&tag=nl.e101
 
P

Peter.R

Flightless Bird
For a look at the CHKDSK log in W7, open Event Viewer:

Start->Run->eventvwr [type]->OK->Windows Logs->Application->Information [Level]->Wininit [Source]

(It is normal for CHKDSK to remove unused index entries and unused security descriptors every time it is run. These do not indicate a problem with the file system).

If CHKDSK has found and fixed errors, it is a good idea to run CHKDSK again - as many times as needed until no problems are found, and then reboot the System yet again, without scheduling a CHKDSK.

It is handy to create a Custom View for CHKDSK in Event Viewer:

'Windows Logs' [Expand]->Application [right-click]->Filter Current Log...->Logged: = Any time->Event Level: = [leave all unchecked, or check all]->Event sources: [Drop-down Arrow] = [x] Wininit [check]->OK [button]

Application [right-click]->Save Filter to Custom View...->Name = CHKDSK->OK [button]

--
Peter.R
(Windows 7 Home Premium 32-bit)
"There are more things in Heaven and earth, Horatio, than are dreamt of in your philosophy." - Shakespeare

"Allen" <allent@austin.rr.com> wrote in message news:ttCdnea7ALpUH-PWnZ2dnUVZ_j6dnZ2d@giganews.com...

>
> I have run chkdsk twice and I have been unable to find the log files that should have been generated. I know that errors were detected on one of the runs, and I would really like to see the details.
> Allen.
 
A

Allen

Flightless Bird
On 2/19/2010 1:16 PM, Dave-UK wrote:
>
> "Allen" <allent@austin.rr.com> wrote in message
> news:Y6qdnbXzhL8kWuPWnZ2dnUVZ_qhi4p2d@giganews.com...
>> On 2/19/2010 11:08 AM, Dave-UK wrote:
>>>
>>> "Allen" <allent@austin.rr.com> wrote in message
>>> news:ttCdnea7ALpUH-PWnZ2dnUVZ_j6dnZ2d@giganews.com...
>>>> I have run chkdsk twice and I have been unable to find the log files
>>>> that should have been generated. I know that errors were detected on
>>>> one of the runs, and I would really like to see the details.
>>>> Allen.
>>>
>>> The log appears, as Chkdsk, in Event Viewer > Windows Logs >
>>> Application.
>>> Right-click, Copy, 'Copy details as text' and paste into a text
>>> document.
>>>
>>>
>>>

>> Thanks, Dave. You always come through.
>> Allen

>
> I had to Google to find out :)
> I ran Chkdsk to make sure and it ran in a command window and then closed
> with
> no messages on the screen. From what I remember you only get a message
> if you
> have any errors, so if you had errors then it should have displayed
> something when
> it finished it's scan, something you could have copied.
>
>
>
>
>
>
>

I ran it with the option to repair. I ran for approximately 4 hours, in
five different steps. Yes, it displays on the screen at the end of each
step, but it scrolls by very fast, without time to notate anything
before it has gone by. The final report would have been several pages.
And--the log doesn't appear. I have six chkdsk logs in the event
file--two from December 2009 and four from dates in 2007 and 2008. I
have no idea why the logs from February don't appear; I guess I'll have
to fight the MS bureaucracy (worse in so-called help than in other
parts) to find out. Thanks again, Dave.
Allen
 
Top