CHKDSK not checking boot disk

**rmayo** · July 11th, 2004, 09:34 PM

I found this on Executive Software site:

When I try to select a partition with Diskeeper, it says, ''Diskeeper has detected that CHKDSK is scheduled to run on the volume: Please run CHKDSK /F.'' What is the problem?

The ''dirty bit'' is set on this partition. The dirty bit is single point of entry that is changed from a 0 to 1 to ensure that CHKDSK /F will be run during the next restart of the system. You can check this by typing CHKNTFS C: (assuming that the C: partition is the one in question) at the Command Prompt. When you reboot the system, CHKDSK should run. When it runs, the dirty bit setting will be reverted to its original value. If it does not run, the dirty bit will remain set and thus you will continue to see the message.

If CHKDSK does not run during the restart, you are probably running a software licensing service called ''Crypkey Service'', ''Crypkey License,'' and possibly a driver ''NetworkX'' that lock the system drive. The ''Crypkey'' portion provides key-based copy protection and the ''NetworkX'' provides a means of transporting it across locally connected networks. Here is a link to the Microsoft Knowledge Base article on this: http://support.microsoft.com/support...LNG=ENG&SA=PER.

The service and driver must be stopped and disabled, and then the CHKDSK /F can run when the system restarts. The software protected by this system will not operate correctly until the service and driver are restarted and enabled.

We have also received reports of a Kensington Mouse driver that inhibits the ability of CHKDSK /F to run. If you are certain that you are not using Crypkey, this may be the issue.

By request of Microsoft, Diskeeper will not run on a partition that has the dirty bit set. The dirty bit is not something to be taken lightly; it is the only way that Windows has to attempt to make sure that you do not get into serious trouble with a partition.

If none of the above applies to your current configuration, we recommend that you do a clean installation of Windows in a separate directory and reboot to that installation. That will allow CHKDSK /F to run and clear the dirty bit

**NooNoo** · July 12th, 2004, 04:15 AM

Welcome to Windrivers rmayo - good find!

**Fraser** · July 13th, 2004, 12:02 PM

The dirty bit does not appear to be getting stuck on. After CHKDSK reports not being able to open the volume for direct access it does not run at the next booting.

I don't have Diskkeeper. I am planning to try moving the drive cable to a motherboard IDE connector to see what that does.

**rmayo** · July 15th, 2004, 09:36 PM

Originally Posted by Fraser

The dirty bit does not appear to be getting stuck on. After CHKDSK reports not being able to open the volume for direct access it does not run at the next booting.

I don't have Diskkeeper. I am planning to try moving the drive cable to a motherboard IDE connector to see what that does.

I have created a couple of drives: One I did

chkdsk /L:131072

this resizes the logfile and then chkdsk ran again.

the other I put in XP second unit and ran chkdsk /f on the drive which then allowed chkdsk to run.

each drive ran fine until I reinstalled diskkeeper at which time it marked the drive as needing to run chkdsk /f. chkdsk would run but would not clean bit. This was determined by running chkntfs. which would indicate a dirty bit. So on that unit I have not reinstilled diskeeper and it seem to be fine.
Hope this might help.

**jrmiller200** · July 20th, 2004, 03:23 PM

http://support.microsoft.com/default...b;en-us;235771

Not saying it's a magic bullet but it shows how things start early in the boot process that can interupt the chkdsk. For me this fix actually worked. I had the sms client installed on the workstation and this fix from microsoft did the trick.

**Fraser** · July 30th, 2004, 05:14 AM

CHKDSK has started checking my boot drive again. It was nothing to do with the controller card. I don't know what has started it but I have installed the new Zone Alarm 5.1.011.000. Also I have removed Privacy Master by Webroot.

**Fraser** · July 30th, 2004, 09:55 AM

I have verified the problem as coming from the previous version of Zone Alarm using another computer that had the same problem and with upgrading Zone Alarm to the new version.