CHKDSK Corruption

[AIANDAS[_2_]]

I have a 500GB HDD running dual boot mode XPSP3 in C: and in G: Win 7 RC1
I just booted up and CHKDSK found corruption in the XPSP3 partiion.

"Corrupt record segment 3116."

What is this thing and should I worry?
I do have an image backup, still.
Also how do I locate the CHKDSK log?
Thanks!

[Tim Meddick]

If you ran "chkdsk" with the "/f" option requiring you to reboot to run
it - it has probably fixed the [quoted] file system error.

You will probably find, that if you run [type] chkdsk /f - again at the
'Command Prompt' (answering [y] and [enter] ) and rebooting - that the
check will NOT find the same error.

If it does (keep on finding the same error boot after boot check) - THEN
you can start to worry...

The log for chkdsk can be found in the 'Event Viewer' ('Start Menu' >
'All Programs' > 'Administrative Tools' > 'Event Viewer') in the
'Applications' section under the label 'Winlogon'.

Make sure the list is arranged 'by date' and that you are looking at the
latest entry...

==

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




"AIANDAS" > wrote in message
...
>I have a 500GB HDD running dual boot mode XPSP3 in C: and in G: Win 7
>RC1
> I just booted up and CHKDSK found corruption in the XPSP3 partiion.
>
> "Corrupt record segment 3116."
>
> What is this thing and should I worry?
> I do have an image backup, still.
> Also how do I locate the CHKDSK log?
> Thanks!

[AIANDAS[_2_]]

I am in XP now and the events there for Winlogon are not today's date. Gotta
log onto Win7 to see this now. But will it actually be log since the Winlogon
events in XP now are not logs?

"Tim Meddick" wrote:

> If you ran "chkdsk" with the "/f" option requiring you to reboot to run
> it - it has probably fixed the [quoted] file system error.
>
> You will probably find, that if you run [type] chkdsk /f - again at the
> 'Command Prompt' (answering [y] and [enter] ) and rebooting - that the
> check will NOT find the same error.
>
> If it does (keep on finding the same error boot after boot check) - THEN
> you can start to worry...
>
> The log for chkdsk can be found in the 'Event Viewer' ('Start Menu' >
> 'All Programs' > 'Administrative Tools' > 'Event Viewer') in the
> 'Applications' section under the label 'Winlogon'.
>
> Make sure the list is arranged 'by date' and that you are looking at the
> latest entry...
>
> ==
>
> Cheers, Tim Meddick, Peckham, London. :-)
>
>
>
>
> "AIANDAS" > wrote in message
> ...
> >I have a 500GB HDD running dual boot mode XPSP3 in C: and in G: Win 7
> >RC1
> > I just booted up and CHKDSK found corruption in the XPSP3 partiion.
> >
> > "Corrupt record segment 3116."
> >
> > What is this thing and should I worry?
> > I do have an image backup, still.
> > Also how do I locate the CHKDSK log?
> > Thanks!
>
>
>

[Tim Meddick]

CHDSK will NOT cause a log to be reported in 'Event Viewer' if it is not
run with the "/f" switch *and* is forced to run BEFORE Windows starts
"on next boot".

Only then will it create an entry in the 'Application' section of 'Event
Viewer' (under Winlogon).

Even if you run chkdsk WITH the '/f' switch on a drive other than the
'system' drive - it will NOT appear as an 'Event Viewer' entry.

If you run the command [chkdsk /f ] from the 'Command Prompt' on a drive
other than the 'system' drive - you will see the results in the 'Command
Prompt' window - so there's no need for a log entry.

It's only when chkdsk runs before Windows loads, does it leave a log
entry (in 'Event Viewer' ).


Open the 'Command Prompt' ('Start Menu' > 'Accessories' > 'Command
Prompt' OR type cmd.exe into the "Run" box on the 'Start Menu') and
type the command :

chkdsk c: /f

....when chkdsk asks you :

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

....type [y] followed by [enter]...then reboot to see the check BEFORE
Windows XP loads.

You can then see the log entry in the 'Event Viewer' in the
'Application' section, under Winlogon.

==

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




"AIANDAS" > wrote in message
...
>I am in XP now and the events there for Winlogon are not today's date.
>Gotta
> log onto Win7 to see this now. But will it actually be log since the
> Winlogon
> events in XP now are not logs?
>
> "Tim Meddick" wrote:
>
>> If you ran "chkdsk" with the "/f" option requiring you to reboot to
>> run
>> it - it has probably fixed the [quoted] file system error.
>>
>> You will probably find, that if you run [type] chkdsk /f - again at
>> the
>> 'Command Prompt' (answering [y] and [enter] ) and rebooting - that
>> the
>> check will NOT find the same error.
>>
>> If it does (keep on finding the same error boot after boot check) -
>> THEN
>> you can start to worry...
>>
>> The log for chkdsk can be found in the 'Event Viewer' ('Start Menu' >
>> 'All Programs' > 'Administrative Tools' > 'Event Viewer') in the
>> 'Applications' section under the label 'Winlogon'.
>>
>> Make sure the list is arranged 'by date' and that you are looking at
>> the
>> latest entry...
>>
>> ==
>>
>> Cheers, Tim Meddick, Peckham, London. :-)
>>
>>
>>
>>
>> "AIANDAS" > wrote in message
>> ...
>> >I have a 500GB HDD running dual boot mode XPSP3 in C: and in G: Win
>> >7
>> >RC1
>> > I just booted up and CHKDSK found corruption in the XPSP3 partiion.
>> >
>> > "Corrupt record segment 3116."
>> >
>> > What is this thing and should I worry?
>> > I do have an image backup, still.
>> > Also how do I locate the CHKDSK log?
>> > Thanks!
>>
>>
>>

[db]

my suggestion is
to boot up with a
xp cd and initiate
the "repair" to
launch the recovery
console.

then for both partitions
run >:

chkdsk /r

--

db·´¯`·...¸><)))º>
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces
- Microsoft Partner
- @hotmail.com
~~~~~~~~~~"share the nirvana" - dbZen

>
>

"AIANDAS" > wrote in message ...
> I have a 500GB HDD running dual boot mode XPSP3 in C: and in G: Win 7 RC1
> I just booted up and CHKDSK found corruption in the XPSP3 partiion.
>
> "Corrupt record segment 3116."
>
> What is this thing and should I worry?
> I do have an image backup, still.
> Also how do I locate the CHKDSK log?
> Thanks!