The easiest way to move an vg to a new device is partitioning the new device, create a pv on the correct device, and then add that device to the vg and then do a pvmove to move the data to the new device. Once done you remove the device from the vg. cloning the boot can be done with dd, but if you do that it is best to only do up to were the 2nd partition starts and deal with the 2nd partition with the above lvm commands. On Mon, Dec 2, 2019 at 12:00 PM Patrick O'Callaghan <pocallaghan@xxxxxxxxx> wrote: > > On Mon, 2019-12-02 at 11:19 -0600, Roger Heflin wrote: > > > > Doing just about anything is going to be really dangerous and tricky > > given the device has duplicate uuids at the LV and PV level. There > > are ways to fix it, but most of those ways will either be exactly > > right, exactly wrong and you no longer have any data. > > Very scary. This is exactly why I don't want to use LVM. I don't > understand it. > > > I don't think fdisk will prevent you from removing the partitions, but > > you will need a reboot or manually delete the live partitions mappings > > to get them to disappear from the OS. > > I'm considering either fdisk or a 'dd if=/dev/zero ..." on the > offending partition, followed by a format with gparted. > > poc > _______________________________________________ > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx