Sata SSD to M.2 SSD NVMe
A partition and disk imaging/cloning program
Brought to you by:
steven_shiau
Hi, im trying to clone from one computer to other computer remotely in same subnetwork, on source pc i have Sata SSD drive, on target machine i have M.2 SSD Nvme, when i try to clone, it gives me error "Failed to create the partition table on the target device: /dev/nvme0n1, im using newest stable version of clonezilla. Can someone help me solve this issue?
I found some discussion about NVMe grub compatibility issue
http://forums.debian.net/viewtopic.php?f=17&t=128212
https://ubuntuforums.org/showthread.php?t=2325056
Sorry that I don't have NVMe SSD, we might need some time to build lab environment to reproduce this issue and find how to solve it.
"im using newest stable version of clonezilla. " -> How about Clonezilla live 2.5.0-25?
http://clonezilla.org/downloads.php
Any difference?
If the issue still remains, please post the whole error messages, you can provide the file /var/log/clonezilla.org and /var/log/partclone.log, too.
Thanks.
Steven
Hi,
Just wondering if this was ever resolved. I'm also trying to clone SATA to NVMe and get an error message "Is this disk too small: /dev/sda", and I get the same message even when I tried going NVMe to SATA. Both disks are 256gb SSDs.
I'm using the most recent stable version of clonezilla, and have tried the alternative stable as well. I tried using -icds and -k1 (and other -k options) in many combinations to no avail.
Any advice on this matter would be greatly appreciated! I have not tried the specific version posted above (2.5.0-25), but will do so and get back to you.
Thanks,
Bit
It's been a long time about this issue. Please give the latest stable Clonezilla live, like 2.5.6-22 or 20180812-bionic:
https://clonezilla.org/downloads.php
Please also try to enter expert mode, and choose the option "-k1".
Steven
Just verifying that I was able to use clonezilla-live-20210609-hirsute-amd64 to successfully clone from SSD to M.2 , It was Windows 10 v1909, and other than having to change the BIOS to AHCI, and wait a bit for the os to recognized new hardware... all went fine. Thanks Clonezilla :-)
Thank, Gary. Was your M.2 an NVME drive? We still have not been able to clone back and forth from NVME to SATA. Ours are dual-boot iMacs.
From: GarryS gschindler@users.sourceforge.net
Sent: Friday, August 13, 2021 12:59 PM
To: [clonezilla:support-requests] 93@support-requests.clonezilla.p.re.sourceforge.net
Subject: [clonezilla:support-requests] #93 Sata SSD to M.2 SSD NVMe
Just verifying that I was able to use clonezilla-live-20210609-hirsute-amd64 to successfully clone from SSD to M.2 , It was Windows 10 v1909, and other than having to change the BIOS to AHCI, and wait a bit for the os to recognized new hardware... all went fine. Thanks Clonezilla :-)
[support-requests:#93]https://sourceforge.net/p/clonezilla/support-requests/93/ Sata SSD to M.2 SSD NVMe
Status: open
Group: clonezilla live stable
Labels: ssd nvme nvme0n1
Created: Wed Feb 22, 2017 06:38 AM UTC by Bojan Simic
Last Updated: Sun Aug 19, 2018 12:25 PM UTC
Owner: Jazz Yao-Tsung Wang
Hi, im trying to clone from one computer to other computer remotely in same subnetwork, on source pc i have Sata SSD drive, on target machine i have M.2 SSD Nvme, when i try to clone, it gives me error "Failed to create the partition table on the target device: /dev/nvme0n1, im using newest stable version of clonezilla. Can someone help me solve this issue?
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/clonezilla/support-requests/93/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Related
Support Requests: #93
I think so. The stick is labeled as Model CX2-BB256-Q11 NVMe LITEON 256GB. It was in a Dell Optiplex 7050, and the SSD I cloned it from was a SuperTalent FTM56N325H if that helps you any.
The image was good enough that SFC and DISM saw no issues. I also was able to run the update to windows 10 20H2 with no issues. All seems ok, at least so far. I wonder if the BIOS settings have a big effect on the process. It was NOT set to UEFI. Would those settings help you?
Last edit: GarryS 2021-08-13