On 2 March 2014 22:29, Cyril Brulebois <[email protected]> wrote: > martin f krafft <[email protected]> (2014-02-27): >> Package: debian-installer >> Version: 20130613+deb7u1+b2 >> Severity: normal >> >> Despite >> >> d-i partman-auto/purge_lvm_from_device boolean true >> d-i partman-lvm/device_remove_lvm boolean true >> d-i partman-lvm/confirm boolean true >> d-i partman-lvm/confirm_nooverwrite boolean true >> >> d-i fails to install a machine when libvirt passes it a storage >> volume that has previously been used as PV by another host. >> >> What happens (in my case) is that partman creates a new GPT, but >> often that will be exactly the same as the one used by the previous >> host using the volume. Therefore, /dev/vda3 will be a valid LVM PV, >> meaning that LVM will find the previous VG. >> >> Now, depending on whether the hostname is (a) the same, or (b) >> different, d-i will fail to install claiming >> >> (a) a VG with the same name is already present; >> (b) the PV is already in use by another VG. > > Logs would be helpful.
Not necessary, as it's easy to reproduce and a known bug (i've tried and fixed couple symptoms but not all). Indeed just use an lvm-preseed, twice in a row, and delete partition table between the two runs. Furthermore, those that install Virtual Machines, with hard-drives provisioned by LVM volumes on the host, may find "shadow effects" where deleted & freshly created lvm-volume for the repeat install still has left-over guest lvm metadata from previous incarnations. wiping / zeroing out the drive before installation would be slow, but would fix this... -- Regards, Dimitri. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/CANBHLUiCt2LygtJy0KcyVr=zn8vh80nq7mfi+74ppaeppy6...@mail.gmail.com
