The source SSD plays up: ocassional blue screening, PC powers off and fails to recongise it on reboot. Fiddling with SATA cables usually helps for a week or so.
Some SSD helth check tools indicate minor degradation (94-97% healthy).
Is it worth enabling -fsck mode?
I'm assuming that the sizes are identical but can't find a data sheet for the SSD.
AFAIK SSDs are factory overprovisioned so that worn / faulty sectors can be replaced on the fly.
Do NMVEs use similar mechanisms?
Is it too of a low level to even be visible to Clonezilla and effect cloning in any way?
Destination NVMe is advertised as having 256-bit AES hardware encryption.
Is it an optional or mandatory feature?
Can it affect cloning in any way?
Is there anything else I've missed and should know about?
Cheers,
Adam
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For your questions,
1. Yes, if the file system integrity has some issue, Clonezilla will fail to clone it. Hence, if you are not sure its integrity, enable -fsck.
2. The destination device must be equal or larger than the source one. You have to make sure that. Of course, you can just give it a try. If it's not, Clonezilla will fail.
3. Clonezilla deals with the file system, not the low level hardware...
4. No idea. Maybe it's driven by some of the drivers...
//NOTE// Back important data before you use Clonezilla. Just in case.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for your reply Steven.
Unfortunately Clonezilla 2.6.3-7 failed to detect/recognise Intel Solid-State Drive 760P Series - 1.024 TB - PCI Express 3.1 X4 (NVMe).
Windows 10 didn't have this problem and I ended up doing the following: https://knowledgebase.macrium.com/display/KNOW7/Cloning+a+disk
which worked perfectly.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi all,
I'm planning to use the latest Clonezilla for cloning
ADATA ADM900S7-1TM-DL4 size: 953GiB (1024GB)
to
Intel Solid-State Drive 760P Series - 1.024 TB - PCI Express 3.1 X4 (NVMe)
https://www.uk.insight.com/en-gb/productinfo/internal-hard-disk-drives/0007688870-00000001
I have a couple concerns:
The source SSD plays up: ocassional blue screening, PC powers off and fails to recongise it on reboot. Fiddling with SATA cables usually helps for a week or so.
Some SSD helth check tools indicate minor degradation (94-97% healthy).
Is it worth enabling -fsck mode?
I'm assuming that the sizes are identical but can't find a data sheet for the SSD.
AFAIK SSDs are factory overprovisioned so that worn / faulty sectors can be replaced on the fly.
Do NMVEs use similar mechanisms?
Is it too of a low level to even be visible to Clonezilla and effect cloning in any way?
Destination NVMe is advertised as having 256-bit AES hardware encryption.
Is it an optional or mandatory feature?
Can it affect cloning in any way?
Is there anything else I've missed and should know about?
Cheers,
Adam
For your questions,
1. Yes, if the file system integrity has some issue, Clonezilla will fail to clone it. Hence, if you are not sure its integrity, enable -fsck.
2. The destination device must be equal or larger than the source one. You have to make sure that. Of course, you can just give it a try. If it's not, Clonezilla will fail.
3. Clonezilla deals with the file system, not the low level hardware...
4. No idea. Maybe it's driven by some of the drivers...
//NOTE// Back important data before you use Clonezilla. Just in case.
Steven
Thank you for your reply Steven.
Unfortunately Clonezilla 2.6.3-7 failed to detect/recognise Intel Solid-State Drive 760P Series - 1.024 TB - PCI Express 3.1 X4 (NVMe).
Windows 10 didn't have this problem and I ended up doing the following:
https://knowledgebase.macrium.com/display/KNOW7/Cloning+a+disk
which worked perfectly.
OK, sure. At least you found the solution.
Steven