Create image of LVM partition and restore to non LVM partion
A partition and disk imaging/cloning program
Brought to you by:
steven_shiau
Menu
▾
▴
Hi,
I am having trouble cloning an LVM partion to a non LVM partion. Currently my process is to image just the LVM partion using dd, then attempt to restore the image to the non LVM partion. Right now I am getting the corrupt .. /tmp/ file errors as the new partion name does not match the old partion name and acts like the image is corrupt. I am getting it to upload now, using the dd expert option, but had to modify my partion table to match the old LVM drive settings. I am going to attempt again with a non LVM table, but figured I would ask.
Is there any way to do this? I have seen several ways of doing this with dd; but not a write up with clonezilla.
Thanks for any help. *edit, please forgive my typos in the header, it has been a long night
Last edit: Colin McGonagill 2017-10-15
It only seems to want to restore if the disk is setup with identical partitions. I cant seem to copy the LVM to its own partition and let it run as suggest here:
http://daniel-albuschat.blogspot.com/2008/02/converting-lvm-to-normal-partition.html
Last edit: Colin McGonagill 2017-10-15
Actually you can manually use "partclone.xx" (e.g., partclone.ext4) to do that. Just like what you have done with dd.
Run "partclone.ext4 --help" for more details.
Steven
Steven,
Any insight as to why it throws an error when you try to restore an image created from an LVM partition to a non LVM partition? I would assume partclone would only "see" the partition on the LVM as a normal partition, and then when restoring it would be able to just put it back there. One thing I seemed to see was because the image file saves the partition table the restore side of the program was running into hiccups, I saw it searching for partition p1,p2,p3, when it shouldnt have even been looking for that. When my drive that was being restored had just 1 partition it didnt work, when i copied the partition table so it was the same, it worked great, even though the restoration process was only restoring p3 to p3, not a whole disk to a whole disk. It seemed odd to me the tables being mis matched gave it an error.
I will try your method tonight and report back.