CHKDSK can't fix the problem

[grendi seri]

Hi,
I have errors on my drive that I can't get rid of.

First I run " chkdsk d: " in read only mode. Chkdsk tells me there is a
problem on the d: drive.
Here is what the command prompt says :
<<
D:\Documents and Settings\David>chkdsk d:
The type of the file system is NTFS.
Volume label is ide13xp.

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 discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

13341950 KB total disk space.
5859380 KB in 58451 files.
21024 KB in 2891 indexes.
0 KB in bad sectors.
132098 KB in use by the system.
65536 KB occupied by the log file.
7329448 KB available on disk.

4096 bytes in each allocation unit.
3335487 total allocation units on disk.
1832362 allocation units available on disk.
>>

So I run " chkdsk d: /f " and restarts Windows Xp Pro.
In the "pre-windows mode", chkdsk runs but when it finishes, the Chkdsk
screen disapears so fast I can't read the final message.

Back in Windows I run again " chkdsk d: " in read only mode and the problem
is still there.
Here is the message I get from the command prompt :
<<
D:\Documents and Settings\David>chkdsk d:
The type of the file system is NTFS.
Volume label is ide13xp.

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 OBJECTS.MAP in index $I30 of file 5076.
Index verification completed.

Errors found. CHKDSK cannot continue in read-only mode.
>>

If I run again chkdsk in read only mode, I'll get the same message as the
first one (top of this post).
Any help would be welcome, thanks.
David

[Dave]

Don't use chkdsk, use scan disk. Open my computer and select the drive.
Then File; properties. On tools tab under error-checking click check now.
Under check disk options select scan for and attempt recovery of bad
sectors.

"grendi seri" <myst...@mystifier.net> wrote in message
news:ODqR0nSqBHA.2344@tkmsftngp07...

[grendi seri]

"Dave" <ANTIdcha...@yahoo.com> wrote in message
news:a37hcr$15vdsn$1...@ID-114940.news.dfncis.de...

> Don't use chkdsk, use scan disk. Open my computer and select the drive.
> Then File; properties. On tools tab under error-checking click check now.
> Under check disk options select scan for and attempt recovery of bad
> sectors.

Thanks , but this drive is where I installed Windows XP Pro, so when I try
to start Scandisk, Windows says he needs to restart the computer in order to
run Scandisk, which will more likely become a Ckkdsk in "pre windows mode".
gs

[Jill Zoeller [MS]]

Chkdsk is prone to falsely reporting errors when in read-only mode and might
report that a volume is corrupted even when no corruption is present. For
example, Chkdsk might report corruption if NTFS modifies an area of the disk
on behalf of a program at the same time Chkdsk is examining the same area.

You can find out if there is any corruption by typing the following at the
command prompt:

fsutil dirty query c: (substitute your drive letter for c:)

If it says the volume is not dirty, then you do not need to run Chkdsk
because there are no file system errors on the disk.

If you scheduled Chkdsk to run at startup (which you said you did but could
not read the results quickly enough), a version of Chkdsk known as Autochk
runs. You can review the Autochk report in the application log of the Event
Viewer snap-in. Autochk information is logged by the Winlogon service, so
look for entries with Winlogon listed as the source of the entry.

Also, there is no version of Scandisk in Windows XP or Windows 2000. There
are, however, two ways to run Chkdsk--one from the command line and other
from the user interface as Dave pointed out. Both do pretty much the same
thing, although the command-line version has more options.

The Windows XP Resource Kit has a lot of information on Chkdsk, including
all the issues I described above. The link below will take you to the RK.
You want to use the Troubleshooting Disks and File Systems chapter in Part
VI: Troubleshooting.

http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechn
ol/winxppro/reskit/prork_overview.asp?frame=true

Hope this helps!

--
This posting is provided "AS IS" with no warranties, and confers no rights.

"grendi seri" <myst...@mystifier.net> wrote in message

news:uvYmOySqBHA.2560@tkmsftngp04...

[grendi seri]

Of course it helps!!
You're DA MAN!
Thanks :)
David

[Jill Zoeller [MS]]

Correct. If you have any doubts, schedule Chkdsk to run in repair mode at
startup and view the resulting log in Event Viewer.

"Alex Nichol" <Alex...@btinternet.delete.com> wrote in message
news:aaag5u8csiu6sq10f...@4ax.com...
Jill Zoeller [MS] wrote:

>You can find out if there is any corruption by typing the following at the
>command prompt:
>
>fsutil dirty query c: (substitute your drive letter for c:)
>
>If it says the volume is not dirty, then you do not need to run Chkdsk
>because there are no file system errors on the disk

Presumably that covers the case of Chkdsk saying it has 'fixed errors
in the Volume Bit map' when run read only immediately in between two
runs of fsutil both of which report 'NOT dirty' ?

--
Alex Nichol MVP (DTS)
Bournemouth, U.K. Alex....@mvps.org
Check out:'How to make a good newsgroup post'at
http://www.dts-l.org/goodpost.htm