Chkdsk: why does the C: always have minor inconsistencies?

  • Thread starter Thread starter void.no.spam.com@gmail.com
  • Start date Start date
V

void.no.spam.com@gmail.com

Guest
Over the last week, I've run "chkdsk x: /f /v /r" on my C and D drives
5 or 6 times. The output of the chkdsk shows up in the Event Viewer
Application Log as Winlogon events. I see that whenever I run chkdsk
on my C drive, it ALWAYS has a line saying "Cleaning up minor
inconsistencies on the drive." The D drive never has that problem.
Both the C and D drives are NTFS. This is on Windows 2000 SP4 with
all the latest updates.

So why is the C drive always getting into an inconsistent state, even
within 24 hours of the previous chkdsk?
 
Re: Chkdsk: why does the C: always have minor inconsistencies?


<void.no.spam.com@gmail.com> wrote in message
news:1192379337.708414.98750@e34g2000pro.googlegroups.com...
> Over the last week, I've run "chkdsk x: /f /v /r" on my C and D drives
> 5 or 6 times. The output of the chkdsk shows up in the Event Viewer
> Application Log as Winlogon events. I see that whenever I run chkdsk
> on my C drive, it ALWAYS has a line saying "Cleaning up minor
> inconsistencies on the drive." The D drive never has that problem.
> Both the C and D drives are NTFS. This is on Windows 2000 SP4 with
> all the latest updates.
>
> So why is the C drive always getting into an inconsistent state, even
> within 24 hours of the previous chkdsk?
>


I'd run the mfg's drive diagnostic to make sure the HD is OK...
 
Re: Chkdsk: why does the C: always have minor inconsistencies?

The disk drive may have failed. You can run;
chkdsk /r
from the recovery console command line. (/r implies /f and /p)

To start the Recovery Console, start the computer from the Windows 2000
Setup CD or the Windows 2000 Setup floppy disks. If you do not have Setup
floppy disks and your computer cannot start from the Windows 2000 Setup CD,
use another Windows 2000-based computer to create the Setup floppy disks. At
the "Welcome to Setup" screen. Press F10 or R to repair a Windows 2000
installation, and then press C to use the Recovery Console. The Recovery
Console then prompts you for the administrator password. If you do not have
the correct password, Recovery Console does not allow access to the
computer. If an incorrect password is entered three times, the Recovery
Console quits and restarts the computer. Note If the registry is corrupted
or missing or no valid installations are found, the Recovery Console starts
in the root of the startup volume without requiring a password. You cannot
access any folders, but you can carry out commands such as chkdsk, fixboot,
and fixmbr for limited disk repairs. Once the password has been validated,
you have full access to the Recovery Console, but limited access to the hard
disk. You can only access the following folders on your computer: drive
root, %windir% or %systemroot%

You can also download and run a disk diagnostic utility from the drive
manufacturer's web site.


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

<void.no.spam.com@gmail.com> wrote:
> Over the last week, I've run "chkdsk x: /f /v /r" on my C and D drives
> 5 or 6 times. The output of the chkdsk shows up in the Event Viewer
> Application Log as Winlogon events. I see that whenever I run chkdsk
> on my C drive, it ALWAYS has a line saying "Cleaning up minor
> inconsistencies on the drive." The D drive never has that problem.
> Both the C and D drives are NTFS. This is on Windows 2000 SP4 with
> all the latest updates.
>
> So why is the C drive always getting into an inconsistent state, even
> within 24 hours of the previous chkdsk?
>
 
Re: Chkdsk: why does the C: always have minor inconsistencies?

Try running HD Tune(freeware).

Download and run it and see what it turns up.
http://www.hdtune.com/

Select the Info tabs and place the cursor on the drive under Drive
letter and then double click the two page icon ( copy to Clipboard )
and copy into a further message.

Select the Health tab and then double click the two page icon ( copy
to Clipboard ) and copy into a further message. Also do a full surface
scan with HD Tune.

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~




