You might get a rough estimate by running it read-only mode (no switches). Then add some time to this. Its more about file / folder count than about total disk size.
--please don't forget to Accept as answer if the reply is helpful--
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
On Windows Server 2016 or 2019, how long has "chkdsk /r /f" taken on large volumes (>2 TB)? I'm thinking through the pros and cons between using NTFS on file servers and replicating the data using DFS, or running file server VMs with ReFS on a VxRail stretched cluster with VSAN replication.
You might get a rough estimate by running it read-only mode (no switches). Then add some time to this. Its more about file / folder count than about total disk size.
--please don't forget to Accept as answer if the reply is helpful--
Hi,
On Windows Server 2016 or 2019, how long has "chkdsk /r /f" taken on large volumes (>2 TB)?
Chkdsk /r /f command will locate bad sectors and recover readable information from bad sectors and then fix found errors in disk.
You can only run chkdsk /r command since it includes the /f function. However, if you only want to fix disk file system errors, you can only use chkdsk /f command since it will cost much less time.
Need to mention that you don’t need to run a chkdsk /r command unless you think the target hard drive has physically bad sectors. This is because, checking 1TB hard drive may take more than 5 hours depending on your hard drive performance.
(source)
Thanks for your time!
Best Regards,
Mico Mi
-----------------------------
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.