Cloning a Drive in Linux via Commands: Difference between revisions

Line 66:

** Before the 'new' Drive is installed, make sure to check the /etc/fstab file and make sure all the other expected Drives are there, otherwise comment them out.

** And finally, run this just to make sure everything is written to the Source Drive (mostly for the sake of USB mounted Drives): <code>sync</code>

=== Scripting ===

Of course all this will be scripted in the future. So basically Acronis for Linux.

=== And for the Critics ===

nvme1n1p1 and nvme1n1p2: Yes it would be great if a SnapShot could be taken of these too, but as far as research and experiments have shown, UEFI will not tolerate that, so it won't work. Plus, realistically, what's gonna change on those Partitions in the brief time DD is running for them? Hint: NOTHING!

SWAP: Yes, the SWAP partition could just be recreated, and it won't be consistent, etc. when cloned with DD, but it doesn't make a difference at all because when the cloned system boots, the SWAP Partition is essentially reset. Interesting question on which is faster, and whether one could run the various commands to create a new SWAP Partition, with the same parameters, UUID, etc. VS running the DD restore command.

SWAP: Yes, the SWAP partition could just be recreated, and it won't be consistent, etc. when cloned with DD, but it doesn't make a difference at all because when the cloned system boots, the SWAP Partition is essentially reset. Interesting question on which is faster, and debatable whether one could run the various commands to create a new SWAP Partition, with the same parameters, UUID, etc. VS running the DD restore command, with the former being faster than the latter.

@@ Line 66: / Line 66: @@
 ** Before the 'new' Drive is installed, make sure to check the /etc/fstab file and make sure all the other expected Drives are there, otherwise comment them out.
 ** And finally, run this just to make sure everything is written to the Source Drive (mostly for the sake of USB mounted Drives): <code>sync</code>
+=== Scripting ===
+Of course all this will be scripted in the future.  So basically Acronis for Linux.
 === And for the Critics ===
 nvme1n1p1 and nvme1n1p2: Yes it would be great if a SnapShot could be taken of these too, but as far as research and experiments have shown, UEFI will not tolerate that, so it won't work.  Plus, realistically, what's gonna change on those Partitions in the brief time DD is running for them?  Hint: NOTHING!
-SWAP: Yes, the SWAP partition could just be recreated, and it won't be consistent, etc. when cloned with DD, but it doesn't make a difference at all because when the cloned system boots, the SWAP Partition is essentially reset.  Interesting question on which is faster, and whether one could run the various commands to create a new SWAP Partition, with the same parameters, UUID, etc. VS running the DD restore command.
+SWAP: Yes, the SWAP partition could just be recreated, and it won't be consistent, etc. when cloned with DD, but it doesn't make a difference at all because when the cloned system boots, the SWAP Partition is essentially reset.  Interesting question on which is faster, and debatable whether one could run the various commands to create a new SWAP Partition, with the same parameters, UUID, etc. VS running the DD restore command, with the former being faster than the latter.