Chkdsk log size

  • Thread starter Thread starter Fanboy
  • Start date Start date
F

Fanboy

Hi all!
As you know, after a pre-boot chkdsk has performed, the log is available on
Application Events, inside a Winlogon item.
The problem is that the max size of a single log is 16kB. More than enough
when everything is ok (i.e. when you aren't interested in viewing it), but
too small when your disk has some problems, and the list of involved files
may be very long.
Is there a way to increase the max size of a log? Or, alternatively, in
chksdk options can you specify a text file as log output?
Many thanks in advance!
 
Hi,

Start/run eventvwr.msc, then click ok. Click on system, then on
action/properties. Increase the size of hte log here.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org
 
Table 27.3 - Chkdsk Parameters
http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/prkd_tro_xudm.asp

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User
Microsoft Newsgroups

Get Windows XP Service Pack 2 with Advanced Security Technologies:
http://www.microsoft.com/athome/security/protect/windowsxp/choose.mspx

-------------------------------------------------------------------------------------------

:

| Hi all!
| As you know, after a pre-boot chkdsk has performed, the log is available on
| Application Events, inside a Winlogon item.
| The problem is that the max size of a single log is 16kB. More than enough
| when everything is ok (i.e. when you aren't interested in viewing it), but
| too small when your disk has some problems, and the list of involved files
| may be very long.
| Is there a way to increase the max size of a log? Or, alternatively, in
| chksdk options can you specify a text file as log output?
| Many thanks in advance!
 
Rick "Nutcase" Rogers said:
Hi,

Start/run eventvwr.msc, then click ok. Click on system, then on
action/properties. Increase the size of hte log here.
Click to expand...

Thanks, but it seems referring to the total size of the registry (512kB for
default).
I'd like to know how to increase the max size of the log for a single event
(16kB for default)
 
Hi,

1) The line to change is "total log size: ___" (note the use of the word
'log').

2) What makes you think that line has anything to do with the registry?

3) The registry is much, much larger than 512kb.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org
 
Hi Fanboy,

Actually I agree with Rick about the way to change the event log size. But
I noticed that you may not faced such a problem with Event Log Size, so
please tell us the situation you faced in detail. And I also appreciate
Carey providing information about Chkdsk Parameters, you may follow the
article to see if they fit your goals.

Thank you for using Microsoft Newsgroup.

Best regards,

Vincent Xu
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security


--------------------
| From: "Fanboy" <[email protected]>
| Newsgroups: microsoft.public.windowsxp.general
| Subject: Chkdsk log size
| Lines: 12
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
| Message-ID: <[email protected]>
| Date: Sun, 03 Jul 2005 19:07:45 GMT
| NNTP-Posting-Host: 82.50.138.247
| X-Complaints-To: "Please send abuse reports to (e-mail address removed) and technical
notifications to (e-mail address removed)"
| X-Trace: news3.tin.it 1120417665 82.50.138.247 (Sun, 03 Jul 2005 21:07:45
MET DST)
| NNTP-Posting-Date: Sun, 03 Jul 2005 21:07:45 MET DST
| Organization: TIN
| Path:
TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onli
ne.de!tiscali!newsfeed1.ip.tiscali.net!news-out.tin.it!news-in.tin.it!news3.
tin.it.POSTED!not-for-mail
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windowsxp.general:417958
| X-Tomcat-NG: microsoft.public.windowsxp.general
|
| Hi all!
| As you know, after a pre-boot chkdsk has performed, the log is available
on
| Application Events, inside a Winlogon item.
| The problem is that the max size of a single log is 16kB. More than enough
| when everything is ok (i.e. when you aren't interested in viewing it), but
| too small when your disk has some problems, and the list of involved files
| may be very long.
| Is there a way to increase the max size of a log? Or, alternatively, in
| chksdk options can you specify a text file as log output?
| Many thanks in advance!
|
|
|
 
Rick "Nutcase" Rogers said:
Hi,

1) The line to change is "total log size: ___" (note the use of the word
'log').

2) What makes you think that line has anything to do with the registry?

3) The registry is much, much larger than 512kb.
Click to expand...

Sorry, it was a ambiguous translation in the english "log". Surely I knew
that it couldn't be THAT registry. :)
Anyway it doesn't change what I mean: you can set the TOTAL size, not the
size for a single log.
 
Vincent Xu said:
Hi Fanboy,

