Hello everybody out there using LVM,
To have an immediate backup disk to replace my main Ubuntu 18.04 hard drive (which uses LVM), I cloned the main hard drive with dd.
This resulted in a clone also having the same LV and PV names.
To synchronize changes done on my main hard drive to the backup, I would need to mount the backup.
I searched the web and found that this can be done with vgimportclone when having the same LV and PV names (UUIDs).
Unfortunately, the following command still fails:
user@computer:~$ sudo vgimportclone -n test /dev/sda2
WARNING: PV 3qlGx5-L1xH-pV0q-6jXT-xLQ1-m2Na-8pTE4Z on /dev/sda2 was already found on /dev/nvme1n1p2.
WARNING: PV TmBs5X-fRO8-toZH-6bFA-GZtI-lNR5-VxpZIL on /dev/sda3 was already found on /dev/nvme1n1p3.
WARNING: PV 3qlGx5-L1xH-pV0q-6jXT-xLQ1-m2Na-8pTE4Z prefers device /dev/nvme1n1p2 because device is used by LV.
WARNING: PV TmBs5X-fRO8-toZH-6bFA-GZtI-lNR5-VxpZIL prefers device /dev/nvme1n1p3 because device is used by LV.
Couldn't find device with uuid TmBs5X-fRO8-toZH-6bFA-GZtI-lNR5-VxpZIL.
Cannot change VG ubuntu-vg while PVs are missing.
Consider vgreduce --removemissing.
Cannot process volume group ubuntu-vg
WARNING: PV 3qlGx5-L1xH-pV0q-6jXT-xLQ1-m2Na-8pTE4Z on /dev/nvme1n1p2 was already found on /dev/sda2.
WARNING: Disabling lvmetad cache which does not support duplicate PVs.
WARNING: PV TmBs5X-fRO8-toZH-6bFA-GZtI-lNR5-VxpZIL on /dev/sda3 was already found on /dev/nvme1n1p3.
My expectation would have been that the LV on the cloned disk gets mounted with the name test.
Which additional diagnostics could I run to find out why the command does not work as expected?
