On Wed, Oct 12, 2011 at 11:25 AM, Toby Corkindale < toby.corkindale@strategicdata.com.au> wrote:
I don't think that is the right conclusion.
What is the output of running: sudo fdisk -l /dev/sdg
Disk /dev/sdg: 2000 GB, 2000396321280 bytes 255 heads, 63 sectors/track, 243201 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdg1 1 60800 488375968 8e Linux LVM Warning: Partition 1 does not end on cylinder boundary. /dev/sdg2 60800 243202 1465144065 fd Lnx RAID auto Warning: Partition 2 does not end on cylinder boundary.
sudo pvdisplay -m
root@ubuntu:~# pvdisplay -m "/dev/sdg1" is a new physical volume of "465.74 GiB" --- NEW Physical volume --- PV Name /dev/sdg1 VG Name PV Size 465.74 GiB Allocatable NO PE Size 0 Total PE 0 Free PE 0 Allocated PE 0 PV UUID okjC2x-EKtY-8Tf7-gkqN-Q7Oj-Kixj-8aTZ2T
sudo vgdisplay
root@ubuntu:~# vgdisplay No volume groups found I've been getting some help in #lvm on freenode. I've backed up my lvm header on /dev/sdg1, and looked at it, and found old(er) configurations still present. http://pastebin.com/ifJg309W
From this, I was able to vgcfgrestore -f /bakupcfg system and see my volumes again. However, they were bunk ... I'm guessing the configuration I restored didn't accurately describe the layout, so instead of filesystems, it just found "data" according to file -s.
In the meantime, have restored the original header. More ideas are always welcome. cheers, / Brett