<br><br><b><i>Austin Roberts <mythtv@ausiv.com></i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> <div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Greetings to all:<br>This followup is for the benefit of those who may run into a similar problem in the future. I was, at last, able to solve this problem. I was right all along...the data was there. So when I started experimenting with the archive files associated with LVM, I stumbled on success. Someone suggested "vgcfgrestore" might work; however, I had to use trial & error with the -t (test) parameter in order to figure this out. By that I mean reading the LVM HowTo and various man pages did not clarify much for me. So here are the steps that I took:
<br>--------------------------------------------------------<br>[root@mythserver lvm]# vgcfgrestore -tf /etc/lvm/archive/VolGroup00_00000.vg<br> Test mode: Metadata will NOT be updated.<br> Please specify a *single* volume group to restore. <br>[root@mythserver lvm]# vgcfgrestore -tf /etc/lvm/archive/VolGroup00_00000.vg Vol<br>Group00<br> Test mode: Metadata will NOT be updated.<br> Restored volume group VolGroup00<br>[root@mythserver lvm]# vgcfgrestore -tvf /etc/lvm/archive/VolGroup00_00000.vg Vo <br>lGroup00<br> Test mode: Metadata will NOT be updated.<br> Restored volume group VolGroup00<br> Test mode: Wiping internal cache<br> Wiping internal VG cache<br>[root@mythserver lvm]# vgcfgrestore -tvvf /etc/lvm/archive/VolGroup00_00000.vg V <br>olGroup00<br> Test mode: Metadata will NOT be updated.<br> Setting
global/locking_type to 1<br> Setting global/locking_dir to /var/lock/lvm<br> File-based locking enabled.<br> Locking /var/lock/lvm/P_orphans WB <br> Locking /var/lock/lvm/V_VolGroup00 W<br> /dev/hda1: No label detected<br> /dev/hda2: No label detected<br> /dev/hda3: No label detected<br> /dev/hda5: lvm2 label detected<br> /dev/hdb: lvm2 label detected <br> /dev/hda5: lvm2 label detected<br> /dev/hdb: lvm2 label detected<br> Restored volume group VolGroup00<br> Unlocking
/var/lock/lvm/V_VolGroup00<br> Unlocking /var/lock/lvm/P_orphans<br> Test mode: Wiping internal cache <br> Wiping internal VG cache<br>[root@mythserver lvm]# vgcfgrestore -vvf /etc/lvm/archive/VolGroup00_00000.vg Vo<br>lGroup00<br> Setting global/locking_type to 1<br> Setting global/locking_dir to /var/lock/lvm <br> File-based locking enabled.<br> Locking /var/lock/lvm/P_orphans WB<br> Locking /var/lock/lvm/V_VolGroup00 W<br> /dev/hda1: No label detected<br> /dev/hda2: No label detected<br> /dev/hda3: No label detected <br> /dev/hda5: lvm2 label
detected<br> /dev/hdb: lvm2 label detected<br> /dev/hda5: lvm2 label detected<br> /dev/hdb: lvm2 label detected<br> Restored volume group VolGroup00<br> Unlocking /var/lock/lvm/V_VolGroup00 <br> Unlocking /var/lock/lvm/P_orphans<br>[root@mythserver lvm]# lvscan<br> inactive '/dev/VolGroup00/LogVol00' [364.21 GB] inherit<br>[root@mythserver lvm]# lvchange -tv -ay /dev/VolGroup00/LogVol00<br> Test mode: Metadata will NOT be updated. <br> Using logical volume(s) on command line<br> Activating logical volume "LogVol00"<br> Found volume group "VolGroup00"<br> Test mode: Wiping internal
cache<br> Wiping internal VG cache <br>[root@mythserver lvm]# lvchange -v -ay /dev/VolGroup00/LogVol00<br> Using logical volume(s) on command line<br> Activating logical volume "LogVol00"<br> Found volume group "VolGroup00"<br> Loading VolGroup00-LogVol00<br>[root@mythserver lvm]# mount -a<br>------------------------------------------------------------------------<br>That did it! We were able to copy our data off the volume and recover the whole system. I hope this helps someone else down the road. <br><br>-Tom-<br></blockquote></div><br>Tom:<br>Today I did something silly that puts me in a perdicament similar to yours. From what I've seen the results I am getting are very similar to the results you were getting at the beginning -- errors about not being able to find the device with a given uuid, etc. <br><br>When I try to
reassign the UUID, I get errors about improper UUID format.<br><br>What did you do in order to reassign the UUID to the faulty drive? I've not been able to find that in any of your explanations.<br><br> Thanks,<br>-Austin<br><br></blockquote>Austin,<br><br>I'm sorry I didn't respond sooner...I had not seen your post until today. Unfortunately for you, I didn't go the route of reassigning the UUID to the faulty drive. When I removed it, I tried to find an answer or someone who could help me with that. Even the LVM mailing list was not helpful on that issue (it's extremely low volume compared to this list). Ultimately, I followed someone's suggestion of issuing the command "<font color="black" face="Verdana,Arial,Helvetica" size="2"><font color="black" face="Verdana,Arial,Helvetica" size="2">vgreduce --removemissing VolGroup00" which allowed me to move on without the previously added, faulty drive.<br><br>Still, it seems like you should have been able
to use vgcfgrestore to get the metadata back, unless you don't have the backup and archive files available.<br><br>Also, there's some information about restoring UUIDs here:<br>http://tldp.org/HOWTO/LVM-HOWTO/recovermetadata.html<br><br>Hopefully you were able to recover the volume by now...<br><br>-Tom-<br><br></font></font><p> 
<hr size=1>Get your own <a href=" http://us.rd.yahoo.com/evt=43290/*http://smallbusiness.yahoo.com/domains"
>web address for just $1.99/1st yr</a>. We'll help. <a href="http://us.rd.yahoo.com/evt=41244/*http://smallbusiness.yahoo.com/"
>Yahoo! Small Business</a>.