Question Locked

chkdsk problem

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I'm having the following problem: When I run chkdsk from a cmd prompt, it shows some index errors. Then before it finishes, it says it cannot continue in read only mode... No problem. I run it with /f and reboot. For some strange reason, when the system comes back up and (apparently) is running chkdsk, I have no video (could this be because I am running an SLI configuration? not the main issue)

I can tell theres hard drive activity and after several minutes of blank screen, the system reboots (as if chkdsk has completed). HOWEVER, when I run chkdsk again from the cmd prompt I get the same index errors as before.

I know that chkdsk creates a log but Where is it?

I tried running chkdsk from the system recovery console with the /p option. M$ states two different things about this...
http://support.microsoft.com/kb/314058
that it fixes problems, and
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/bootcons_chkdsk.mspx?mfr=true
that it doesn't.

Where is the log for chkdsk? Why would chkdsk not fix problems if it finds no bad sectors?

2 replies

by dennish122

Okay, speaking of chkdsk. Would just like to share that while it is a useful tool that repairs volumes, it also can create problems of its own. For example, if your computer crashes or is shut down improperly, CHKDSK may be programmed to run upon the next boot up. While the tool is running, it needs exclusive access to the hard drive which means that you can?t use your computer during CHKDSK error-checking. If this happens frequently, you may not have access to your computer for several hours, several times per week.

You can read this guide on how to fix chkdsk errors.

This discussion is closed to new replies.