void.no.spam.com@gmail.com wrote:
> Over the last week, I've run "chkdsk x: /f /v /r" on my C and D drives
> 5 or 6 times. The output of the chkdsk shows up in the Event Viewer
> Application Log as Winlogon events. I see that whenever I run chkdsk
> on my C drive, it ALWAYS has a line saying "Cleaning up minor
> inconsistencies on the drive." The D drive never has that problem.
> Both the C and D drives are NTFS. This is on Windows 2000 SP4 with
> all the latest updates.
>
> So why is the C drive always getting into an inconsistent state, even
> within 24 hours of the previous chkdsk?
 
Re: Chkdsk: why does the C: always have minor inconsistencies?

"void.no.spam.com@gmail.com" <void.no.spam.com@gmail.com> wrote in
news:1192379337.708414.98750@e34g2000pro.googlegroups.com:

> Over the last week, I've run "chkdsk x: /f /v /r" on my C and D drives
> 5 or 6 times. The output of the chkdsk shows up in the Event Viewer
> Application Log as Winlogon events. I see that whenever I run chkdsk
> on my C drive, it ALWAYS has a line saying "Cleaning up minor
> inconsistencies on the drive." The D drive never has that problem.
> Both the C and D drives are NTFS. This is on Windows 2000 SP4 with
> all the latest updates.
>
> So why is the C drive always getting into an inconsistent state, even
> within 24 hours of the previous chkdsk?

Your C: (NTFS) drive gets that message because your running operating
system is on it, so some of the files are open. See the explanation at

""CHKDSK detected minor inconsistencies" error message in Windows 2000
and in Windows NT":
http://support.microsoft.com/kb/109524

"Windows 2000 Chkdsk Reports Cleaning Unused Security Descriptors":
http://support.microsoft.com/kb/q255008/
 
Re: Chkdsk: why does the C: always have minor inconsistencies?

On Oct 14, 1:06 pm, "Dave Patrick" <DSPatr...@nospam.gmail.com> wrote:
> The disk drive may have failed. You can run;
> chkdsk /r
> from the recovery console command line. (/r implies /f and /p)

Is running it from the recovery console any different from telling the
chkdsk to run the next time the system is restarted? And I did do a
"chkdsk /f /v /r". If I do "chkdsk /?" it does not have a /p option.


> To start the Recovery Console, start the computer from the Windows 2000
> Setup CD or the Windows 2000 Setup floppy disks. If you do not have Setup
> floppy disks and your computer cannot start from the Windows 2000 Setup CD,
> use another Windows 2000-based computer to create the Setup floppy disks. At
> the "Welcome to Setup" screen. Press F10 or R to repair a Windows 2000
> installation, and then press C to use the Recovery Console. The Recovery
> Console then prompts you for the administrator password. If you do not have
> the correct password, Recovery Console does not allow access to the
> computer. If an incorrect password is entered three times, the Recovery
> Console quits and restarts the computer. Note If the registry is corrupted
> or missing or no valid installations are found, the Recovery Console starts
> in the root of the startup volume without requiring a password. You cannot
> access any folders, but you can carry out commands such as chkdsk, fixboot,
> and fixmbr for limited disk repairs. Once the password has been validated,
> you have full access to the Recovery Console, but limited access to the hard
> disk. You can only access the following folders on your computer: drive
> root, %windir% or %systemroot%
>
> You can also download and run a disk diagnostic utility from the drive
> manufacturer's web site.
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]http://www.microsoft.com/protect
>
> <void.no.spam....@gmail.com> wrote:
> > Over the last week, I've run "chkdsk x: /f /v /r" on my C and D drives
> > 5 or 6 times. The output of the chkdsk shows up in the Event Viewer
> > Application Log as Winlogon events. I see that whenever I run chkdsk
> > on my C drive, it ALWAYS has a line saying "Cleaning up minor
> > inconsistencies on the drive." The D drive never has that problem.
> > Both the C and D drives are NTFS. This is on Windows 2000 SP4 with
> > all the latest updates.
>
> > So why is the C drive always getting into an inconsistent state, even
> > within 24 hours of the previous chkdsk?
 
Re: Chkdsk: why does the C: always have minor inconsistencies?

You'll be assured nothing will have a lock on any part of the disk.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

<void.no.spam.com@gmail.com> wrote:
> Is running it from the recovery console any different from telling the
> chkdsk to run the next time the system is restarted? And I did do a
> "chkdsk /f /v /r". If I do "chkdsk /?" it does not have a /p option.
 
Back
Top