chkdsk and ntfs problems in xp pro

[Pardus]

Been using xp for a week now, works well except for running chkdsk in command mode on my boot partition.

This is what i get even after rebooting with chkdsk/f serveral times. I did a diag test on the hard drive, no errors reports.


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.
Correcting errors in the Volume Bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

45022130 KB total disk space.
31084684 KB in 30588 files.
10444 KB in 3126 indexes.
0 KB in bad sectors.
109722 KB in use by the system.
65536 KB occupied by the log file.
13817280 KB available on disk.

4096 bytes in each allocation unit.
11255532 total allocation units on disk.
3454320 allocation units available on disk.


what does this mean and how do i fix it ? do i need a 3rd party tool ?

 

[bacillus]

sounds like you need to bootup with the xp cd, choose repair & use CHKDSK with the /F (fix) option!

 

[bsobel]

> Correcting errors in the Volume Bitmap.
Windows found problems with the file system.

I think this is what your worried about, don't be. Chkdsk is trying to check the consistancy of the entire file system while you (you being yourself, background apps, the os itself) attempts to continue using it. The bitmap is the data that indicates what part of the disk is used/unused. It's quite normal if your system is writing files to find minor problems in the bitmap everytime you run chkdsk other than with /f (since in that mode it runs exclusively during startup).

Bill

 

[johnlog]

If you have Norton Utilities 2002 and run DiskDoctor it will come up with a message to check the disk next time you boot up XP. All it is really doing is running CHKDSK /F for you automatically.

Another way is to open a DOS window and type for each partition CHKDSK /F. That also will auto run CHKDSK /F next time you boot up XP. Just before booting up to XP you will see a screen which says it is going to check your hard drive(s) depending on which ones you setup to be checked at the next boot up.

It works.

 

[bsobel]

johnlog, the original poster stated "even after rebooting with chkdsk/f serveral times". I don't believe there isn't a problem here, XP is working as expected.
Bill

 

[Pardus]

i appreciate everyone's help, i did do chkdsk /f again from the command window, rebooted while it did its thing and it still wont go away. Picked up Norton 2002, going to try that now.

Thanks all.

 

[bsobel]

ActiveX, "rebooted while it did its thing and it still wont go away. Picked up Norton 2002, going to try that now"

It won't go away, it's normal. It doesn't neccesiary indicate an error. Norton 2002 is not going to change anything as their isn't an error to fix.
Bill

 

[c0rv1d43]

AFAIK the "inconsistencies" message from chkdsk occurs on boot volumes because of lack of synchronization of redundant state information on system files that are open when the check is run. You might try running chkdsk with the "/r" switch instead.
I never run chkdsk in read-only mode (no switches). I mean, what would be the purpose?

- Collin

 

[bsobel]

> I never run chkdsk in read-only mode (no switches). I mean, what would be the purpose?

The purpose is to find major problems that require chkdsk to run in repair mode. Not a big deal on a workstation machine, but when repair mode takes a couple of hours to run on a server, you want to know you need to do it

Bill

 

[c0rv1d43]

Sorry, I was assuming we were talking about workstations. Come to think of it, I hardly ever use read-only mode for chkdsk on servers. Run 'em 'til they smoke and failover, I say.



- Collin