LVM2: Object sdd2 has an LVM2 PV label and header, but the recorded size of the object (963561984 sectors) does not match the actual size (321187545 sectors). Please indicate whether or not sdd2 is an LVM2 PV.
If your container includes an MD RAID region, it's possible that LVM2 has found the PV label on one of that region's child objects instead of on the MD region itself. If this is the case, then object sdd2 is most likely NOT one of the LVM2 PVs.
Choosing "no" here is the default, and is always safe, since no changes will be made to your configuration. Choosing "yes" will modify your configuration, and will cause problems if it's not the correct choice. The only time you would really need to choose "yes" here is if you are converting an existing container from using the LVM2 tools to using EVMS, and the container is NOT created from an MD RAID region. If you created and manage your containers only with EVMS, you should always be able to answer "no".
If you answer "no" and your volumes are correctly discovered and activated, you may disable this message in the future by editing the EVMS config file and setting the device_size_prompt option to "no" in the lvm2 section.evms_activate: Responding with default selection "No, it is not a PV.".
LVM2: Object sda2 has an LVM2 PV label and header, but the recorded size of the object (963561984 sectors) does not match the actual size (321187545 sectors). Please indicate whether or not sda2 is an LVM2 PV.
If your container includes an MD RAID region, it's possible that LVM2 has found the PV label on one of that region's child objects instead of on the MD region itself. If this is the case, then object sda2 is most likely NOT one of the LVM2 PVs.
Choosing "no" here is the default, and is always safe, since no changes will be made to your configuration. Choosing "yes" will modify your configuration, and will cause problems if it's not the correct choice. The only time you would really need to choose "yes" here is if you are converting an existing container from using the LVM2 tools to using EVMS, and the container is NOT created from an MD RAID region. If you created and manage your containers only with EVMS, you should always be able to answer "no".
If you answer "no" and your volumes are correctly discovered and activated, you may disable this message in the future by editing the EVMS config file and setting the device_size_prompt option to "no" in the lvm2 section.evms_activate: Responding with default selection "No, it is not a PV.".
Error returned from evms_commit_changes(): No such device