Attachment uploads are currently disabled. This is a temporary situation and will resume as normal in the coming days.
UNSOLVED
L
loisengleny
10 Posts
0
9968
August 24th, 2006 02:00
CHKDSK/DEFRAG problem
Hello! I am going to get straight to the point...
System Type: Dell Dimension 1100/B110
OS: Windows XP
For the past week I have been having problems when I go in and analyze to see if I should defrag or not. Upon clicking defrag I am getting a message stating that CHKDSK /C is scheduled to run so it prevents me from defragment and analyzing. I have clicked start/run and typed in CHKDSK/c and it found two errors, but then it said it couldn't finish. I think this may have been because windows of course is running, correct? Anyways, I restarted and now everything seems to be fine, well for now. I have let it go through the CHKDSK process before on start up and eventually I get that message back again when I try and analyze in defrag. Also, a few times when CHKDSK was running at start up it had three steps that it went through, other times it had 5. Then there was quite a few times in which it stated that the volume is dirty...what the heck does that mean? I really am trying to figure this out for it is really frustrating to have to sit and wait through CHKDSK on start up, especially when I am in a hurry. Please if any one has any information about this CHKDSK/DEFRAG?VOLUME DIRTY thing, any help will be greatly appreciated. Thanks in advance!
- See utility "fsutil"
Message Edited by zeke1312 on 08-24-200612:12 AM
loisengleny
10 Posts
432
0
Posted August 24th, 2006 11:00
I understand that errors can not be fixed when windows is running. But why after I do a CHKDSK at startup, everything loads correctly, if I try to analyze or defrag then, things are fine...but eventually sometime within the day I will try to analyze to see how things are and it will have the yucky message again...CHKDSK is scheduled to run.... :( Why does it keep happening?
loisengleny
10 Posts
432
0
Posted August 24th, 2006 15:00
Zeke: Is it ok to disable the dirty bit then?
Pete: How do I run this thorough disk diagnostics testing?
- fsutil query c: checks to see of dirty bit is set. I'd recommend not using fsutil cmbs to resolve. Instead run chkdsk/f to verify disk clean or not. If checkdisk fails to resolve ,others,may post resolution. There is no way using fsutil to reset dirty bit that that I know of.
Message Edited by zeke1312 on 08-24-200612:07 PM
loisengleny
10 Posts
432
0
Posted August 24th, 2006 17:00
Zeke:
So far so good, I rebooted and let chkdsk run its course...once everything loaded I defragmented the system. So far there have been no probs with me going in and analyzing...let us see how things go for the rest of the day.
Also, I was exploring the system and found an error log....oh my.....is it suppose to have lots of errors in their? I mean I found things like:
Source: Service Control Manager application management service terminated ERROR: Specific module could not be found
and another:
Source: NTFS The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume c:
there were others but it would take me forever to type them all in....many of them though were of the first example I gave.
Got any clue as to what these are? Is it normal to have a lot of errors in this log? By the way, I accessed the log by the following process:
Start/Help and Support under Pick a Task click on Use Tools to view your computer information and diagnose problems then click on Advanced System Information then View the error log
loisengleny
10 Posts
207
0
Posted August 24th, 2006 20:00
Zeke:
Still on the good side here. I am pretty impressed that things have made it this far into the day without messing up. I am praying for the best. I will let you know how things are tonight and tomorrow. It is so important to keep my system up and running correctly for I am an online college student so I depend on this thing for my future...
I also want to say thanks a lot for helping me out...you seem to answer me so quickly...I really appreciate it!
Pete...thank you too!
PETER345
1 Rookie
•
5796 Posts
432
0
Posted August 24th, 2006 04:00
A dirty file system generally results from an improper shutdown (or possibly other anomaly). It means that the file system is likely to have some errors.
With NTFS, I have usually (always?) seen 3 passes.
Peter