Jan Schunk

Currently we have only 6 machines left to be migrated via clonezilla (the reason that they currently still running on the old system is not clonezilla related), all other machines (more than 100) are already clone d and running fine. I will take a look at lite server when we may need it. "assign the destination device" via command does not help: the issue with wrong device name is only on the sub task restoring LVM metadata backup. A LVM metadata backup contain some section like this: physical_volumes...

I used clonezilla-live-2.6.7-28-amd64. Sorry that I posted two issues in one thread. Issue one: device name (on Debian/Ubuntu/CentOS VMs with LVM) Issue two: different port names used (on CentOS VM with LVM)

I tried the CentOS machine again and now I found the bug: Clonezilla live on remote-source starts netcat (nc) on this ports: /dev/sda1: 9015 /dev/centos/swap: (skipped) /dev/centos/root: 9021 Clonezilla live on remote-dest expects and tries netcat (nc) on this ports: /dev/sda1: 9015 /dev/centos/swap: 9021 /dev/centos/root: 9027 (connection refused) PS: /dev/sda1 (boot) and /dev/centos/root are both XFS Because we only have one machine like this, I used this workaround: Wait for /dev/centos/root to...

I tried the CentOS machine again and now I found the bug: Clonezilla live on remote-source starts netcat (nc) on this ports: /dev/sda1: 9015 /dev/centos/swap: (skipped) /dev/centos/root: 9021 Clonezilla live on remote-dest expects and tries netcat (nc) on this ports: /dev/sda1: 9015 /dev/centos/swap: 9021 /dev/centos/root: 9027 (connection refused) PS: /dev/sda1 (boot) and /dev/centos/root are both XFS Because we only have one machine like this, I used this workaround: Wait for /dev/centos/root to...

I tried the CentOS machine again and now I found the bug: Clonezilla live on remote-source starts netcat (nc) on this ports: /dev/sda1: 9015 /dev/centos/swap: (skipped) /dev/centos/root: 9021 Clonezilla live on remote-dest expects and tries netcat (nc) on this ports: /dev/sda1: 9015 /dev/centos/swap: 9021 /dev/centos/root: 9027 (connection refused) PS: /dev/sda1 (boot) and /dev/centos/root are both XFS Because we only have one machine like this, I used this workaround: Wait for /dev/centos/root to...

There a still machines with LVM which could not be cloned. Example is a CentOS VM with two partitions: sda1 boot sda2 lvm Inside the LVM is one vg with two lvs: /dev/centos/swap /dev/centos/root Clonezilla live restores the metadata, does partclone of /dev/centos/swap with dd mode (you see on the screen, the data really transfers) followed by two lines: Cloned successfully. Failed to clone remote image /dev/centos/swap next it tries partclone of /dev/centos/root which does not start (read image_hdr...

There a still machines with LVM which could not be cloned. Example is a CentOS VM with two partitions: sda1 boot sda2 lvm Inside the LVM is one vg with two lvs: /dev/centos/swap /dev/centos/root Clonezilla live restores the metadata, does partclone of /dev/centos/swap with dd mode (you see on the screen, the data really transfers) followed by two lines: Cloned successfully. Failed to clone remote image /dev/centos/swap next it tries partclone of /dev/centos/root which does not start (read image_hdr...

There a still machines with LVM which could not be cloned. Example is a CentOS VM with two partitions: sda1 boot sda2 lvm Inside the LVM is one vg with two lvs: /dev/centos/swap /dev/centos/root Clonezilla ive restores the metadata, does partclone of /dev/centos/swap with dd mode (you see on the screen, the data really transfers) followed by two lines: Cloned successfully. Failed to clone remote image /dev/centos/swap next it tries partclone of /dev/centos/root which does not start (read image_hdr...