Actually I agree with Rick about the way to change the event log size. But
I noticed that you may not faced such a problem with Event Log Size, so
please tell us the situation you faced in detail.
Click to expand...

Yes, thanks Vincent.
After I saw some disk errors in my system events report, I decided to run
chkdsk (reboot was necessary).
During the scan, many lines were displayed reporting several problems on my
disk. I didn't worried about reading or writing anything, since I knew that
a log had to be stored somewhere.
When, after Windows reboot, I looked for it (i.e. in Application Events,
under Winlogon item) I discovered that it wasn't complete. It was cut after
about 16kB (because that's the size of the txt file where I copied the log
into).
So this is my request: where (and if) I can set a bigger size for any single
log.
Regards.
 
Hello,

I think I got your idea.

Actually 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. One event log message for each volume checked is
recorded as follows:

Event ID: 1001
Source: Winlogon
Description: This includes file system type; drive letter or GUID, and
volume name or serial number to help determine what volume Chkdsk ran
against.
Also included is whether Chkdsk ran because a user scheduled it or because
the dirty bit was set.

So you know,the log in event log is a detailed one.But as a workaround ,you
can make a log manually via following steps:

1. When you boot up,cancel the autochk.

2. Paste this into a command prompt and run it: CHKDSK C: /F >
C:\CHKDISKLOG.TXT

3. After CHKDSK has run paste this in Start | Run:C:\CHKDISKLOG.TXT

4. You would be able to see the log.

Thank you for using Microsoft Newsgroup, I hope my suggestions helps.

Best regards,

Vincent Xu
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security


--------------------
| From: "Fanboy" <[email protected]>
| Newsgroups: microsoft.public.windowsxp.general
| References: <[email protected]>
<[email protected]>
| Subject: Re: Chkdsk log size
| Lines: 24
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
| Message-ID: <[email protected]>
| Date: Mon, 04 Jul 2005 08:29:42 GMT
| NNTP-Posting-Host: 82.50.138.247
| X-Complaints-To: "Please send abuse reports to (e-mail address removed) and technical
notifications to (e-mail address removed)"
| X-Trace: news4.tin.it 1120465782 82.50.138.247 (Mon, 04 Jul 2005 10:29:42
MET DST)
| NNTP-Posting-Date: Mon, 04 Jul 2005 10:29:42 MET DST
| Organization: TIN
| Path:
TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onli
ne.de!tiscali!newsfeed1.ip.tiscali.net!news-out.tin.it!news-in.tin.it!news4.
tin.it.POSTED!not-for-mail
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windowsxp.general:418280
| X-Tomcat-NG: microsoft.public.windowsxp.general
|
|
| "Vincent Xu [MSFT]" <[email protected]> ha scritto nel
messaggio
| | > Hi Fanboy,
| >
| > Actually I agree with Rick about the way to change the event log size.
But
| > I noticed that you may not faced such a problem with Event Log Size, so
| > please tell us the situation you faced in detail.
|
| Yes, thanks Vincent.
| After I saw some disk errors in my system events report, I decided to run
| chkdsk (reboot was necessary).
| During the scan, many lines were displayed reporting several problems on
my
| disk. I didn't worried about reading or writing anything, since I knew
that
| a log had to be stored somewhere.
| When, after Windows reboot, I looked for it (i.e. in Application Events,
| under Winlogon item) I discovered that it wasn't complete. It was cut
after
| about 16kB (because that's the size of the txt file where I copied the log
| into).
| So this is my request: where (and if) I can set a bigger size for any
single
| log.
| Regards.
|
|
|
 
Fanboy said:
Hi all!
As you know, after a pre-boot chkdsk has performed, the log is available on
Application Events, inside a Winlogon item.
The problem is that the max size of a single log is 16kB. More than enough
when everything is ok (i.e. when you aren't interested in viewing it), but
too small when your disk has some problems, and the list of involved files
may be very long.
Is there a way to increase the max size of a log? Or, alternatively, in
chksdk options can you specify a text file as log output?
Many thanks in advance!
Click to expand...


The way is open a command propmt window with administrator privileges, and type this:

chkdsk

you'll see in the information displayed the size of the log file (65536 KB for example);

then type: chkdsk /L:[size in KB] with the size you desire (131072 KB for example);
example of command to type: chkdsk /L:131072
the system will ask you to schedule the size change in the next reboot.
Let me know if that fixed.

Bye.
 
Back
Top