chkdsk "checking for file system on D:" & the "volume is dirty"

Something strange has begun to happen, without any known cause by me. At startup the XP system goes into a chkdsk mode and starts "checking for file system on D: ". It coments that "the "volume is dirty" and "chkdsk is verifying files ". It then takes about 5 hours as it goes thru 90,000+ file segments and a lot of segments are found bad ( "bad" may not be the correct word chkdsk uses, but I cannot recall the exact wording Also, I believe chkdsk says it is a 3-phase operation, but I go to sleep before phase 1 is completed and if phases 2 and 3 actually run I don't see them. By the time I get back to the machine, XP has finished starting). After the checking is finished and XP finishes starting up, I can find no problem with any files. All operations at this point seem normal. But when I shutdown the PC and then restart it, the chkdsk saga starts all over again.

When I try to run Disk Defragmenter/Analyze on the D drive I get the message that " disk defragmenter has detected that chkdsk is scheduled to run on the Volume D and that I should run chkdsk /f ". I get no such message on Drive C.

After reading about chkdsk, I am concerned that having to run it to get my system up may in fact be destroying my files or something. But I can't get the PC up and running without going thru the chkdsk saga. I can't get out of the chkdsk operation unless I unplug the PC.

I really need some good advice right now. Thanks.

 

Try going to a command prompt and typing:

chkntfs /d

to return chkdsk to default settings.

But you may want to go to the drive manufacturer and get a drive diagnostic program, just in case.

Also, find this registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager

The default value of BootExecute should be "autocheck autochk* ". There may be added boot executions if you have a defragmenter that boot defrags.

 

chkdsk

Thanks, I will try the things you note. But first I want to be sure of the spelling of the command you give. Is it spelled "chkntfs /d "?
thanks

 

Yes, that is correct. chkntfs /d

Prior to running that you could run chkntfs d: and it will tell you if the d:\ drive is actually tagged as "Dirty." That would give us more info to work with.

CAUTION, I suggest you back up any critical data on that drive!

 

Good advice.

You might also want to look in your event logs (start => run => eventvwr.msc) for an application log event entitled Winlogon. Informational item and when you open it you will see details of what chkdsk found and what it fixed.

Let me echo the suggestion in red from surferdude2's last post. Chkdsk can certainly destroy data on occasion but a drive it 'fixes' things on as yours seems to be is normally in pretty bad shape.

 

chkdsk

The only backup capability I have would be to copy the folders and files from D drive to my C drive. Would that be a good thing or would it make C drive "dirty" (assuming D drive is dirty) ??

 

chkdsk

I have obtained a drive diagnostic program (Powermax) from Maxtor. Will running it posssibly make matters worst (assuming I do not run the fromat options) ??

 

No harm should ever result from running the chkntfs command or any manufacturers diagnostic program.

 

chkdsk

I looked in the Event Logs and found no Winlogon entries.

 

chkdsk

I ran the chkntfs d: and a "dos type" black box flashed on the screen (too fast to see anything on it, but it appeared to be mostly blank). The box dissapeared and the system appeared normal as if I had not run anything. Is this normal result from chkntfs d: ??

 

chkdsk

Before I run the hard disk diagnostic program: since the program runs from a floppy on bootup and since I am getting the chkdsk on bootup, will the two conflict with eact other? I would think that the diagnostic program would try to run first since it runs from the floppy and the chkdsk would run second since it appears to run in XP, i.e. after bootup proper.

 

The diagnostic will run first. Windows will not be booting during that process. Then when you remove the floppy, windows will attempt to boot. The chkdsk that is scheduled by XP runs prior to the Windows 32 bit environment loading. You should be able to elect to not run it. Doesn't it ask and advise? Refuse it if you are allowed.

I would leave the diagnostic disk until last since I don't think this is a hardware issue. Explore the earlier solutions offered first. You must run the commands from a command window and NOT from the RUN window. That's why it closed before letting you read the results.

 

To run chkntfs /d, go to Start > Run, and type: cmd

That will open a command window. Then, type:
chkntfs /d <Enter>
Exit <Enter>