chkdsk repeatedly finds "problems with file system"

[Guest]

I have read several threads about this problem (described in more detail
below) which I found by searching, but I have not found any conclusion in any
of them as to whether (a) this a bug of some sort, possibly SP2-related,
which inaccurately reports errors, and, if so, what to do about it, or (b)
there really is some real error which chkdsk is finding but not fixing, in
which case, what to do about that.

The problem is this:
When I run chkdsk it says that it corrected the volume bitmap. It says it
found problems with the file system and that I should run chkdsk /f. I do
that. But then when I run chkdsk again, I get the same message. I have run
chkdsk and chkdsk /f both from the gui and from the command prompt -- same
result.

What is the current thinking on this issue?

OS: Windows XP Home SP2, file system NTFS
Dell Dimension 8200, 768mb RAM
Hard drive: WD 40gb

 

[Kerry Brown]

I have read several threads about this problem (described in more detail
below) which I found by searching, but I have not found any conclusion in
any
of them as to whether (a) this a bug of some sort, possibly SP2-related,
which inaccurately reports errors, and, if so, what to do about it, or (b)
there really is some real error which chkdsk is finding but not fixing, in
which case, what to do about that.

The problem is this:
When I run chkdsk it says that it corrected the volume bitmap. It says it
found problems with the file system and that I should run chkdsk /f. I do
that. But then when I run chkdsk again, I get the same message. I have
run
chkdsk and chkdsk /f both from the gui and from the command prompt -- same
result.

What is the current thinking on this issue?

OS: Windows XP Home SP2, file system NTFS
Dell Dimension 8200, 768mb RAM
Hard drive: WD 40gb

Get a second opinion. Download the Data Lifeguard diagnostic (DOS) either
floppy or CD from www.westerndigital.com It will test the drive but not the
filesystem. If the drive tests OK then the problem is with the filesystem.
It may be time to backup and reinstall everything.

Kerry

 

[Guest]

Forget data lifeguard,its a waste of youre time..However,try installing xp cd,
exit the info page,restart computer,boot to xp cd (you may need to adjust for
this in BIOS,priority boot drive or similiar),then at xp cd boot info
screen select
recovery,type:1 For C: drive,press enter key for password,then type:
CHKDSK C: /R When its thru-12-20 min.,type:EXIT Let xp start,remove cd.

 

[Kerry Brown]

Forget data lifeguard,its a waste of youre time..However,try installing xp
cd,
exit the info page,restart computer,boot to xp cd (you may need to adjust
for
this in BIOS,priority boot drive or similiar),then at xp cd boot info
screen select
recovery,type:1 For C: drive,press enter key for password,then type:
CHKDSK C: /R When its thru-12-20 min.,type:EXIT Let xp start,remove cd.

What planet are you from? Do you read the posts before you reply? Harold
indicated he has run chkdsk multiple times. My post clearly says that Data
Lifeguard only checks the disk not the file system. My reasoning is if
chkdsk doesn't work and the disk physically checks out OK then it's worth it
to back up and do a clean install. Something in the file system is corrupted
beyond chkdsk's ability to repair. I will give you that Data Lifeguard will
sometimes pass a marginal disk so WD doesn't have to warranty it but it will
find obviously bad disks. I would test the disk before bothering to go much
further than Harold has already. If chkdsk doesn't work and Data Lifeguard
is useless how would you check the disk?

Kerry

 

[Ron Martell]

What planet are you from? Do you read the posts before you reply? Harold
indicated he has run chkdsk multiple times. My post clearly says that Data
Lifeguard only checks the disk not the file system. My reasoning is if
chkdsk doesn't work and the disk physically checks out OK then it's worth it
to back up and do a clean install. Something in the file system is corrupted
beyond chkdsk's ability to repair. I will give you that Data Lifeguard will
sometimes pass a marginal disk so WD doesn't have to warranty it but it will
find obviously bad disks. I would test the disk before bothering to go much
further than Harold has already. If chkdsk doesn't work and Data Lifeguard
is useless how would you check the disk?

Kerry

Andrew is a blathering nincompoop who persists in giving incorrect,
and sometimes dangerously incorrect, responses on these newsgroups.

Most of the regulars just ignore him unless he posts something that is
totally bonkers and which might cause problems if his suggestions were
followed.
Ron Martell Duncan B.C. Canada
--
Microsoft MVP
On-Line Help Computer Service
http://onlinehelp.bc.ca

In memory of a dear friend Alex Nichol MVP
http://aumha.org/alex.htm

 

[Guest]

The WD DLDiag utility extended test passed the disk with no problems. Ran
chkdsk again from the gui -- no message at the end. Ran it from the command
prompt -- got same old message. Not sure what to think. Everything seems to
be working fine. This seems to have started not too long ago after chkdsk
reported that it found free space which was allocated, and three orphaned
files which it assigned (to files defined with numbers in the error message
-- no lost fragments converted to files). Maybe it fixed something wrong, or
maybe that message was the indication that something was already wrong.

Under the circumstances, at this point, having run the WD WLDiag, I don't
see any additional benefit in running the recovery console and the /r
parameter.

Maybe I should just sit tight for now (and hold my mouth right)?

thanks

 

[Kerry Brown]

Andrew is a blathering nincompoop who persists in giving incorrect,
and sometimes dangerously incorrect, responses on these newsgroups.

Most of the regulars just ignore him unless he posts something that is
totally bonkers and which might cause problems if his suggestions were
followed.

I know this. Sometimes I just can't believe he actually thinks what he posts
is helpful and just have to say something

Kerry

 

[Kerry Brown]

The WD DLDiag utility extended test passed the disk with no problems. Ran
chkdsk again from the gui -- no message at the end. Ran it from the
command
prompt -- got same old message. Not sure what to think. Everything seems
to
be working fine. This seems to have started not too long ago after chkdsk
reported that it found free space which was allocated, and three orphaned
files which it assigned (to files defined with numbers in the error
message
-- no lost fragments converted to files). Maybe it fixed something wrong,
or
maybe that message was the indication that something was already wrong.

Under the circumstances, at this point, having run the WD WLDiag, I don't
see any additional benefit in running the recovery console and the /r
parameter.

Maybe I should just sit tight for now (and hold my mouth right)?

thanks

Make sure you have good backups. I have never seen a case when running chdsk
from the recovery console fixed something that having it run on a reboot
misses. Who knows though? It can't hurt as long as you have a backup. I have
seen cases where chkdsk couldn't fix something and the drive passed other
diagnostics. Repeatedly running chkdsk eventually corrupted the file system.
I suspect it was a marginal drive with sectors that could occasionally be
read but in reality were bad.

Kerry