Well, you honestly need to start readin up again. For years chkdsk /f has NEVER ben the same as chkdsk /r. Here is the output of chkdsk /?:
volume Specifies the drive letter (followed by a colon),
mount point, or volume name.
filename FAT/FAT32 only: Specifies the files to check for fragment
/F Fixes errors on the disk.
/V On FAT/FAT32: Displays the full path and name of every fi
on the disk.
On NTFS: Displays cleanup messages if any.
/R Locates bad sectors and recovers readable information
(implies /F).
/L:size NTFS only: Changes the log file size to the specified nu
of kilobytes. If size is not specified, displays current
size.
/X Forces the volume to dismount first if necessary.
All opened handles to the volume would then be invalid
(implies /F).
/I NTFS only: Performs a less vigorous check of index entrie
/C NTFS only: Skips checking of cycles within the folder
structure.
he /I or /C switch reduces the amount of time required to run Chkdsk by
kipping certain checks of the volume.
Also note:
**broken link removed**
With the following quote:
/r Locates bad sectors and recovers readable information. The disk must be locked. /r includes the functionality of /f, with the additional analysis of physical disk errors.
So now you can clearly see that you are totally wrong about that statement. Note the part about physical disk errors, sound familiar?
Next, you mention replacing a hard drive for blue screen. Are you in the same thread, because the beginning post states that every time he boots his PC, the box goes into automatic chkdsk. This is almost always because of hardware problems if it constantly happens because chkdsk cannot fix the problem, yet NT still sees that there is a problem in the table. The reason it blue screens is more than likely because the registry files are corrupt from the bad sectors that chkdsk cannot seem to fix. You see, in Windows, the most written to and read section of a drive is where the registry is because it is essentially a database. If a drive is going to have problems, probably 60% of the time it is going to include this area.
Lastly you throw your resume out there. Wow, all of 50 nodes huh? The pressure you must be under with handling 50 nodes. My house has 27 nodes and thats just my home network. I am one of 5 senior/lead infrastructure engineers for a world wide company with 486,000+ nodes, & 140,000+ users along with owning my own company. There is no one technical above me in ranking in this company either. I'm also highly publicised on the net, along with being a past Microsoft MVP. So there, you have my resume now. You can either believe I know what I'm doing and learn something or you can be close minded as you have and continue your tasks of administerring 50 nodes.
And, oh, I'm not trying to come off being a smart ass.