Is there a way to improve chkdsk performance in HDD?
I have a system which has 8 GB of RAM. While running chkdsk
it takes quite a bit of time to complete. This is for external HDD. I know there are two options -
Have an SSD, that should improve performance but with a weak/strong possibility of lesser read and write cycles at least on the lower end of the SSD range.
Get more memory. This should improve the performance but I don't know how much as
chkdsk
appears to be a single threaded app which works serially. The only option might be have a large block size but don't know if it's possible, at least in Windows 10.There is also possibility of defragging the filesystem which should help
chkdsk
as well but dunno how good or bad this will be?
The reason to improve chkdsk
is mani-fold. I know if it starts happening too often, its probable that the HDD is prone to failure more .
The performance I am seeking for is more for external HDD's than internal HDD's at this moment in time.
The options I use are chkdsk g: /f /x /r
on a Windows 10 box. The external HDD is a Seagate Slim BUP 2 TB HDD with support for only USB 2.0.
Currently, it takes anywhere between 7-10 hours or even more to check the whole HDD. I dunno if it should take that much time.
windows-10 hard-drive memory ssd performance
|
show 1 more comment
I have a system which has 8 GB of RAM. While running chkdsk
it takes quite a bit of time to complete. This is for external HDD. I know there are two options -
Have an SSD, that should improve performance but with a weak/strong possibility of lesser read and write cycles at least on the lower end of the SSD range.
Get more memory. This should improve the performance but I don't know how much as
chkdsk
appears to be a single threaded app which works serially. The only option might be have a large block size but don't know if it's possible, at least in Windows 10.There is also possibility of defragging the filesystem which should help
chkdsk
as well but dunno how good or bad this will be?
The reason to improve chkdsk
is mani-fold. I know if it starts happening too often, its probable that the HDD is prone to failure more .
The performance I am seeking for is more for external HDD's than internal HDD's at this moment in time.
The options I use are chkdsk g: /f /x /r
on a Windows 10 box. The external HDD is a Seagate Slim BUP 2 TB HDD with support for only USB 2.0.
Currently, it takes anywhere between 7-10 hours or even more to check the whole HDD. I dunno if it should take that much time.
windows-10 hard-drive memory ssd performance
Why do you even need to run the full chkdsk so often, especially with Win10's NTFS having online scans and repairs? Daily scandisk used to be normal in the Win98 era, but definitely not these days.
– grawity
Jan 2 at 20:14
Why are you trying to improve the performance of CHKDSK? Are you wanting to do so for any disk you run checks on, or only a specific disk? What CHKDSK options are you using? Please don't reply in the comments. Edit your question with this information.
– Twisty Impersonator
Jan 2 at 20:31
@TwistyImpersonator done, updated.
– shirish
Jan 2 at 20:34
Good, but please also answer my first question.
– Twisty Impersonator
Jan 2 at 20:36
I did, updated it again.
– shirish
Jan 2 at 20:40
|
show 1 more comment
I have a system which has 8 GB of RAM. While running chkdsk
it takes quite a bit of time to complete. This is for external HDD. I know there are two options -
Have an SSD, that should improve performance but with a weak/strong possibility of lesser read and write cycles at least on the lower end of the SSD range.
Get more memory. This should improve the performance but I don't know how much as
chkdsk
appears to be a single threaded app which works serially. The only option might be have a large block size but don't know if it's possible, at least in Windows 10.There is also possibility of defragging the filesystem which should help
chkdsk
as well but dunno how good or bad this will be?
The reason to improve chkdsk
is mani-fold. I know if it starts happening too often, its probable that the HDD is prone to failure more .
The performance I am seeking for is more for external HDD's than internal HDD's at this moment in time.
The options I use are chkdsk g: /f /x /r
on a Windows 10 box. The external HDD is a Seagate Slim BUP 2 TB HDD with support for only USB 2.0.
Currently, it takes anywhere between 7-10 hours or even more to check the whole HDD. I dunno if it should take that much time.
windows-10 hard-drive memory ssd performance
I have a system which has 8 GB of RAM. While running chkdsk
it takes quite a bit of time to complete. This is for external HDD. I know there are two options -
Have an SSD, that should improve performance but with a weak/strong possibility of lesser read and write cycles at least on the lower end of the SSD range.
Get more memory. This should improve the performance but I don't know how much as
chkdsk
appears to be a single threaded app which works serially. The only option might be have a large block size but don't know if it's possible, at least in Windows 10.There is also possibility of defragging the filesystem which should help
chkdsk
as well but dunno how good or bad this will be?
The reason to improve chkdsk
is mani-fold. I know if it starts happening too often, its probable that the HDD is prone to failure more .
The performance I am seeking for is more for external HDD's than internal HDD's at this moment in time.
The options I use are chkdsk g: /f /x /r
on a Windows 10 box. The external HDD is a Seagate Slim BUP 2 TB HDD with support for only USB 2.0.
Currently, it takes anywhere between 7-10 hours or even more to check the whole HDD. I dunno if it should take that much time.
windows-10 hard-drive memory ssd performance
windows-10 hard-drive memory ssd performance
edited Jan 2 at 21:21
shirish
asked Jan 2 at 20:09
shirishshirish
222311
222311
Why do you even need to run the full chkdsk so often, especially with Win10's NTFS having online scans and repairs? Daily scandisk used to be normal in the Win98 era, but definitely not these days.
– grawity
Jan 2 at 20:14
Why are you trying to improve the performance of CHKDSK? Are you wanting to do so for any disk you run checks on, or only a specific disk? What CHKDSK options are you using? Please don't reply in the comments. Edit your question with this information.
– Twisty Impersonator
Jan 2 at 20:31
@TwistyImpersonator done, updated.
– shirish
Jan 2 at 20:34
Good, but please also answer my first question.
– Twisty Impersonator
Jan 2 at 20:36
I did, updated it again.
– shirish
Jan 2 at 20:40
|
show 1 more comment
Why do you even need to run the full chkdsk so often, especially with Win10's NTFS having online scans and repairs? Daily scandisk used to be normal in the Win98 era, but definitely not these days.
– grawity
Jan 2 at 20:14
Why are you trying to improve the performance of CHKDSK? Are you wanting to do so for any disk you run checks on, or only a specific disk? What CHKDSK options are you using? Please don't reply in the comments. Edit your question with this information.
– Twisty Impersonator
Jan 2 at 20:31
@TwistyImpersonator done, updated.
– shirish
Jan 2 at 20:34
Good, but please also answer my first question.
– Twisty Impersonator
Jan 2 at 20:36
I did, updated it again.
– shirish
Jan 2 at 20:40
Why do you even need to run the full chkdsk so often, especially with Win10's NTFS having online scans and repairs? Daily scandisk used to be normal in the Win98 era, but definitely not these days.
– grawity
Jan 2 at 20:14
Why do you even need to run the full chkdsk so often, especially with Win10's NTFS having online scans and repairs? Daily scandisk used to be normal in the Win98 era, but definitely not these days.
– grawity
Jan 2 at 20:14
Why are you trying to improve the performance of CHKDSK? Are you wanting to do so for any disk you run checks on, or only a specific disk? What CHKDSK options are you using? Please don't reply in the comments. Edit your question with this information.
– Twisty Impersonator
Jan 2 at 20:31
Why are you trying to improve the performance of CHKDSK? Are you wanting to do so for any disk you run checks on, or only a specific disk? What CHKDSK options are you using? Please don't reply in the comments. Edit your question with this information.
– Twisty Impersonator
Jan 2 at 20:31
@TwistyImpersonator done, updated.
– shirish
Jan 2 at 20:34
@TwistyImpersonator done, updated.
– shirish
Jan 2 at 20:34
Good, but please also answer my first question.
– Twisty Impersonator
Jan 2 at 20:36
Good, but please also answer my first question.
– Twisty Impersonator
Jan 2 at 20:36
I did, updated it again.
– shirish
Jan 2 at 20:40
I did, updated it again.
– shirish
Jan 2 at 20:40
|
show 1 more comment
1 Answer
1
active
oldest
votes
It's about /r
. This is what it means:
/r
Locates bad sectors and recovers readable information.
(source)
With this option chkdsk
reads (tries to read) the entire space assigned to the filesystem (or the entire partition, I'm not sure, usually there's no difference). It's somewhat similar to badblocks
in Linux. This takes time. Yes, it takes about 10 hours to read 2TB via USB 2.0 (which maximum speed is 60 MB/s; 2TB HDD is 2000000 MB, do the math).
This option is useful when you suspect there may be bad sectors on the device. They are a hardware issue. If you run chkdsk
only to fix/check filesystem inconsistency (i.e. invalid data on a healthy hardware) then you don't need /r
.
However if you're experiencing bad sectors (what does S.M.A.R.T. say?) and you do need /r
so often then your HDD is probably dying.
To make chkdsk
take less time run it without /r
or connect the disk via an interface that provides more bandwidth (if you can).
Switching to SSD connected via the same USB 2.0 bottleneck will speed things up only because the SSD will probably be smaller. More RAM won't help you at all.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1389918%2fis-there-a-way-to-improve-chkdsk-performance-in-hdd%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
It's about /r
. This is what it means:
/r
Locates bad sectors and recovers readable information.
(source)
With this option chkdsk
reads (tries to read) the entire space assigned to the filesystem (or the entire partition, I'm not sure, usually there's no difference). It's somewhat similar to badblocks
in Linux. This takes time. Yes, it takes about 10 hours to read 2TB via USB 2.0 (which maximum speed is 60 MB/s; 2TB HDD is 2000000 MB, do the math).
This option is useful when you suspect there may be bad sectors on the device. They are a hardware issue. If you run chkdsk
only to fix/check filesystem inconsistency (i.e. invalid data on a healthy hardware) then you don't need /r
.
However if you're experiencing bad sectors (what does S.M.A.R.T. say?) and you do need /r
so often then your HDD is probably dying.
To make chkdsk
take less time run it without /r
or connect the disk via an interface that provides more bandwidth (if you can).
Switching to SSD connected via the same USB 2.0 bottleneck will speed things up only because the SSD will probably be smaller. More RAM won't help you at all.
add a comment |
It's about /r
. This is what it means:
/r
Locates bad sectors and recovers readable information.
(source)
With this option chkdsk
reads (tries to read) the entire space assigned to the filesystem (or the entire partition, I'm not sure, usually there's no difference). It's somewhat similar to badblocks
in Linux. This takes time. Yes, it takes about 10 hours to read 2TB via USB 2.0 (which maximum speed is 60 MB/s; 2TB HDD is 2000000 MB, do the math).
This option is useful when you suspect there may be bad sectors on the device. They are a hardware issue. If you run chkdsk
only to fix/check filesystem inconsistency (i.e. invalid data on a healthy hardware) then you don't need /r
.
However if you're experiencing bad sectors (what does S.M.A.R.T. say?) and you do need /r
so often then your HDD is probably dying.
To make chkdsk
take less time run it without /r
or connect the disk via an interface that provides more bandwidth (if you can).
Switching to SSD connected via the same USB 2.0 bottleneck will speed things up only because the SSD will probably be smaller. More RAM won't help you at all.
add a comment |
It's about /r
. This is what it means:
/r
Locates bad sectors and recovers readable information.
(source)
With this option chkdsk
reads (tries to read) the entire space assigned to the filesystem (or the entire partition, I'm not sure, usually there's no difference). It's somewhat similar to badblocks
in Linux. This takes time. Yes, it takes about 10 hours to read 2TB via USB 2.0 (which maximum speed is 60 MB/s; 2TB HDD is 2000000 MB, do the math).
This option is useful when you suspect there may be bad sectors on the device. They are a hardware issue. If you run chkdsk
only to fix/check filesystem inconsistency (i.e. invalid data on a healthy hardware) then you don't need /r
.
However if you're experiencing bad sectors (what does S.M.A.R.T. say?) and you do need /r
so often then your HDD is probably dying.
To make chkdsk
take less time run it without /r
or connect the disk via an interface that provides more bandwidth (if you can).
Switching to SSD connected via the same USB 2.0 bottleneck will speed things up only because the SSD will probably be smaller. More RAM won't help you at all.
It's about /r
. This is what it means:
/r
Locates bad sectors and recovers readable information.
(source)
With this option chkdsk
reads (tries to read) the entire space assigned to the filesystem (or the entire partition, I'm not sure, usually there's no difference). It's somewhat similar to badblocks
in Linux. This takes time. Yes, it takes about 10 hours to read 2TB via USB 2.0 (which maximum speed is 60 MB/s; 2TB HDD is 2000000 MB, do the math).
This option is useful when you suspect there may be bad sectors on the device. They are a hardware issue. If you run chkdsk
only to fix/check filesystem inconsistency (i.e. invalid data on a healthy hardware) then you don't need /r
.
However if you're experiencing bad sectors (what does S.M.A.R.T. say?) and you do need /r
so often then your HDD is probably dying.
To make chkdsk
take less time run it without /r
or connect the disk via an interface that provides more bandwidth (if you can).
Switching to SSD connected via the same USB 2.0 bottleneck will speed things up only because the SSD will probably be smaller. More RAM won't help you at all.
edited Jan 2 at 21:25
answered Jan 2 at 21:15
Kamil MaciorowskiKamil Maciorowski
26.2k155680
26.2k155680
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1389918%2fis-there-a-way-to-improve-chkdsk-performance-in-hdd%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Why do you even need to run the full chkdsk so often, especially with Win10's NTFS having online scans and repairs? Daily scandisk used to be normal in the Win98 era, but definitely not these days.
– grawity
Jan 2 at 20:14
Why are you trying to improve the performance of CHKDSK? Are you wanting to do so for any disk you run checks on, or only a specific disk? What CHKDSK options are you using? Please don't reply in the comments. Edit your question with this information.
– Twisty Impersonator
Jan 2 at 20:31
@TwistyImpersonator done, updated.
– shirish
Jan 2 at 20:34
Good, but please also answer my first question.
– Twisty Impersonator
Jan 2 at 20:36
I did, updated it again.
– shirish
Jan 2 at 20:40