after XP sp3 [machine does chkdsk every boot up, tells me "volume is dirty]

did update, also attempted to add/upgrade wireless router, now machine does chkdsk every boot up, tells me "volume is dirty" also

 

Look here:
http://forums.techguy.org/windows-nt-2000-xp/521889-solved-volume-dirty-question.html

mickzer.

 

why does system do chkdsk each boot

why does system do chkdsk each boot,
and then tell me volume is dirty and during recovery
"recovering orphanad file XXXXX
insufficient disk space to recover lost data "
then (i think ) it reboots and loads normally
the link leads me to a question posted on another board and doesn't give an answer.

help please

 

chaosm,

Your answer is right there in the info that you provided.

You are out of space on the disk. When chkdsk finds some orphan files, it tries to copy those but since you don't have any free space, it fails. It marks the volume dirty & exits. So when you reboot, the cycle repeats itself.

Try to free up some space & try again.

Goodluck.

 

What rsinfo said sounds familiar to me. If you have a lot of disk space though, watch what happens during shutdown, do you see any messages that a program needs to be "forced" to shut down?

Run a full chkdsk on the drive, with a surface check.

I came across this:
http://support.microsoft.com/kb/322275/en-us
it gives some explanation about a "dirty" drive. I don't know the utility it talks about though.

Matt

 

mattman,

The utility is fsutil and the knowledebase talks about FAT drives on which fsutil cannot see the dirty bit & fails.

 

mattman,

Can you please elaborate that further ?

 

From the link I provided:
"try this
got to Start | Run |
bring up a command prompt by typing in CMD click on OK and type fsutil dirty query d:
This queries the drive, and more than likely it will tell you that it is dirty.
Next, type CHKNTFS /X D:
The X tells Windows to NOT check that particular drive on the next reboot. At this time, manually reboot your computer, it should not do a Chkdsk and take you directly to Windows.

Once Windows has fully loaded, bring up another CMD prompt, now you want to do a Chkdsk manually by typing Chkdsk /f /r d:. This should take you through 5 stages of the scan and will unset that dirty bit. Finally, type fsutil dirty query d: and Windows will confirm that the dirty bit is not set on that drive.

http://www.microsoft.com/resources/...all/proddocs/en-us/fsutil_dirty.mspx?mfr=true


Does that not help you?
mickzer.

 

Hi rsinfo,
The drive appears to be running low on space, but that may not be the reason for CHKDSK running at every startup. Even the recovered orphan files might be taking up a lot of space and should be deleted unless the files need to be recovered.

Just for information
http://backupencyclopedia.com/glossary/c/c.html
under the heading Check Disk.

So, yes, more space needs to be made on the drive, but that does not mean that the problem that is causing CHKDSK to run will be fixed.

Make space, then fix the file system, then I would also recommend running a Disk Defragmentation.

Matt
PS mickzer, the link you put in is not working

 

Thanks Matt.
I fixed the link in Post 9, but I think it was a bit superfluous anyway.

mickzer.

 

So as i understand this that the "system" tries to recopy ALL the files or just the orphanded ones? because the drive is 250G and if i have over 125G of orphan fiiles than i have another major issue don't you think?.