Archived from groups: microsoft.public.win2000.general,microsoft.public.windowsxp.general,microsoft.public.windowsxp.help_and_support (
More info?)
But you miss the critical point. There is no reason to do it.
--
--------------------------------------------------------------------------------------------------
http://webdiary.smh.com.au/archives/_comment/001075.html
=================================================
"lukesh" <lukesh@discussions.microsoft.com> wrote in message news:07732140-15BF-4BED-AD67-B062C8734D35@microsoft.com...
> Hi Thommy,
> There is no magic formula that can tell you how long Chkdsk will take to
> run. Running Chkdsk can take anywhere from a few seconds to several days,
> depending on your specific situation.
>
> The following list describes the variables that also affect the length of
> time that Chkdsk takes to run.
> Variable 1: The “Indexes†Phase
> During the first phase (checking files) and the third phase (checking
> security descriptors), the progress of the “percent completed†indicator is
> relatively smooth. Unused file record segments do require less time to
> process, and large security descriptors do take more time to process, but
> overall the “percent completed†is a fairly accurate reflection of the actual
> time that the phase requires. The second phase (checking indexes) is the one
> that typically takes the longest to run.
> Variable 2: The Condition of the Volume
> The condition of a volume plays a role in how long Chkdsk takes to run. If
> there were a formula for predicting the time that it takes to run Chkdsk on a
> particular volume, it would include such variables as the number of files and
> folders, the degree of fragmentation of the volume and of the MFT in
> particular, the format of file names (long names, 8.3-formatted names, or a
> mixture), the number of bad sectors on the disk, and the amount of actual
> corruption that Chkdsk must repair. All else being equal, Chkdsk times
> typically increase linearly with respect to the total number of files and
> folders on a volume.
> Variable 3: Hardware Issues
> Hardware issues also affect how long it takes for Chkdsk to run. The
> variables include the available memory, CPU speed, I/O throughput (fibre
> channel or Small Computer System Interface [SCSI]), disk RPM speed, and
> others.
> Variable 4: The Chkdsk Settings
> If you use the /r command-line switch, Chkdsk has to read and verify every
> sector on the volume, which adds significantly to the time that it takes for
> large volumes.
> If you do not use the /r option, the biggest time issue on a particular
> hardware platform is the number of files and folders that are on the volume,
> instead of the absolute size of the volume.
>
> There is no way to speed it up. Sorry.
>
> Lukesh
>
> "Thommy Kanther" wrote:
>
>> I have a 120GB external hard disc connected through USB.
>> When I perform a chkdsk /r it lasts approx 10 hours to perform a chkdsk.
>>
>> Is there any way to speed this check up?
>>
>> Thommy
>>
>>
Facebook
Twitter
Instagram