Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
ChkDsk Finds Errors, But Does Not Fix?
132 views
Skip to first unread message
(PeteCresswell)
Nov 18, 2011, 5:31:15 PM11/18/11
to
-----------------------------------------------------------
D:\>chkdsk C:
The type of the file system is NTFS.
Volume label is System.
WARNING! F parameter not specified.
Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Deleting index entry ad192216_0.gif in index $I30 of file 57313.
Deleting index entry AD1922~1.GIF in index $I30 of file 57313.
Index verification completed.
Errors found. CHKDSK cannot continue in read-only mode.
D:\>CHKDSK C: /F
ttype of the file system is NTFS.
clock current drive.
chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N) Y
This volume will be checked the next time the system restarts.
-----------------------------------------------------------
I've been through this four times already. Each time, when I
reboot, ChkDsk runs before XP's window comes up. It seems to
end normally, but the summary screen flashes by so fast I can't
read the details.
Last time around, I made a movie of the screen. On that
iteration, at least, ChkDsk reported no errors at all.
But ChkDsk run immediately after that reboot reported errors
different from the screeen paste above - but seemingly the same
as a number or prior runs:
-------------------------------------------------------
C:\>chkdsk C:
The type of the file system is NTFS.
Volume label is System.
WARNING! F parameter not specified.
Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
Correcting errors in the Volume Bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.
41945683 KB total disk space.
23800572 KB in 166703 files.
92396 KB in 6397 indexes.
0 KB in bad sectors.
295999 KB in use by the system.
65536 KB occupied by the log file.
17756716 KB available on disk.
4096 bytes in each allocation unit.
10486420 total allocation units on disk.
4439179 allocation units available on disk.
-------------------------------------------------------
Bottom line, though, I keep getting these errors back-to-back.
i.e. Run ChkDsk, see errors, Schedule ChkDsk /F for next boot,
reboot, run ChkDsk, see errors.....
I've run a utility called HD Tune that purports to do a detailed
scan for errors on the drive; but it does not find any.
Is there a way out of this situation without rebuilding the
system?
--
PeteCresswell
D:\>chkdsk C:
The type of the file system is NTFS.
Volume label is System.
WARNING! F parameter not specified.
Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Deleting index entry ad192216_0.gif in index $I30 of file 57313.
Deleting index entry AD1922~1.GIF in index $I30 of file 57313.
Index verification completed.
Errors found. CHKDSK cannot continue in read-only mode.
D:\>CHKDSK C: /F
ttype of the file system is NTFS.
clock current drive.
chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N) Y
This volume will be checked the next time the system restarts.
-----------------------------------------------------------
I've been through this four times already. Each time, when I
reboot, ChkDsk runs before XP's window comes up. It seems to
end normally, but the summary screen flashes by so fast I can't
read the details.
Last time around, I made a movie of the screen. On that
iteration, at least, ChkDsk reported no errors at all.
But ChkDsk run immediately after that reboot reported errors
different from the screeen paste above - but seemingly the same
as a number or prior runs:
-------------------------------------------------------
C:\>chkdsk C:
The type of the file system is NTFS.
Volume label is System.
WARNING! F parameter not specified.
Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
Correcting errors in the Volume Bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.
41945683 KB total disk space.
23800572 KB in 166703 files.
92396 KB in 6397 indexes.
0 KB in bad sectors.
295999 KB in use by the system.
65536 KB occupied by the log file.
17756716 KB available on disk.
4096 bytes in each allocation unit.
10486420 total allocation units on disk.
4439179 allocation units available on disk.
-------------------------------------------------------
Bottom line, though, I keep getting these errors back-to-back.
i.e. Run ChkDsk, see errors, Schedule ChkDsk /F for next boot,
reboot, run ChkDsk, see errors.....
I've run a utility called HD Tune that purports to do a detailed
scan for errors on the drive; but it does not find any.
Is there a way out of this situation without rebuilding the
system?
--
PeteCresswell
Jan Alter
Nov 18, 2011, 6:39:04 PM11/18/11
to
"(PeteCresswell)" <x...@y.Invalid> wrote in message
news:8vldc7tpjeae3op3o...@4ax.com...
Click on 'Start' then click 'run' and type cmd (enter)
In the black screen command line type
CHKDSK C: /F /R
( I'm not remembering clearly if one leaves a space between two
parameters. I would try it the way I typed it above first, then if you don't
get satisfaction try it with no space between the /f and /r parameter.)
When windows starts the next time it will run chkdsk in repair mode to
delete the entries and repair bad sectors.
You can read about the different parameters below.
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/chkdsk.mspx?mfr=true
and this from Norton
http://service1.symantec.com/support/powerquest.nsf/docid/2004066687571562
Don't be surprised that it takes longer to run it in the /f/r mode.
If you keep getting errors I would consider checking the integrity of the
hard disk with the manufacturer's diagnostic utility. Additionally, if that
comes up negative but you still are getting chkdsk runs on bootup I would
run memtest86 to check the RAM.
--
Jan Alter
bea...@verizon.net
news:8vldc7tpjeae3op3o...@4ax.com...
In the black screen command line type
CHKDSK C: /F /R
( I'm not remembering clearly if one leaves a space between two
parameters. I would try it the way I typed it above first, then if you don't
get satisfaction try it with no space between the /f and /r parameter.)
When windows starts the next time it will run chkdsk in repair mode to
delete the entries and repair bad sectors.
You can read about the different parameters below.
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/chkdsk.mspx?mfr=true
and this from Norton
http://service1.symantec.com/support/powerquest.nsf/docid/2004066687571562
Don't be surprised that it takes longer to run it in the /f/r mode.
If you keep getting errors I would consider checking the integrity of the
hard disk with the manufacturer's diagnostic utility. Additionally, if that
comes up negative but you still are getting chkdsk runs on bootup I would
run memtest86 to check the RAM.
--
Jan Alter
bea...@verizon.net
Paul
Nov 19, 2011, 12:07:42 AM11/19/11
to
the recovery console (MSDOS command line window) and run CHKDSK
from there. I was playing around with that, a few hours ago,
in a virtual machine.
(Press "R" for recovery)
http://images.techtree.com/ttimages/story/105281_recoveryconsole.gif
(Multiple OS partitions may be identified.
Type the number next to the one you want.
You'll be prompted to enter the Administrator password.)
http://cdnsupport.gateway.com/s/tutorials/images/Topic_37929/160844.gif
Once the command prompt is present, you can type
chkdsk /?
to see the options. And when finished, this will cause a reboot.
exit
The advantage of running chkdsk that way, is C: is not busy, so the
check can repair things. There is no need for it to schedule
a check on the next reboot.
HTH,
Paul
J. P. Gilliver (John)
Nov 19, 2011, 5:56:31 AM11/19/11
to
In message <ja6qav$mif$1...@dont-email.me>, Jan Alter <bea...@verizon.net>
writes:
[]
startup process - or, possibly, the shutdown process - is itself either
corrupting the file system, or setting a flag that makes Windows'
startup process think it is corrupted. (Probably not the latter as
scandisk actually _is_ reporting it is finding errors in the file
system.)
>
If you start up Windows (with chkdsk if it insists), then, from the
desktop, start up a command prompt and run it, I think you've said you
get a clean bill of health. If you then do this again - start up command
prompt, run scandisk - _in the same session_, perhaps just before you
close down after you've been using the PC for whatever you normally use
it for - and again get a clean BOH, then it _suggests_ it is the
shutdown or startup process that is corrupt and causing the file system
damage. (It would also _tend_ to exonerate the HD and RAM, though Jan's
suggestion of running the HD manufacturer's utility and memtest are
definitely worth doing too to be sure, in case there is a fault with one
of those that only shows up at startup or shutdown.)
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G.5AL-IS-P--Ch++(p)Ar@T0H+Sh0!:`)DNAf
What would be unusual would be if there weren't any coincidences at all for
several days in a row. Andy Roberts (UMRAt), 23rd. October 1998.
writes:
[]
>If you keep getting errors I would consider checking the integrity of the
>hard disk with the manufacturer's diagnostic utility. Additionally, if that
>comes up negative but you still are getting chkdsk runs on bootup I would
>run memtest86 to check the RAM.
>
I am also wondering if there's some corruption in Windows, such that the
>hard disk with the manufacturer's diagnostic utility. Additionally, if that
>comes up negative but you still are getting chkdsk runs on bootup I would
>run memtest86 to check the RAM.
>
startup process - or, possibly, the shutdown process - is itself either
corrupting the file system, or setting a flag that makes Windows'
startup process think it is corrupted. (Probably not the latter as
scandisk actually _is_ reporting it is finding errors in the file
system.)
>
If you start up Windows (with chkdsk if it insists), then, from the
desktop, start up a command prompt and run it, I think you've said you
get a clean bill of health. If you then do this again - start up command
prompt, run scandisk - _in the same session_, perhaps just before you
close down after you've been using the PC for whatever you normally use
it for - and again get a clean BOH, then it _suggests_ it is the
shutdown or startup process that is corrupt and causing the file system
damage. (It would also _tend_ to exonerate the HD and RAM, though Jan's
suggestion of running the HD manufacturer's utility and memtest are
definitely worth doing too to be sure, in case there is a fault with one
of those that only shows up at startup or shutdown.)
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G.5AL-IS-P--Ch++(p)Ar@T0H+Sh0!:`)DNAf
What would be unusual would be if there weren't any coincidences at all for
several days in a row. Andy Roberts (UMRAt), 23rd. October 1998.
0 new messages