chkdsk....not fixing

[steve.uk]

when i run chkdsk from the command prompt in read only mode i get the
message 'chkdsk has found errors on the drive, you should run chkdsk /f to
fix them'.....

if i run disk doctor in norton it tells me that security descriptors have
errors.

i have run chkdsk /f and chkdsk /r and disk doctor (which does the same
thing) but the errors are not fixed.

how can i find these errors and fix them?

[Lilla]

The following thread is between someone with the problem you report, and
Microsoft.

From: Tim Adams )
Subject: Re: Chkdsk errors on NTFS hard disk in XP Pro
Newsgroups: microsoft.public.windowsxp.perform maintain
Date: 2002-01-30 16:22:28 PST

I *am* running chkdsk on the volume in which XP is
installed. I'm afraid I didn't see anything in the
document you mentioned re chkdsk errors in read only
mode. ( Part VI of the Windows XP Resource Kit, which I
found at this link :

http://www.microsoft.com/technet/treeview/default.asp?
url=/technet/prodtechnol/winxppro/reskit/prkd tro gwoj.asp

I just re-read this chkdsk chapter, and still couldn't
find this information. I apologize if I'm overlooking
it. If you can point out where it is, I'll be grateful!

I ran FSUTIL DIRTY QUERY C: , which reports that the
drive is clean. Further, chkdsk does not automatically
run at start-up; it runs only if I specify chkdsk /f
before rebooting.

However, after chkdsk /f runs at start-up, the Event
Viewer does report consistently that corrections are
being made. Here's the latest Event Viewer entry :

A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 2 unused index entries from index $SII of
file 0x9.
Cleaning up 2 unused index entries from index $SDH of
file 0x9.
Cleaning up 2 unused security descriptors.

Do you think I can regard these Event Viewer entries as
inconsequential and/or usual, and ignore them, if FSUTIL
DIRTY QUERY C: continues to report no errors ... or do
they affect your suspicions of what's going on?

Thanks once more.

From: Jill Zoeller [MS] )
Subject: Re: Chkdsk errors on NTFS hard disk in XP Pro
Newsgroups: microsoft.public.windowsxp.perform_maintain
Date: 2002-01-30 16:45:49 PST

Hi Tim,
Looking at the chapter, I see that the read-only text was somewhat
buried--it's in the section on determining how long Chkdsk will run. I can
see why this text would be easy to overlook, and I apologize for assuming
you'd see it. I will definitely make this clearer for the Windows .NET
Server Resource Kit. :-)

I will have to look into why you're seeing errors being fixed at startup
even when the volume is marked as clean. This is surprising to me, so let me
talk to a developer and get back to you. This might be normal (and something
I did not know when I wrote the chapter), or it could be something else. I
don't want to make an assumption just yet until I find out more.

Are you seeing these problems on both disks?

From: Jill Zoeller [MS] )
Subject: Re: Chkdsk errors on NTFS hard disk in XP Pro
Newsgroups: microsoft.public.windowsxp.perform_maintain
Date: 2002-01-31 09:05:10 PST

Hi Tim, I got a response from a developer last night that should clear
things up:

"These are cleanup. They are not corruption. They happen naturally as the
system is being used. It does not harm anything if you leave them on the
disk.
If the dirty bit is not set, a full blown chkdsk will not be run on the
drive at startup. But as I explained above, the inconsistencies are minor
and do not warrant a chkdsk run at startup. So it is indeed appropriate that
the dirty bit is not set and chkdsk is not run at startup."

Yours is the first report I've seen of these "clean-up" issues, so I'll make
sure this gets documented for future releases. I'm sorry you spent so much
time troubleshooting phantom errors. I think this has been a learning
experience for both of us!

From: Tim Adams )
Subject: Re: Chkdsk errors on NTFS hard disk in XP Pro
Newsgroups: microsoft.public.windowsxp.perform maintain
Date: 2002-01-31 09:49:10 PST

And I guess that takes care of that! I really appreciate
your help in resolving this problem. I'll forward this
thread to Dell, so their techs are aware of it.

Tim
"steve.uk" > wrote in message
...
> when i run chkdsk from the command prompt in read only mode i get the
> message 'chkdsk has found errors on the drive, you should run chkdsk /f to
> fix them'.....
>
> if i run disk doctor in norton it tells me that security descriptors have
> errors.
>
> i have run chkdsk /f and chkdsk /r and disk doctor (which does the same
> thing) but the errors are not fixed.
>
> how can i find these errors and fix them?
>
>