Clonezilla performs the exact same clone 5 different times. It goes straight from 100% of cloning sdb1 to sda1 into doing it all over again. It's taking hours. Help.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
What were the steps you have done? What was the error message? Please take some photos then post them. It would be easier for us to understand what went wrong there.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think I have the same problem. I only tested with the ubuntu version ( 202010127-groovy). And gave up after the third loop.
I want to migrate (clone) a SSD (960G) to another SSD (1024G). The origin has a proxmox system installed with several containers and VMs in use.
I used the "to RAM" boot option. Then selected "device-device", "beginners", and then "disk_to_local_disk". I selected the correct disks, and started the process.
The third partition (sda3, the big one) enters in the loop, 1.5 hours each. The previous 2 partitions (/boot, and /root I think) finish cloning fast and just once.
I have attached 5 images. They come from a video I took the second time it happened. The name of the file is the frame in the video, so they are numerically in order.
"202010127-groovy" -> Have you tried the latest Clonezilla live 2.7.1-22 or 20210127-groovy? https://clonezilla.org/downloads.php
Is this issue also reproducible?
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It happened to me exactly the same problem, cloning a Proxmox installation. Eventually it succeeded, because I don't have many VMs. As far as I can tell it worked everything as expected. But how would I check?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Clonezilla performs the exact same clone 5 different times. It goes straight from 100% of cloning sdb1 to sda1 into doing it all over again. It's taking hours. Help.
Which version of Clonezilla live did you use? What were the steps? You should give more details so that we can try to help you.
Steven
Dead latest. Both Ubuntu and Debian Based. I'm working with device to device beginner sdb to sda. Both 256gb drives.
For context (dead Latest) : 202010127-groovy & 2.7.2-22. Both were tested. Same on both.
What were the steps you have done? What was the error message? Please take some photos then post them. It would be easier for us to understand what went wrong there.
Steven
I think I have the same problem. I only tested with the ubuntu version ( 202010127-groovy). And gave up after the third loop.
I want to migrate (clone) a SSD (960G) to another SSD (1024G). The origin has a proxmox system installed with several containers and VMs in use.
I used the "to RAM" boot option. Then selected "device-device", "beginners", and then "disk_to_local_disk". I selected the correct disks, and started the process.
The third partition (sda3, the big one) enters in the loop, 1.5 hours each. The previous 2 partitions (/boot, and /root I think) finish cloning fast and just once.
I have attached 5 images. They come from a video I took the second time it happened. The name of the file is the frame in the video, so they are numerically in order.
Any idea if this is really a bug? Do you need more info?
"202010127-groovy" -> Have you tried the latest Clonezilla live 2.7.1-22 or 20210127-groovy?
https://clonezilla.org/downloads.php
Is this issue also reproducible?
Steven
"202010127-groovy". That's misspelled. Sorry.
I tried with the latest available '20210127-groovy'. I have not tried with the debian version, but OP says xhe used both.
I think CZ is cloning sd3 for every VM in the proxmox system. Or for every LV, since every VM is a LV in a LVM thin pool. This is just a theory.
LVM thin provisioning? If so, well, Clonezilla does not support that due to an issue:
ref: https://sourceforge.net/p/clonezilla/discussion/Clonezilla_live/thread/e222fbb297/
Steven
Ohh I see. So proxmox is out of the question for now. At least in the default installation.
I hope it gets fixed. Thank you for your time.
It happened to me exactly the same problem, cloning a Proxmox installation. Eventually it succeeded, because I don't have many VMs. As far as I can tell it worked everything as expected. But how would I check?
Maybe you can give Clonezilla live >= 2.7.2-30 or 20210511-* a try. Some minor improvement about LVM.
Steven
Still not working even with the latest test builds.
I suggest you post your issue in a new thread.
Tell us the steps you have done. It would be easier for others to help you.