Thread: chkdsk problems
View Single Post

  #17  
Old 04-08-2005, 11:26 AM
MetalKnight Offline
Registered User
 
Join Date: Apr 2005
Posts: 2
Quote:
Originally Posted by Ant
Anyone else have any ideas?

Hi guys,

This one is actually pretty easy to fix. Getting the checkdisk stuck seems to be pretty common in XP. So lets fix it!

First, check to see if the disk/partition is actually DIRTY (IE broken/lost chains, bad cluster data etc), which it probably is. Open a command prompt. Type fsutil dirty query c: and replace the c: with whatever drive letter you wish to check. It will tell you if the disk is DIRTY or NOT.

Assuming that is is DIRTY, you will need to check it and repair damages. But, you will also need to reset your scheduled chkdsk that will forever try to run upon bootup (hence it being stuck).

Now use the chkntfs utility to reset this. From the command prompt, type chkntfs /d. This will reset the checkdisk but it will still have to run on the next boot up, but after that, it will no longer attempt to run every time and it removes it from the scheduler which will allow normal checkdisk access to the drive again. (You can also input chkntfs /? for a list of all the NTFS utility commands.)

Reboot and let the checkdisk run this last time.

Once you are back into the XP console, go to My Computer, right click the drive that you need to check, go to Tools and then go to Error-Checking and click the Check Now button. Select both options for automatically fix errors and scan disk for bad clusters. Depending on the size of the disk, this will take anywhere from a while to a very long while (6 Phases I think).

When that is finally done, the drive should be fixed of problems. Now it is highly recommended to do a defragmentation of the drive so everything gets moved and placed in proper order. Once the defrag is complete, check again for DIRTY drives using the fsutil dirty query c: command again. Your drive(s) should be NOT DIRTY now.

Reboot to make sure the scheduled checkdisk no longer launches on reboot (it should not) and then drink a beer or two and celebrate fixing this issue without the hassle of reloading the OS!


MetalKnight
Reply With Quote