Clonezilla disk to image speed decreasing over time
I am actually backing my whole 2tb disk using Clonezilla disk-to-image option.
I don't use any encryption or anything that I know that could slow down the process, and yet, Clonezilla tells me that there is 72 hours remaining at a speed of 400MB/min.
When I started it, Clonezilla told me that it would take 8 hours at 3gb/min but that speed just kept decreasing over time. Now one hour after the start of the copy, I am at 400mb/min and it keep decreasing. Is it normal ?
I am using Clonezilla on a bootable USB Key and the external hard drive receiving the copy image is new and healthy (using usb3 too). The only bad point I can think of is that the disk I am copying is usually a bit slow on my Windows (something is wrong with it, I don't know what) but still it shouldn't be THAT slow (and doesn't explain why it started at 3gb/min).
Is there anything I can do to speed up the process? Is it safe to reboot my computer during the copy and try again? Should I even bother trying again?
Edit:
Ok, 10 minutes after my question it is now at 84 hours. I just want to know if it is safe to shut it down because I am not going to wait the whole week for that.
hard-drive performance clonezilla
asked Apr 24 '16 at 14:50
RogerRoger
13615
|
show 1 more comment
I am actually backing my whole 2tb disk using Clonezilla disk-to-image option.
I don't use any encryption or anything that I know that could slow down the process, and yet, Clonezilla tells me that there is 72 hours remaining at a speed of 400MB/min.
When I started it, Clonezilla told me that it would take 8 hours at 3gb/min but that speed just kept decreasing over time. Now one hour after the start of the copy, I am at 400mb/min and it keep decreasing. Is it normal ?
I am using Clonezilla on a bootable USB Key and the external hard drive receiving the copy image is new and healthy (using usb3 too). The only bad point I can think of is that the disk I am copying is usually a bit slow on my Windows (something is wrong with it, I don't know what) but still it shouldn't be THAT slow (and doesn't explain why it started at 3gb/min).
Is there anything I can do to speed up the process? Is it safe to reboot my computer during the copy and try again? Should I even bother trying again?
Edit:
Ok, 10 minutes after my question it is now at 84 hours. I just want to know if it is safe to shut it down because I am not going to wait the whole week for that.
hard-drive performance clonezilla
asked Apr 24 '16 at 14:50
RogerRoger
13615
1
Compression makes a big difference pgzip vs pbzip. pbzip can be way faster. You need to use a type starting with p for multi-core compression. The compressible of the data plays a big factor in speed.
– cybernard
Apr 24 '16 at 15:10
1
bad/weak sectors also significantly slow the drive down when it needs to ECC a lot of sectors.
– cybernard
Apr 24 '16 at 15:41
1
those are estimated times and can change at any point during the clone process, I agree with cybernard, the drive you are cloning from may have bad sectors or other performance issues.
– Moab
Apr 24 '16 at 16:19
1
You can press CTRL + C to cancel the current copy process. Just keep doing that until the cloning stops. After that you can just shut down normally.
– chue x
Apr 24 '16 at 16:53
I have exactly the same behavior, have you found a solution for your issue so could actually clone the disk?
– Thomas
Aug 22 '16 at 20:42
|
show 1 more comment
I am actually backing my whole 2tb disk using Clonezilla disk-to-image option.
I don't use any encryption or anything that I know that could slow down the process, and yet, Clonezilla tells me that there is 72 hours remaining at a speed of 400MB/min.
When I started it, Clonezilla told me that it would take 8 hours at 3gb/min but that speed just kept decreasing over time. Now one hour after the start of the copy, I am at 400mb/min and it keep decreasing. Is it normal ?
I am using Clonezilla on a bootable USB Key and the external hard drive receiving the copy image is new and healthy (using usb3 too). The only bad point I can think of is that the disk I am copying is usually a bit slow on my Windows (something is wrong with it, I don't know what) but still it shouldn't be THAT slow (and doesn't explain why it started at 3gb/min).
Is there anything I can do to speed up the process? Is it safe to reboot my computer during the copy and try again? Should I even bother trying again?
Edit:
Ok, 10 minutes after my question it is now at 84 hours. I just want to know if it is safe to shut it down because I am not going to wait the whole week for that.
hard-drive performance clonezilla
asked Apr 24 '16 at 14:50
RogerRoger
13615
I am actually backing my whole 2tb disk using Clonezilla disk-to-image option.
I don't use any encryption or anything that I know that could slow down the process, and yet, Clonezilla tells me that there is 72 hours remaining at a speed of 400MB/min.
When I started it, Clonezilla told me that it would take 8 hours at 3gb/min but that speed just kept decreasing over time. Now one hour after the start of the copy, I am at 400mb/min and it keep decreasing. Is it normal ?
I am using Clonezilla on a bootable USB Key and the external hard drive receiving the copy image is new and healthy (using usb3 too). The only bad point I can think of is that the disk I am copying is usually a bit slow on my Windows (something is wrong with it, I don't know what) but still it shouldn't be THAT slow (and doesn't explain why it started at 3gb/min).
Is there anything I can do to speed up the process? Is it safe to reboot my computer during the copy and try again? Should I even bother trying again?
Edit:
Ok, 10 minutes after my question it is now at 84 hours. I just want to know if it is safe to shut it down because I am not going to wait the whole week for that.
hard-drive performance clonezilla
hard-drive performance clonezilla
asked Apr 24 '16 at 14:50
RogerRoger
13615
asked Apr 24 '16 at 14:50
RogerRoger
13615
edited Apr 24 '16 at 15:01
Roger
asked Apr 24 '16 at 14:50
RogerRoger
13615
asked Apr 24 '16 at 14:50
RogerRoger
13615
asked Apr 24 '16 at 14:50
RogerRoger
13615
13615
1
Compression makes a big difference pgzip vs pbzip. pbzip can be way faster. You need to use a type starting with p for multi-core compression. The compressible of the data plays a big factor in speed.
– cybernard
Apr 24 '16 at 15:10
1
bad/weak sectors also significantly slow the drive down when it needs to ECC a lot of sectors.
– cybernard
Apr 24 '16 at 15:41
1
those are estimated times and can change at any point during the clone process, I agree with cybernard, the drive you are cloning from may have bad sectors or other performance issues.
– Moab
Apr 24 '16 at 16:19
1
You can press CTRL + C to cancel the current copy process. Just keep doing that until the cloning stops. After that you can just shut down normally.
– chue x
Apr 24 '16 at 16:53
I have exactly the same behavior, have you found a solution for your issue so could actually clone the disk?
– Thomas
Aug 22 '16 at 20:42
|
show 1 more comment
1
Compression makes a big difference pgzip vs pbzip. pbzip can be way faster. You need to use a type starting with p for multi-core compression. The compressible of the data plays a big factor in speed.
– cybernard
Apr 24 '16 at 15:10
1
bad/weak sectors also significantly slow the drive down when it needs to ECC a lot of sectors.
– cybernard
Apr 24 '16 at 15:41
1
those are estimated times and can change at any point during the clone process, I agree with cybernard, the drive you are cloning from may have bad sectors or other performance issues.
– Moab
Apr 24 '16 at 16:19
1
You can press CTRL + C to cancel the current copy process. Just keep doing that until the cloning stops. After that you can just shut down normally.
– chue x
Apr 24 '16 at 16:53
I have exactly the same behavior, have you found a solution for your issue so could actually clone the disk?
– Thomas
Aug 22 '16 at 20:42
1
1
Compression makes a big difference pgzip vs pbzip. pbzip can be way faster. You need to use a type starting with p for multi-core compression. The compressible of the data plays a big factor in speed.
– cybernard
Apr 24 '16 at 15:10
Compression makes a big difference pgzip vs pbzip. pbzip can be way faster. You need to use a type starting with p for multi-core compression. The compressible of the data plays a big factor in speed.
– cybernard
Apr 24 '16 at 15:10
1
1
bad/weak sectors also significantly slow the drive down when it needs to ECC a lot of sectors.
– cybernard
Apr 24 '16 at 15:41
bad/weak sectors also significantly slow the drive down when it needs to ECC a lot of sectors.
– cybernard
Apr 24 '16 at 15:41
1
1
those are estimated times and can change at any point during the clone process, I agree with cybernard, the drive you are cloning from may have bad sectors or other performance issues.
– Moab
Apr 24 '16 at 16:19
those are estimated times and can change at any point during the clone process, I agree with cybernard, the drive you are cloning from may have bad sectors or other performance issues.
– Moab
Apr 24 '16 at 16:19
1
1
You can press CTRL + C to cancel the current copy process. Just keep doing that until the cloning stops. After that you can just shut down normally.
– chue x
Apr 24 '16 at 16:53
You can press CTRL + C to cancel the current copy process. Just keep doing that until the cloning stops. After that you can just shut down normally.
– chue x
Apr 24 '16 at 16:53
I have exactly the same behavior, have you found a solution for your issue so could actually clone the disk?
– Thomas
Aug 22 '16 at 20:42
I have exactly the same behavior, have you found a solution for your issue so could actually clone the disk?
– Thomas
Aug 22 '16 at 20:42
|
show 1 more comment
2 Answers
2
active
oldest
votes
i had the same issue , i was using Clonezilla from Parted.Magic 2017-06-12 to clone SSD->SSD sata3 , the speed was starting at 12GB/min but after 1min was droping to 5 and later to 1, after i boot it in 64bit mode (at parted magic select Default 64 instead of 32) the issue was gone, i got 9GB/min average at cloning 60GB.
answered Aug 7 '17 at 0:38
George DimaGeorge Dima
30819
add a comment |
I experienced this speed degradation many times on different setups. It usually happen when recovering data from failing(but somehow still working) HDD.
This solution helped me in one of such cases:
- while still in Clonezilla, notice what is your source and target
partitions and disks (for example source:/dev/sda1 target:/dev/sdb1) It is very important, otherwise you will rewrite your data. - cancel Clonezilla cloning process (Ctrl+C) and enter command line prompt
- $sudo ddrescue -n --force /dev/{your source partition} /dev/{your target partition} myrecoverylog.txt
-n options postpone recovery of most hard to read blocks until the end of the process, so you may even skip recovery of them with Ctrl+C.
Here, on ddrescue page are details:
https://www.gnu.org/software/ddrescue/manual/ddrescue_manual.html
answered Aug 17 '18 at 8:22
AndreiAndrei
1456
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%2f1069206%2fclonezilla-disk-to-image-speed-decreasing-over-time%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
i had the same issue , i was using Clonezilla from Parted.Magic 2017-06-12 to clone SSD->SSD sata3 , the speed was starting at 12GB/min but after 1min was droping to 5 and later to 1, after i boot it in 64bit mode (at parted magic select Default 64 instead of 32) the issue was gone, i got 9GB/min average at cloning 60GB.
answered Aug 7 '17 at 0:38
George DimaGeorge Dima
30819
add a comment |
i had the same issue , i was using Clonezilla from Parted.Magic 2017-06-12 to clone SSD->SSD sata3 , the speed was starting at 12GB/min but after 1min was droping to 5 and later to 1, after i boot it in 64bit mode (at parted magic select Default 64 instead of 32) the issue was gone, i got 9GB/min average at cloning 60GB.
answered Aug 7 '17 at 0:38
George DimaGeorge Dima
30819
add a comment |
i had the same issue , i was using Clonezilla from Parted.Magic 2017-06-12 to clone SSD->SSD sata3 , the speed was starting at 12GB/min but after 1min was droping to 5 and later to 1, after i boot it in 64bit mode (at parted magic select Default 64 instead of 32) the issue was gone, i got 9GB/min average at cloning 60GB.
answered Aug 7 '17 at 0:38
George DimaGeorge Dima
30819
i had the same issue , i was using Clonezilla from Parted.Magic 2017-06-12 to clone SSD->SSD sata3 , the speed was starting at 12GB/min but after 1min was droping to 5 and later to 1, after i boot it in 64bit mode (at parted magic select Default 64 instead of 32) the issue was gone, i got 9GB/min average at cloning 60GB.
answered Aug 7 '17 at 0:38
George DimaGeorge Dima
30819
answered Aug 7 '17 at 0:38
George DimaGeorge Dima
30819
answered Aug 7 '17 at 0:38
George DimaGeorge Dima
30819
answered Aug 7 '17 at 0:38
George DimaGeorge Dima
30819
30819
add a comment |
add a comment |
I experienced this speed degradation many times on different setups. It usually happen when recovering data from failing(but somehow still working) HDD.
This solution helped me in one of such cases:
- while still in Clonezilla, notice what is your source and target
partitions and disks (for example source:/dev/sda1 target:/dev/sdb1) It is very important, otherwise you will rewrite your data. - cancel Clonezilla cloning process (Ctrl+C) and enter command line prompt
- $sudo ddrescue -n --force /dev/{your source partition} /dev/{your target partition} myrecoverylog.txt
-n options postpone recovery of most hard to read blocks until the end of the process, so you may even skip recovery of them with Ctrl+C.
Here, on ddrescue page are details:
https://www.gnu.org/software/ddrescue/manual/ddrescue_manual.html
answered Aug 17 '18 at 8:22
AndreiAndrei
1456
add a comment |
I experienced this speed degradation many times on different setups. It usually happen when recovering data from failing(but somehow still working) HDD.
This solution helped me in one of such cases:
- while still in Clonezilla, notice what is your source and target
partitions and disks (for example source:/dev/sda1 target:/dev/sdb1) It is very important, otherwise you will rewrite your data. - cancel Clonezilla cloning process (Ctrl+C) and enter command line prompt
- $sudo ddrescue -n --force /dev/{your source partition} /dev/{your target partition} myrecoverylog.txt
-n options postpone recovery of most hard to read blocks until the end of the process, so you may even skip recovery of them with Ctrl+C.
Here, on ddrescue page are details:
https://www.gnu.org/software/ddrescue/manual/ddrescue_manual.html
answered Aug 17 '18 at 8:22
AndreiAndrei
1456
add a comment |
I experienced this speed degradation many times on different setups. It usually happen when recovering data from failing(but somehow still working) HDD.
This solution helped me in one of such cases:
- while still in Clonezilla, notice what is your source and target
partitions and disks (for example source:/dev/sda1 target:/dev/sdb1) It is very important, otherwise you will rewrite your data. - cancel Clonezilla cloning process (Ctrl+C) and enter command line prompt
- $sudo ddrescue -n --force /dev/{your source partition} /dev/{your target partition} myrecoverylog.txt
-n options postpone recovery of most hard to read blocks until the end of the process, so you may even skip recovery of them with Ctrl+C.
Here, on ddrescue page are details:
https://www.gnu.org/software/ddrescue/manual/ddrescue_manual.html
answered Aug 17 '18 at 8:22
AndreiAndrei
1456
I experienced this speed degradation many times on different setups. It usually happen when recovering data from failing(but somehow still working) HDD.
This solution helped me in one of such cases:
- while still in Clonezilla, notice what is your source and target
partitions and disks (for example source:/dev/sda1 target:/dev/sdb1) It is very important, otherwise you will rewrite your data. - cancel Clonezilla cloning process (Ctrl+C) and enter command line prompt
- $sudo ddrescue -n --force /dev/{your source partition} /dev/{your target partition} myrecoverylog.txt
-n options postpone recovery of most hard to read blocks until the end of the process, so you may even skip recovery of them with Ctrl+C.
Here, on ddrescue page are details:
https://www.gnu.org/software/ddrescue/manual/ddrescue_manual.html
answered Aug 17 '18 at 8:22
AndreiAndrei
1456
answered Aug 17 '18 at 8:22
AndreiAndrei
1456
answered Aug 17 '18 at 8:22
AndreiAndrei
1456
answered Aug 17 '18 at 8:22
AndreiAndrei
1456
1456
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%2f1069206%2fclonezilla-disk-to-image-speed-decreasing-over-time%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
1
Compression makes a big difference pgzip vs pbzip. pbzip can be way faster. You need to use a type starting with p for multi-core compression. The compressible of the data plays a big factor in speed.
– cybernard
Apr 24 '16 at 15:10
1
bad/weak sectors also significantly slow the drive down when it needs to ECC a lot of sectors.
– cybernard
Apr 24 '16 at 15:41
1
those are estimated times and can change at any point during the clone process, I agree with cybernard, the drive you are cloning from may have bad sectors or other performance issues.
– Moab
Apr 24 '16 at 16:19
1
You can press CTRL + C to cancel the current copy process. Just keep doing that until the cloning stops. After that you can just shut down normally.
– chue x
Apr 24 '16 at 16:53
I have exactly the same behavior, have you found a solution for your issue so could actually clone the disk?
– Thomas
Aug 22 '16 at 20:42