it must be june, as my volume group is inconsistent again. argh! okay i had a hard drive fail a few months back. by some wierd circumstance it suddenly started working again. i moved all my data off of it, but left it in the volume group as unused available space (just in case... after all, it was working again). Yesterday i got some more ram and did an upgrade. while init 0 was shutting down the box, it complained that /dev/hdg1, /dev/hdg2, /dev/hdg3, and /dev/hdg4 couldnt be shut down by LVM. no problem, thats the hd that was having issues, there wasnt any data on it anyway. i installed my ram and rebooted my box.




Code:
* Setting up the Logical Volume Manager ... 
 WARNING: Volume Group vg is not consistent 
 Volume group "vg" inconsistent 
 WARNING: Inconsistent metadata found for VG vg - updating to use version 163 
 Volume group "vg" inconsistent 
 WARNING: Inconsistent metadata found for VG vg - updating to use version 164 
 Volume group "vg" inconsistent 
 WARNING: Inconsistent metadata found for VG vg - updating to use version 165 
 Volume group vg metadata is inconsistent 
 Volume group for uuid not found: YcTvYUVDAzucoZnkil7k1H12mxJx2ggJ2xs5TfPa6njKKeOa24E8a2OUV06CEVZj 
 Volume group vg metadata is inconsistent 
 Volume group for uuid not found: YcTvYUVDAzucoZnkil7k1H12mxJx2ggJOvQM1qYhwMlk11jz3AzTRvOitLrE8SrS 
 Volume group vg metadata is inconsistent 
 Volume group for uuid not found: YcTvYUVDAzucoZnkil7k1H12mxJx2ggJ87G51VgLs67gTinB4etjaJK3d8LRh5fL 
 Volume group vg metadata is inconsistent 
 Volume group for uuid not found: YcTvYUVDAzucoZnkil7k1H12mxJx2ggJfG3tIyaB3t2qdH7DWg3EUFZgV3l6PTA7 
 Volume group vg metadata is inconsistent 
 Volume group for uuid not found: YcTvYUVDAzucoZnkil7k1H12mxJx2ggJAsjezo9ZOS61AXBsLB6ZDJAcvHZILgu7 
  Volume group vg metadata is inconsistent 
 Volume group for uuid not found: YcTvYUVDAzucoZnkil7k1H12mxJx2ggJJoy0mKcoRIqxkLi2asX5XzcmqpTfK3eP 
 Volume group vg metadata is inconsistent 
 Volume group for uuid not found: YcTvYUVDAzucoZnkil7k1H12mxJx2ggJjy2lm8Psysw1VWOhokchQzQ9f34Lwi7u 
* Setting up dm-crypt [ ... ] 


* Mounting local filesystems ...      [ ok ] 
mount: special device /dev/vg/usr does not exist 
mount: special device /dev/vg/home does not exist 
mount: special device /dev/vg/opt does not exist 
mount: special device /dev/vg/var does not exist 
mount: special device /dev/vg/tmp does not exist 
mount: special device /dev/vg/e does not exist 
* Some local filesystem failed to mount    [ !! ]


grr.

okay so try this:
Code:
vgchange -ay --partial 
Partial mode. Incomplete volume groups will be activated read-only. 
Volume group "vg" inconsistent 
WARNING: Inconsistent metadata found for VG vg - updating to use version 168 
Volume group vg metadata is inconsistent 
Volume group vg metadata is inconsistent 
Volume group vg metadata is inconsistent 
Volume group vg metadata is inconsistent 
Volume group vg metadata is inconsistent 
Volume group vg metadata is inconsistent 
Volume group vg metadata is inconsistent 
7 logical volume(s) in volume group "vg" now active


thats a good sign!

Code:
vgdisplay 
WARNING: Volume group "vg" inconsistent 
--- Volume group --- 
VG Name                        vg 
System ID 
Format                            lvm2 
Metadata Areas               39 
Metadata Sequence No     169 
VG Access                      read/write 
VG Status                       resizable 
MAX LV                          255 
Cur LV                           7 
Open LV                         0 
Max PV                          255 
Cur PV                          35 
Act PV                           35 
VG Size                         1.70 TB 
PE Size                         4.00 MB 
Total PE                        445306 
Alloc PE / Size               445184 / 1.70 TB 
Free PE / Size                122 / 488.00 MB 
VG UUID                       YcTvYU-VDAz-ucoZ-nkil-7k1H-12mx-Jx2ggJ


so just to test, i mounted one of the drives, ran a du... it ran fine, wrote to the drive... everything works great. That says to me, that using --partial mounts the entire vg! the vg metadata is correct!!

i tried to use vgreduce --removemissing... and nothing happens

Code:
vgreduce --removemissing vg 
 WARNING: Inconsistent metadata found for VG vg - updating up use version 169 
 Volume group "vg" is already consistent 

vgscan 
 Reading all physical volumes. This may take a while... 
 Volume group "vg" inconsistent 
 WARNING: Invonsistent metadata found for VG vg - updating to use version 170 
 Found volume group "vg" using metadata type lvm2 

vgchange -a n 
 Volume group "vg" inconsistent 
 WARNING: Inconsistent metadata found for VG vg - updating to use version 171 
 Volume group vg metadata is inconsistent 
 Volume group for uuid not found: YcTvYUVDAzucoZnkil7k1H12mxJx2ggJ2xs5TfPa6njKKeOa24E8a2OUV06CEVZj 
 Volume group vg metadata is inconsistent 
 Volume group for uuid not found: YcTvYUVDAzucoZnkil7k1H12mxJx2ggJOvQM1qYhwMlk11jz3AzTRvOitLrE8SrS 
 Volume group vg metadata is inconsistent 
 Volume group for uuid not found: YcTvYUVDAzucoZnkil7k1H12mxJx2ggJ87G51VgLs67gTinB4etjaJK3d8LRh5fL 
 Volume group vg metadata is inconsistent 
 Volume group for uuid not found: YcTvYUVDAzucoZnkil7k1H12mxJx2ggJfG3tIyaB3t2qdH7DWg3EUFZgV3l6PTA7 
 Volume group vg metadata is inconsistent 
 Volume group for uuid not found: YcTvYUVDAzucoZnkil7k1H12mxJx2ggJAsjezo9ZOS61AXBsLB6ZDJAcvHZILgu7 
  Volume group vg metadata is inconsistent 
 Volume group for uuid not found: YcTvYUVDAzucoZnkil7k1H12mxJx2ggJJoy0mKcoRIqxkLi2asX5XzcmqpTfK3eP 
 Volume group vg metadata is inconsistent 
 Volume group for uuid not found: YcTvYUVDAzucoZnkil7k1H12mxJx2ggJjy2lm8Psysw1VWOhokchQzQ9f34Lwi7u 
   7 logical volume(s) in volume group "vg" now active


odd... i cant deactivate the volume group.


it could also be noteworthy that cfdisk /dev/hdg (the problem disk) shows the partitions, but /dev/hdg1, 2, 3, and 4 dont seem to show up in pvdisplay. (which is fine, but they USED to be there)


okay, so those uuid's it cannot find are a concatination of the vg's uuid (YcTvYU-VDAz-ucoZ-nkil-7k1H-12mx-Jx2ggJ) and the uuids for each of my 7 lvs.

i guess none of this is REALLY a problem except that i cant activate lvm on boot because of it.

can anybody make a suggestion as to how i can fix any of this??

please! thanks!

also... if you dont know the answer but have a good forum for lvm questions you can direct me to, it would be appreciated!