To do a read-only chkdsk it's just "chkdsk <driveletter>:" and then there are a few other options in Server 2008 R2. They are
My understanding is that /R takes the longest and is the most exhaustive. /F is the next slowest. And adding /I and /C can reduce the time even more and are usually pretty good at fixing the corruption issues shown in task manager.
Here's my goal: I manage a remote system. I need to run chkdsk on a non-boot-volume that has 10tb of data across hundreds of millions of files. I need it to finish as fast as possible with the best chance at fixing corruption. I think what I want to do is "chkdsk G: /f /i /c" right?
To help I will have stopped any service that touches the drive, stopped AV watching the volume, etc. Is there anything else I can do to help it go as fast as possible? We've maxed out the ram in the system. If I have it run at boot-up is that faster? I potentially could have remote hands hook up a monitor to it and check in with them from time to time. Last time I ran this remotely over RDP it took 15 hours on a smaller volume but similar makeup.