Cloning a SSD using GPT not working (Clonezilla)
I am using Windows 8.1 Pro installed on a 128 GB SSD, partition-table is GPT. My Asus Mainboard uses UEFI and i installed windows 8.1 as a uefi installation. Therefore the first boot device is selected as "Windows Boot Manager", it's perfectly working and it's really fast. Now i bought a new bigger SSD. I plugged it in and booted with clonezilla to clone the whole disk (disk2disk mode) to the new SSD.
I cloned it, turned the pc off and disconnected the old ssd. Turned it on and it didn't start windows, after the EFI-initialization it stayed black. Now i booted with a windows 8.1 stick(only my new cloned ssd is plugged in) and selected the "computer repair options" and navigated to trouble shooting and used the automatic repair.
I waited about ~a hour and assumed that it crashed (allthough the circle was still moving). I restarted and tried it again now i am getting instantly the error message that automatic repair couldnt fix my problem.
The only option is to run the terminal and try to fix it.
What can i do in order to use my new SSD with my old windows installation. A complete new installation is no option at the moment.
Thank you very much.
windows boot partitioning ssd uefi
asked Feb 7 '15 at 14:27
UDE_StudentUDE_Student
614
add a comment |
I am using Windows 8.1 Pro installed on a 128 GB SSD, partition-table is GPT. My Asus Mainboard uses UEFI and i installed windows 8.1 as a uefi installation. Therefore the first boot device is selected as "Windows Boot Manager", it's perfectly working and it's really fast. Now i bought a new bigger SSD. I plugged it in and booted with clonezilla to clone the whole disk (disk2disk mode) to the new SSD.
I cloned it, turned the pc off and disconnected the old ssd. Turned it on and it didn't start windows, after the EFI-initialization it stayed black. Now i booted with a windows 8.1 stick(only my new cloned ssd is plugged in) and selected the "computer repair options" and navigated to trouble shooting and used the automatic repair.
I waited about ~a hour and assumed that it crashed (allthough the circle was still moving). I restarted and tried it again now i am getting instantly the error message that automatic repair couldnt fix my problem.
The only option is to run the terminal and try to fix it.
What can i do in order to use my new SSD with my old windows installation. A complete new installation is no option at the moment.
Thank you very much.
windows boot partitioning ssd uefi
asked Feb 7 '15 at 14:27
UDE_StudentUDE_Student
614
Not sure why it made the difference, but I've found running the clone process with the new SSD mounted via an external USB enclosure works for me. Have done 2 machines that way, but I cloned with Acronis, not clonezilla.
– Tetsujin
Feb 7 '15 at 14:41
The “Windows Boot Manager” entry is tightly coupled to the device path and maybe even partition UUID. TLDR: Follow the instructions outlined in this answer to repair the boot entry.
– Daniel B
Feb 7 '15 at 14:49
possible duplicate of How can I repair the Windows 8 EFI Bootloader?
– Daniel B
Feb 7 '15 at 14:49
Thanks for the link. I tried that that but it doesnt work.
– UDE_Student
Feb 7 '15 at 14:59
add a comment |
I am using Windows 8.1 Pro installed on a 128 GB SSD, partition-table is GPT. My Asus Mainboard uses UEFI and i installed windows 8.1 as a uefi installation. Therefore the first boot device is selected as "Windows Boot Manager", it's perfectly working and it's really fast. Now i bought a new bigger SSD. I plugged it in and booted with clonezilla to clone the whole disk (disk2disk mode) to the new SSD.
I cloned it, turned the pc off and disconnected the old ssd. Turned it on and it didn't start windows, after the EFI-initialization it stayed black. Now i booted with a windows 8.1 stick(only my new cloned ssd is plugged in) and selected the "computer repair options" and navigated to trouble shooting and used the automatic repair.
I waited about ~a hour and assumed that it crashed (allthough the circle was still moving). I restarted and tried it again now i am getting instantly the error message that automatic repair couldnt fix my problem.
The only option is to run the terminal and try to fix it.
What can i do in order to use my new SSD with my old windows installation. A complete new installation is no option at the moment.
Thank you very much.
windows boot partitioning ssd uefi
asked Feb 7 '15 at 14:27
UDE_StudentUDE_Student
614
I am using Windows 8.1 Pro installed on a 128 GB SSD, partition-table is GPT. My Asus Mainboard uses UEFI and i installed windows 8.1 as a uefi installation. Therefore the first boot device is selected as "Windows Boot Manager", it's perfectly working and it's really fast. Now i bought a new bigger SSD. I plugged it in and booted with clonezilla to clone the whole disk (disk2disk mode) to the new SSD.
I cloned it, turned the pc off and disconnected the old ssd. Turned it on and it didn't start windows, after the EFI-initialization it stayed black. Now i booted with a windows 8.1 stick(only my new cloned ssd is plugged in) and selected the "computer repair options" and navigated to trouble shooting and used the automatic repair.
I waited about ~a hour and assumed that it crashed (allthough the circle was still moving). I restarted and tried it again now i am getting instantly the error message that automatic repair couldnt fix my problem.
The only option is to run the terminal and try to fix it.
What can i do in order to use my new SSD with my old windows installation. A complete new installation is no option at the moment.
Thank you very much.
windows boot partitioning ssd uefi
windows boot partitioning ssd uefi
asked Feb 7 '15 at 14:27
UDE_StudentUDE_Student
614
asked Feb 7 '15 at 14:27
UDE_StudentUDE_Student
614
asked Feb 7 '15 at 14:27
UDE_StudentUDE_Student
614
asked Feb 7 '15 at 14:27
UDE_StudentUDE_Student
614
asked Feb 7 '15 at 14:27
UDE_StudentUDE_Student
614
614
Not sure why it made the difference, but I've found running the clone process with the new SSD mounted via an external USB enclosure works for me. Have done 2 machines that way, but I cloned with Acronis, not clonezilla.
– Tetsujin
Feb 7 '15 at 14:41
The “Windows Boot Manager” entry is tightly coupled to the device path and maybe even partition UUID. TLDR: Follow the instructions outlined in this answer to repair the boot entry.
– Daniel B
Feb 7 '15 at 14:49
possible duplicate of How can I repair the Windows 8 EFI Bootloader?
– Daniel B
Feb 7 '15 at 14:49
Thanks for the link. I tried that that but it doesnt work.
– UDE_Student
Feb 7 '15 at 14:59
add a comment |
Not sure why it made the difference, but I've found running the clone process with the new SSD mounted via an external USB enclosure works for me. Have done 2 machines that way, but I cloned with Acronis, not clonezilla.
– Tetsujin
Feb 7 '15 at 14:41
The “Windows Boot Manager” entry is tightly coupled to the device path and maybe even partition UUID. TLDR: Follow the instructions outlined in this answer to repair the boot entry.
– Daniel B
Feb 7 '15 at 14:49
possible duplicate of How can I repair the Windows 8 EFI Bootloader?
– Daniel B
Feb 7 '15 at 14:49
Thanks for the link. I tried that that but it doesnt work.
– UDE_Student
Feb 7 '15 at 14:59
Not sure why it made the difference, but I've found running the clone process with the new SSD mounted via an external USB enclosure works for me. Have done 2 machines that way, but I cloned with Acronis, not clonezilla.
– Tetsujin
Feb 7 '15 at 14:41
Not sure why it made the difference, but I've found running the clone process with the new SSD mounted via an external USB enclosure works for me. Have done 2 machines that way, but I cloned with Acronis, not clonezilla.
– Tetsujin
Feb 7 '15 at 14:41
The “Windows Boot Manager” entry is tightly coupled to the device path and maybe even partition UUID. TLDR: Follow the instructions outlined in this answer to repair the boot entry.
– Daniel B
Feb 7 '15 at 14:49
The “Windows Boot Manager” entry is tightly coupled to the device path and maybe even partition UUID. TLDR: Follow the instructions outlined in this answer to repair the boot entry.
– Daniel B
Feb 7 '15 at 14:49
possible duplicate of How can I repair the Windows 8 EFI Bootloader?
– Daniel B
Feb 7 '15 at 14:49
possible duplicate of How can I repair the Windows 8 EFI Bootloader?
– Daniel B
Feb 7 '15 at 14:49
Thanks for the link. I tried that that but it doesnt work.
– UDE_Student
Feb 7 '15 at 14:59
Thanks for the link. I tried that that but it doesnt work.
– UDE_Student
Feb 7 '15 at 14:59
add a comment |
1 Answer
1
active
oldest
votes
I don't know if the problem is exactly the same as mine. But I left here my cent.
I have tried a disc to disc clone from a 930GiB HDD (source drive) with a GPT partition table to 890GiB SSD (destination). Please note I am a Linux user and I have a dual boot with windows 10. I have tried to left unchanged all the partitions and to reduce slightly the size of my data partition only.
- With gparted, I resized the bigger data partition in order to have an overall size that fits the destination SSD, and moved all free space at the end
- I used clonezilla-Live from USB pen, with advanced mode and -icds enabled.
It failed. It looks like Clonezilla fails, at start, to clone the partition table to the destination disk because it wrongly uses sfdisk utility that is for older partition types instead of sgdisk utils.
My solution:
- The same as previous (overall size must fit)
I manually copied the partition from one drive to another, using Clonezilla shell with this command:
sgdisk /dev/sdSourceDeviceName -R /dev/sdDestinationDeviceName
Performed Clonezilla disc-to-disc clone, selecting the option
-icdsand the option to NOT CREATE a partition table on destination disk, option-k. (In this case Clonezilla uses the destination partitions as they are, and resizes partitions when sizes are smaller, in order to fit, it perform a good "best effort").
It worked. I obtained all the partitions the same size as source (Yes I only reduced the bigger partition a bit).
Why it worked The problem was with the automated procedure that is not able to clone&adapt the GPT table to the destination disc, the step 2 performs manually this step in the right way.
Dual boot with windows keeps working well.
Regards
answered Apr 18 '17 at 7:16
Fabiano TarlaoFabiano Tarlao
1135
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%2f874952%2fcloning-a-ssd-using-gpt-not-working-clonezilla%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
I don't know if the problem is exactly the same as mine. But I left here my cent.
I have tried a disc to disc clone from a 930GiB HDD (source drive) with a GPT partition table to 890GiB SSD (destination). Please note I am a Linux user and I have a dual boot with windows 10. I have tried to left unchanged all the partitions and to reduce slightly the size of my data partition only.
- With gparted, I resized the bigger data partition in order to have an overall size that fits the destination SSD, and moved all free space at the end
- I used clonezilla-Live from USB pen, with advanced mode and -icds enabled.
It failed. It looks like Clonezilla fails, at start, to clone the partition table to the destination disk because it wrongly uses sfdisk utility that is for older partition types instead of sgdisk utils.
My solution:
- The same as previous (overall size must fit)
I manually copied the partition from one drive to another, using Clonezilla shell with this command:
sgdisk /dev/sdSourceDeviceName -R /dev/sdDestinationDeviceName
Performed Clonezilla disc-to-disc clone, selecting the option
-icdsand the option to NOT CREATE a partition table on destination disk, option-k. (In this case Clonezilla uses the destination partitions as they are, and resizes partitions when sizes are smaller, in order to fit, it perform a good "best effort").
It worked. I obtained all the partitions the same size as source (Yes I only reduced the bigger partition a bit).
Why it worked The problem was with the automated procedure that is not able to clone&adapt the GPT table to the destination disc, the step 2 performs manually this step in the right way.
Dual boot with windows keeps working well.
Regards
answered Apr 18 '17 at 7:16
Fabiano TarlaoFabiano Tarlao
1135
add a comment |
I don't know if the problem is exactly the same as mine. But I left here my cent.
I have tried a disc to disc clone from a 930GiB HDD (source drive) with a GPT partition table to 890GiB SSD (destination). Please note I am a Linux user and I have a dual boot with windows 10. I have tried to left unchanged all the partitions and to reduce slightly the size of my data partition only.
- With gparted, I resized the bigger data partition in order to have an overall size that fits the destination SSD, and moved all free space at the end
- I used clonezilla-Live from USB pen, with advanced mode and -icds enabled.
It failed. It looks like Clonezilla fails, at start, to clone the partition table to the destination disk because it wrongly uses sfdisk utility that is for older partition types instead of sgdisk utils.
My solution:
- The same as previous (overall size must fit)
I manually copied the partition from one drive to another, using Clonezilla shell with this command:
sgdisk /dev/sdSourceDeviceName -R /dev/sdDestinationDeviceName
Performed Clonezilla disc-to-disc clone, selecting the option
-icdsand the option to NOT CREATE a partition table on destination disk, option-k. (In this case Clonezilla uses the destination partitions as they are, and resizes partitions when sizes are smaller, in order to fit, it perform a good "best effort").
It worked. I obtained all the partitions the same size as source (Yes I only reduced the bigger partition a bit).
Why it worked The problem was with the automated procedure that is not able to clone&adapt the GPT table to the destination disc, the step 2 performs manually this step in the right way.
Dual boot with windows keeps working well.
Regards
answered Apr 18 '17 at 7:16
Fabiano TarlaoFabiano Tarlao
1135
add a comment |
I don't know if the problem is exactly the same as mine. But I left here my cent.
I have tried a disc to disc clone from a 930GiB HDD (source drive) with a GPT partition table to 890GiB SSD (destination). Please note I am a Linux user and I have a dual boot with windows 10. I have tried to left unchanged all the partitions and to reduce slightly the size of my data partition only.
- With gparted, I resized the bigger data partition in order to have an overall size that fits the destination SSD, and moved all free space at the end
- I used clonezilla-Live from USB pen, with advanced mode and -icds enabled.
It failed. It looks like Clonezilla fails, at start, to clone the partition table to the destination disk because it wrongly uses sfdisk utility that is for older partition types instead of sgdisk utils.
My solution:
- The same as previous (overall size must fit)
I manually copied the partition from one drive to another, using Clonezilla shell with this command:
sgdisk /dev/sdSourceDeviceName -R /dev/sdDestinationDeviceName
Performed Clonezilla disc-to-disc clone, selecting the option
-icdsand the option to NOT CREATE a partition table on destination disk, option-k. (In this case Clonezilla uses the destination partitions as they are, and resizes partitions when sizes are smaller, in order to fit, it perform a good "best effort").
It worked. I obtained all the partitions the same size as source (Yes I only reduced the bigger partition a bit).
Why it worked The problem was with the automated procedure that is not able to clone&adapt the GPT table to the destination disc, the step 2 performs manually this step in the right way.
Dual boot with windows keeps working well.
Regards
answered Apr 18 '17 at 7:16
Fabiano TarlaoFabiano Tarlao
1135
I don't know if the problem is exactly the same as mine. But I left here my cent.
I have tried a disc to disc clone from a 930GiB HDD (source drive) with a GPT partition table to 890GiB SSD (destination). Please note I am a Linux user and I have a dual boot with windows 10. I have tried to left unchanged all the partitions and to reduce slightly the size of my data partition only.
- With gparted, I resized the bigger data partition in order to have an overall size that fits the destination SSD, and moved all free space at the end
- I used clonezilla-Live from USB pen, with advanced mode and -icds enabled.
It failed. It looks like Clonezilla fails, at start, to clone the partition table to the destination disk because it wrongly uses sfdisk utility that is for older partition types instead of sgdisk utils.
My solution:
- The same as previous (overall size must fit)
I manually copied the partition from one drive to another, using Clonezilla shell with this command:
sgdisk /dev/sdSourceDeviceName -R /dev/sdDestinationDeviceName
Performed Clonezilla disc-to-disc clone, selecting the option
-icdsand the option to NOT CREATE a partition table on destination disk, option-k. (In this case Clonezilla uses the destination partitions as they are, and resizes partitions when sizes are smaller, in order to fit, it perform a good "best effort").
It worked. I obtained all the partitions the same size as source (Yes I only reduced the bigger partition a bit).
Why it worked The problem was with the automated procedure that is not able to clone&adapt the GPT table to the destination disc, the step 2 performs manually this step in the right way.
Dual boot with windows keeps working well.
Regards
answered Apr 18 '17 at 7:16
Fabiano TarlaoFabiano Tarlao
1135
edited Aug 3 '17 at 13:54
answered Apr 18 '17 at 7:16
Fabiano TarlaoFabiano Tarlao
1135
answered Apr 18 '17 at 7:16
Fabiano TarlaoFabiano Tarlao
1135
answered Apr 18 '17 at 7:16
Fabiano TarlaoFabiano Tarlao
1135
1135
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%2f874952%2fcloning-a-ssd-using-gpt-not-working-clonezilla%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
Not sure why it made the difference, but I've found running the clone process with the new SSD mounted via an external USB enclosure works for me. Have done 2 machines that way, but I cloned with Acronis, not clonezilla.
– Tetsujin
Feb 7 '15 at 14:41
The “Windows Boot Manager” entry is tightly coupled to the device path and maybe even partition UUID. TLDR: Follow the instructions outlined in this answer to repair the boot entry.
– Daniel B
Feb 7 '15 at 14:49
possible duplicate of How can I repair the Windows 8 EFI Bootloader?
– Daniel B
Feb 7 '15 at 14:49
Thanks for the link. I tried that that but it doesnt work.
– UDE_Student
Feb 7 '15 at 14:59