Can't restore the volume group after ghosting an hdd

I had a hard drive begin to go bad on me, so I ghosted it to another drive. lvm2 successfully picked up on the ghosted drive and didn't complain about it. I used pvmove to send the data off to other parts of the array. I removed the hdd I ghosted to from the array, wiped it, and readded it as a new drive.

Now I can't seem to put my array back together.
I'm worried about the output of the lvs command saying that the volume group is inconsistent. What exactly does that mean, and what do I do about it? I can still seem to mount everything ok and get to my data, but these errors are disconcerting. Is there a way to get everything back to "normal"?

pvs:
Found duplicate PV iCXUP4rdy2ZhoIJ4NWl1s3dr1au6QofX: using /dev/hdg1
not /dev/hdg
Found duplicate PV fFNJ9uKeNSMVQxwLH82lnI3J0hQYRKTh: using /dev/hdk1
not /dev/hdk
Warning: Volume Group vg0 is not consistent

  PV         VG   Fmt  Attr PSize   PFree
  /dev/hde4  vg0  lvm2 a-   179.75G      0
  /dev/hdg   vg0  lvm2 a-   172.55G  60.36G
  /dev/hdi   vg0  lvm2 a-   152.67G 152.67G
  /dev/hdk   vg0  lvm2 a-   233.76G      0

vgs:
Found duplicate PV iCXUP4rdy2ZhoIJ4NWl1s3dr1au6QofX: using /dev/hdg1
not /dev/hdg
Found duplicate PV fFNJ9uKeNSMVQxwLH82lnI3J0hQYRKTh: using /dev/hdk1
not /dev/hdk
VG #PV #LV #SN Attr VSize VFree
vg0 4 1 0 wz--n 738.73G 213.03G

lvs:
Found duplicate PV iCXUP4rdy2ZhoIJ4NWl1s3dr1au6QofX: using /dev/hdg1
not /dev/hdg
Found duplicate PV fFNJ9uKeNSMVQxwLH82lnI3J0hQYRKTh: using /dev/hdk1
not /dev/hdk
Volume group "vg0" inconsistent

  LV   VG   Attr   LSize   Origin Snap%  Move Copy%
  lv0  vg0  -wi--- 525.70G

Which of those devices is intended to hold the PV?

Did you run commands against hdg or hdg1?
(If it's partitioned you should always use hdg1, never hdg.)

Updating to a recent version of the lvm2 tools will help avoid that in future. Meanwhile it might be that you need to wipe the partition tables (the 1st 512 bytes of hdg and hdk - back it up first).

Alasdair

[email protected]

Oh confound it!

I cleaned off a bunch of junk on my array to reduce total usage to two drives. I pvmoved the other two drives and reduced the logical volume. Then I reduced the volume group to eliminate those two drives. I went to resize the reiserfs, but here's what I get:

[root@fileserver archive]# resize_reiserfs /dev/vg0/lv0 resize_reiserfs 3.6.19 (2003 www.namesys.com)

bread: Cannot read the block (2): (Invalid argument).
reiserfs_open: bread failed reading block 2
bread: Cannot read the block (16): (Invalid argument).
reiserfs_open: bread failed reading block 16

reiserfs_open: the reiserfs superblock cannot be found on /dev/vg0/lv0.

but

  PV         VG   Fmt  Attr PSize   PFree
  /dev/hde4  vg0  lvm2 a-   179.75G      0
  /dev/hdg1       lvm2 --   172.55G 172.55G
  /dev/hdi        lvm2 --   152.67G 152.67G
  /dev/hdk1  vg0  lvm2 a-   233.76G  37.81G

and again:

VG #PV #LV #SN Attr VSize VFree
vg0 2 1 0 wz--n 413.51G 37.81G

and finally:

  LV   VG   Attr   LSize   Origin Snap%  Move Copy%
  lv0  vg0  -wi-s- 375.70G

What caused this to die? Just after I got DVD-R's too! :(