On Tue, Oct 28, 2014 at 11:45 AM, Robert Nichols <rnicholsNOSPAM at comcast.net > wrote: > Yes, that would have helped a lot. I can see in file > /etc/lvm/backup/vg_devserver that the lv_root LV has been extended by a > mere 32 Megabytes (yes, Mega) on the missing physical volume. Do you > still have the additional disk? The best thing to do would be to put > it back, make a partition on it, and then re-create the missing PV. > I'll assume that the new partition is /dev/sdb1. Adjust all references > in the following if it si something else. > I don't think I have that disk alive, take a look to this image http://imgur.com/jMuhM03 this is how my disk looks like > > Make a copy of /etc/lvm/backup/vg_devserver on vg_devserver.bak, and > then run > > pvcreate -v --restorefile vg_devserver.bak \ > --uuid "vSbuSJ-o1Kh-N3ur-JYkM-Ktr4-WEO2-JWe2wS" \ > /dev/sdb1 > > This is the result of the command above: # pvcreate -v --restorefile /etc/lvm/backup/vg_devserver.bak --uuid "vSbuSJ-o1Kh-N3ur-JYkM-Ktr4-WEO2-JWe2wS" /dev/sdb1 /dev/root: read failed after 0 of 4096 at 27522957312: Input/output error /dev/root: read failed after 0 of 4096 at 27523014656: Input/output error Wiping cache of LVM-capable devices /dev/root: read failed after 0 of 4096 at 27522957312: Input/output error /dev/root: read failed after 0 of 4096 at 27523014656: Input/output error Couldn't find device with uuid vSbuSJ-o1Kh-N3ur-JYkM-Ktr4-WEO2-JWe2wS. Wiping cache of LVM-capable devices /dev/root: read failed after 0 of 4096 at 27522957312: Input/output error /dev/root: read failed after 0 of 4096 at 27523014656: Input/output error Device /dev/sdb1 not found (or ignored by filtering). > (I've broken that up into multiple lines to avoid word wrap problems.) > > You should then be able to run pvs and lvs successfully. To properly > remove this PV from the LVM structure, run > > lvreduce --extents -8 /dev/vg_devserver/lv_root > vgreduce vg_devserver /dev/sdb1 > pvremove /dev/sdb1 > > That lvreduce will get rid of the 32MB that were allocated on that > added PV. You will probably get a warning about possible data loss > and will have to confirm. The vgreduce and pvremove should then > proceed without any issues. >