Fully clone your system from a SATA device to a NVMe device
I am working on a laptop with a 500 GB SSD, dual booting on Windows and Ubuntu.
I recently bought a Samsung 960 EVO m.2 NVMe 500 GB SSD and installed it successfully. However, given the faster interface provided by NVMe compared to SATA/AHCI, I'd like to move my current systems to the NVMe SSD.
Reasonably enough, I used CloneZilla (You should (as always) get the latest stable release, as NVMe interfaced disks aren't recognized on older versions, that often come packaged with USB boot disk creating software such as lili USB creator) and cloned all the content from my SATA SSD to my NVMe SSD. As soon as I'll be able to boot on the NVMe SSD, i'll format the SATA SSD and use it as storage.
I had to work a lot with the UEFI before I was able to have the NVMe SSD available in the boot options. However, I did not have to mod my BIOS. It seems that it started to appear in the boot options as soon as I had a bootmgr on my NVMe SSD, that CloneZilla had cloned.
However, as you could expect, I got the same issue as I can boot from a clone, but only when the original drive isn't plugged in and I expected it.
I didn't change the drive's unique identifier yet, but I have a few concerns before I do it:
1) Since CloneZilla cloned all of the configuration of GRUB, if I boot on the GRUB of the NVMe SSD, Iget the GRUB, but of course, it still lists sda1 instead of nvme0n1p1, so it will boot on the SATA SSD. Would reinstalling GRUB solve this problem, or do I have a high risk of losing possibility to boot? I'd say that as long as I keep the data on both disks, installing GRUB would have GRUB list a) Ubuntu on /dev/nvme0n1p1 b) Windows boot manager on /dev/nvme0n1p2 c) Ubuntu on /dev/sda1 d) Windows boot manager on /dev/sda2
2) when I override the boot order to boot on Windows boot manager on the NVMe SSD, Windows doesn't boot, it gets stuck on the loading screen, without ever failing, just stuck. Would you think that is the consequence of trying to boot on a newer disk with the same drive ID as the old one (as The post that I mentioned earlier would suggest).
Would changing the drive's id solve this problem?
I know that all of this seems overly cautious, and that it seems like it wouldn't cost me much to try the solutions I've listed, but I'd rather be sure that I can go through and provide feedback to other users with the same issue than just blindly go into it without being entirely sure that it is safe.
boot ssd grub clonezilla nvme
add a comment |
I am working on a laptop with a 500 GB SSD, dual booting on Windows and Ubuntu.
I recently bought a Samsung 960 EVO m.2 NVMe 500 GB SSD and installed it successfully. However, given the faster interface provided by NVMe compared to SATA/AHCI, I'd like to move my current systems to the NVMe SSD.
Reasonably enough, I used CloneZilla (You should (as always) get the latest stable release, as NVMe interfaced disks aren't recognized on older versions, that often come packaged with USB boot disk creating software such as lili USB creator) and cloned all the content from my SATA SSD to my NVMe SSD. As soon as I'll be able to boot on the NVMe SSD, i'll format the SATA SSD and use it as storage.
I had to work a lot with the UEFI before I was able to have the NVMe SSD available in the boot options. However, I did not have to mod my BIOS. It seems that it started to appear in the boot options as soon as I had a bootmgr on my NVMe SSD, that CloneZilla had cloned.
However, as you could expect, I got the same issue as I can boot from a clone, but only when the original drive isn't plugged in and I expected it.
I didn't change the drive's unique identifier yet, but I have a few concerns before I do it:
1) Since CloneZilla cloned all of the configuration of GRUB, if I boot on the GRUB of the NVMe SSD, Iget the GRUB, but of course, it still lists sda1 instead of nvme0n1p1, so it will boot on the SATA SSD. Would reinstalling GRUB solve this problem, or do I have a high risk of losing possibility to boot? I'd say that as long as I keep the data on both disks, installing GRUB would have GRUB list a) Ubuntu on /dev/nvme0n1p1 b) Windows boot manager on /dev/nvme0n1p2 c) Ubuntu on /dev/sda1 d) Windows boot manager on /dev/sda2
2) when I override the boot order to boot on Windows boot manager on the NVMe SSD, Windows doesn't boot, it gets stuck on the loading screen, without ever failing, just stuck. Would you think that is the consequence of trying to boot on a newer disk with the same drive ID as the old one (as The post that I mentioned earlier would suggest).
Would changing the drive's id solve this problem?
I know that all of this seems overly cautious, and that it seems like it wouldn't cost me much to try the solutions I've listed, but I'd rather be sure that I can go through and provide feedback to other users with the same issue than just blindly go into it without being entirely sure that it is safe.
boot ssd grub clonezilla nvme
add a comment |
I am working on a laptop with a 500 GB SSD, dual booting on Windows and Ubuntu.
I recently bought a Samsung 960 EVO m.2 NVMe 500 GB SSD and installed it successfully. However, given the faster interface provided by NVMe compared to SATA/AHCI, I'd like to move my current systems to the NVMe SSD.
Reasonably enough, I used CloneZilla (You should (as always) get the latest stable release, as NVMe interfaced disks aren't recognized on older versions, that often come packaged with USB boot disk creating software such as lili USB creator) and cloned all the content from my SATA SSD to my NVMe SSD. As soon as I'll be able to boot on the NVMe SSD, i'll format the SATA SSD and use it as storage.
I had to work a lot with the UEFI before I was able to have the NVMe SSD available in the boot options. However, I did not have to mod my BIOS. It seems that it started to appear in the boot options as soon as I had a bootmgr on my NVMe SSD, that CloneZilla had cloned.
However, as you could expect, I got the same issue as I can boot from a clone, but only when the original drive isn't plugged in and I expected it.
I didn't change the drive's unique identifier yet, but I have a few concerns before I do it:
1) Since CloneZilla cloned all of the configuration of GRUB, if I boot on the GRUB of the NVMe SSD, Iget the GRUB, but of course, it still lists sda1 instead of nvme0n1p1, so it will boot on the SATA SSD. Would reinstalling GRUB solve this problem, or do I have a high risk of losing possibility to boot? I'd say that as long as I keep the data on both disks, installing GRUB would have GRUB list a) Ubuntu on /dev/nvme0n1p1 b) Windows boot manager on /dev/nvme0n1p2 c) Ubuntu on /dev/sda1 d) Windows boot manager on /dev/sda2
2) when I override the boot order to boot on Windows boot manager on the NVMe SSD, Windows doesn't boot, it gets stuck on the loading screen, without ever failing, just stuck. Would you think that is the consequence of trying to boot on a newer disk with the same drive ID as the old one (as The post that I mentioned earlier would suggest).
Would changing the drive's id solve this problem?
I know that all of this seems overly cautious, and that it seems like it wouldn't cost me much to try the solutions I've listed, but I'd rather be sure that I can go through and provide feedback to other users with the same issue than just blindly go into it without being entirely sure that it is safe.
boot ssd grub clonezilla nvme
I am working on a laptop with a 500 GB SSD, dual booting on Windows and Ubuntu.
I recently bought a Samsung 960 EVO m.2 NVMe 500 GB SSD and installed it successfully. However, given the faster interface provided by NVMe compared to SATA/AHCI, I'd like to move my current systems to the NVMe SSD.
Reasonably enough, I used CloneZilla (You should (as always) get the latest stable release, as NVMe interfaced disks aren't recognized on older versions, that often come packaged with USB boot disk creating software such as lili USB creator) and cloned all the content from my SATA SSD to my NVMe SSD. As soon as I'll be able to boot on the NVMe SSD, i'll format the SATA SSD and use it as storage.
I had to work a lot with the UEFI before I was able to have the NVMe SSD available in the boot options. However, I did not have to mod my BIOS. It seems that it started to appear in the boot options as soon as I had a bootmgr on my NVMe SSD, that CloneZilla had cloned.
However, as you could expect, I got the same issue as I can boot from a clone, but only when the original drive isn't plugged in and I expected it.
I didn't change the drive's unique identifier yet, but I have a few concerns before I do it:
1) Since CloneZilla cloned all of the configuration of GRUB, if I boot on the GRUB of the NVMe SSD, Iget the GRUB, but of course, it still lists sda1 instead of nvme0n1p1, so it will boot on the SATA SSD. Would reinstalling GRUB solve this problem, or do I have a high risk of losing possibility to boot? I'd say that as long as I keep the data on both disks, installing GRUB would have GRUB list a) Ubuntu on /dev/nvme0n1p1 b) Windows boot manager on /dev/nvme0n1p2 c) Ubuntu on /dev/sda1 d) Windows boot manager on /dev/sda2
2) when I override the boot order to boot on Windows boot manager on the NVMe SSD, Windows doesn't boot, it gets stuck on the loading screen, without ever failing, just stuck. Would you think that is the consequence of trying to boot on a newer disk with the same drive ID as the old one (as The post that I mentioned earlier would suggest).
Would changing the drive's id solve this problem?
I know that all of this seems overly cautious, and that it seems like it wouldn't cost me much to try the solutions I've listed, but I'd rather be sure that I can go through and provide feedback to other users with the same issue than just blindly go into it without being entirely sure that it is safe.
boot ssd grub clonezilla nvme
boot ssd grub clonezilla nvme
asked Dec 2 at 7:42
PoutchiPatch
17119
17119
add a comment |
add a comment |
active
oldest
votes
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%2f1380127%2ffully-clone-your-system-from-a-sata-device-to-a-nvme-device%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f1380127%2ffully-clone-your-system-from-a-sata-device-to-a-nvme-device%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