WinServ2k3 chkdsk issues

[Eskimo]

While in the OS if we run chkdsk in read-only mode we get some orphanad files and what not. Upon reboot and running with /f we get no errors at all. Even if we put the drive in another machine we get no errors at all.

I have searched far and wide, but will admit I'm at my wits end. How do you even google for that error? Search for chkdsk errors? Like thats going to help!

I know that pre sp1 versions of this OS had issues with security tags on files, this is not the same thing but I woldn't rule out any that there may be some common thread between them.

Anyone else ever heard of this?

[Eskimo]

I forgot to mention that I have two identical brand new servers that this is occuring on.

[Eskimo]

Found the answer.

If you are using small byte clusters (512) and the volume is very fragmented then chkdsk cannot shadow the volume correctly and will cause errors. IBM's automated server installer plus backup sofware and raid monitor were the only items installed. If small clusters are used, it will not take much to cause this.

The answer is vey anti-intuitive. When you have chkdsk errors the LAST thing you want to do is defrag the volume, but thats what you have to do.