XP CHKDSK question.

gtghmgtghm New
edited May 2004 in Science & Tech
Ok I scheluded a CHKDSK on my C drive (OS drive)
It said that it couldn't run the request because there were files in use and did I want to schedule it on the next restart which I said yes.

When it rebooted it treid to run the CHKDSK.
It identified the file system then said that it couldn't continue because access was denied to the volume then it said that it was done with the check and booted into XP, took about 3 minutes...

I did this on a different drive and it took forever.... did the 5 out of 5 things it does...

So what is the problem, or what do I look for that would be causeing CHKDSK not to have access to the volume so that it can run the test?

Thanks,
"g"

Comments

  • LeonardoLeonardo Wake up and smell the glaciers Eagle River, Alaska Icrontian
    edited April 2004
    Taking a long time to complete could involve several factors:

    Very large volume - 160GB, 200GB?
    CHKDSK made many repairs - that's a good thing, repairs that is.
    Disk had highly fragmented files.
    Old drive with low platter rotation speed.

    As for not having access to the drive and not completing the operation? Beats me. Someone else will have to answer that.
  • gtghmgtghm New
    edited April 2004
    Its not that its taking a long time I expect that for a 30gb partition its just that I can't get it to run CHKDSK on the c: drive because it says that it dosen't have access to the volume.
    I'm trying a work around now by stoping all my AV protection and booting into safe mode. Seems to be working I'll defrag after that...

    Thanks,
    "g"
  • JonshandbrakeJonshandbrake PERTH, WESTERN AUSTRALIA Member
    edited May 2004
    I may be a little late in offering an opinion but here goes anyway. This happens to me on a regular basis. I just go back and set another chkdsk schedule and reboot, and it works fine the second time around.

    I find it happens a lot if I set the schedule then go off and do a few other things before I reboot. If I set it then reboot immediately my XP (Pro or HE) does the task fine. It can take a fair while to do, particularly if you have a large hard drive.

    Also you can shorten the time if you have Norton Systemworks. By doing a disc doctor scan and scheduling a chkdsk via disc doctor XP only does three of the 5 components. Which sometimes is enough.

    But before setting any disc scan, defrag your drive, even though it may say that it doesn't require it. I find my system works fine after all that. I also do this proceedure once a week whether it needs it or not. Some people may think this obsessive and that once a month is fine. But it works for me and keeps any problems to a bare minimum if any at all.
  • Straight_ManStraight_Man Geeky, in my own way Naples, FL Icrontian
    edited May 2004
    Leonardo wrote:
    Taking a long time to complete could involve several factors:

    Very large volume - 160GB, 200GB?
    CHKDSK made many repairs - that's a good thing, repairs that is.
    Disk had highly fragmented files.
    Old drive with low platter rotation speed.

    As for not having access to the drive and not completing the operation? Beats me. Someone else will have to answer that.

    There at least are a couple major ways to get the "no access" to happen, but Jonshandbrake has the right idea as to best first way to try and solve it. Basically, a file system can be locked. CHKDSK starts after a restart, and a cold shutdown with a damaged file system can leave it locked. Restart, with CHKDSK scheduled, and the file system comes up unlocked as far as CHKDSK is concerned. When CHKDSK is done, if a fast followup run validates the drive, the file system is returned to normal status.

    John D.
Sign In or Register to comment.