use all disk to pv and create lvm clone faild help me!

[yeyudragon]

hi~
I want clone virturemachine to another plant. my vm's vda is crete a partion and create lvm ,so this disk (vda) can clone. but my vm's vdb is use all disk to pv and create lvm lisk this

pvcreate /dev/vdb
vgcreate datavg /dev/vdb
lvcreate -l +100%FREE -n datalv datavg

so when i clone this disk (vdb) it's faild clonezilla say cat not found any partion on this disk. pls tell me how can i do it? I have so manly vms to clone .

[stevenshiau]

Is that possible you can share the virtual machine? We'd like to reproduce this issue here.
Thanks.

[yeyudragon]

You can try this: Create a Linux virtual machine using any virtualization software, then add a disk and create an LVM in raw device mode. Use the following commands to create it:
"
pvcreate /dev/sdb
vgcreate /dev/sdb datavg
lvcreate -l +100%FREE /dev/datavg -n datalv
mkfs.ext4 /dev/datavg/datalv
mkdir /data
mount /dev/datavg/datalv /data
echo "any text work" > /data/test.txt
"
Then use "clonezilla" to migrate this virtual machine. This will reproduce the problem; it will keep prompting that the disk partition for 'sdb' cannot be found, and the migration will fail.

[stevenshiau]

OK, I finally have some time to try this. Before doing that, just want to make sure:

1. Which version of Clonezilla live did you use?
2. Did you do that by disk cloning or image restoring?

[yeyudragon]

QA

1. I've used multiple versions: older, latest stable, and test version

2. I've tried all the modes in the program: disk-to-disk, disk-to-file, and disk-to-SMB，basically all of them. I've even tried the advanced options after selecting a mode.

Finally, Happy New Year!

[stevenshiau]

Maybe you can use the latest testing one, i.e., Clonezilla live 3.3.1-30. Then run it, and share the log file /var/log/clonezilla/clonezilla.log?

[yeyudragon]

OK,I Try it pls wait

[yeyudragon]

err：

log：

[yeyudragon]

about my os part and raw disk

[stevenshiau]

log-pv.txt
lvm-img-dir.txt

For LVM, since same names of VG and LV can not co-exist on the same machine, you can only use image way to deal with it.
The above two files were created by testing Clonezilla live 3.3.1-30. The process to save it as an image is shown in log-pv.txt. You can see the /dev/sdc is for PV. I used what you have mentioned to create that:
`pvcreate /dev/sdc

vgcreate datavg /dev/sdc

lvcreate -l +100%FREE /dev/datavg -n datalv

mkfs.ext4 /dev/datavg/datalv

mkdir /data

mount /dev/datavg/datalv /data

echo "any text work" > /data/test.txt
`
The image was saved successfully, and the file lvm-img-dir.txt shows the image dir.

[yeyudragon]

I tried saving it locally, and it worked. However, this doesn't meet my actual needs. In reality, the raw device disk exceeds 2TB. Saving it locally would consume even more disk space, and network disk migration would take even longer. I think the best practice would be to directly migrate disk from machine A to machine B.

[yeyudragon]

The practical application scenario involves migrating production servers to a virtualized environment. Server downtime is permissible, so "Clonezilla" is used for cold migration, and many machines have been successfully migrated. In actual production environments, raw devices range in size from 2-8TB.

Using non-raw device mode to partition and then create an LVM allows for network cold migration via a "source-destination" approach. I have also successfully migrated many machines in actual production environments using this method, thanks to the powerful features of "Clonezilla," for which I am very grateful!

However, using the raw device LVM method for network cold migration via a "source-destination" approach results in the aforementioned errors. I cannot use a separate disk larger than 8TB to store the image just to migrate 8TB of data; it's also impractical in a real-world environment.

Therefore, I believe that if "Clonezilla" could solve the raw device migration problem via a "source-destination" approach, it would perfectly resolve the current issues. Or do you have any other better suggestions? Please advise.

[stevenshiau]

So you meant you want to do the cloning via network? i.e., the "remote-source" and "remote-dest" here:
https://clonezilla.org//clonezilla-live/doc/01_Save_disk_image/images/ocs-06-dev-img.png
If so, I would suggest you use Clonezilla lite server at the moment:
https://clonezilla.org///fine-print-live-doc.php?path=clonezilla-live/doc/12_lite_server_BT_from_dev
It actually covers the mode you want, and you can choose to use multicast/BT mechanism to do massive deployment. Of course, it includes the deployment for one to one.

[yeyudragon]

I tried the "lite_server_BT_from_dev" method, but it didn't work no matter what. My sdb is a raw device. After selecting sdb, the program runs, and then it prompts: "Choose the source partition(s) to save..." The list then displays the partition information of sda. If I don't make a selection, the program exits. Whether I select one partition or all for the next step, an error occurs and the program cannot proceed. Is it possible that it hasn't been adapted for raw devices?

[stevenshiau]

OK, the BT mode has an issue for this scenario. We will fix it in the next testing release.
ATM, please use multicast/broadcast mode.