No subject


Wed Sep 13 06:36:04 UTC 2006


you were getting at the beginning -- errors about not being able to find the
device with a given uuid, etc.

When I try to reassign the UUID, I get errors about improper UUID format.

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.

Thanks,
-Austin

------=_Part_80931_29539372.1158203175226
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<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.&nbsp;&nbsp;I was, at last, able to solve this problem.&nbsp;&nbsp;I was right all along...the data was there.&nbsp;&nbsp;So when I started experimenting with the archive files associated with LVM, I stumbled on success.&nbsp;&nbsp;Someone suggested &quot;vgcfgrestore&quot; might work; however, I had to use trial &amp; error with the -t (test) parameter in order to figure this out.&nbsp;&nbsp;By that I mean reading the LVM HowTo and various man pages did not clarify much for me.&nbsp;&nbsp;So here are the steps that I took:
<br>--------------------------------------------------------<br>[root at mythserver lvm]# vgcfgrestore -tf /etc/lvm/archive/VolGroup00_00000.vg<br>&nbsp;&nbsp;Test mode: Metadata will NOT be updated.<br>&nbsp;&nbsp;Please specify a *single* volume group to restore.
<br>[root at mythserver lvm]# vgcfgrestore -tf /etc/lvm/archive/VolGroup00_00000.vg Vol<br>Group00<br>&nbsp;&nbsp;Test mode: Metadata will NOT be updated.<br>&nbsp;&nbsp;Restored volume group VolGroup00<br>[root at mythserver lvm]# vgcfgrestore -tvf /etc/lvm/archive/VolGroup00_00000.vg Vo
<br>lGroup00<br>&nbsp;&nbsp;Test mode: Metadata will NOT be updated.<br>&nbsp;&nbsp;Restored volume group VolGroup00<br>&nbsp;&nbsp;&nbsp;&nbsp;Test mode: Wiping internal cache<br>&nbsp;&nbsp;&nbsp;&nbsp;Wiping internal VG cache<br>[root at mythserver lvm]# vgcfgrestore -tvvf /etc/lvm/archive/VolGroup00_00000.vg V
<br>olGroup00<br>&nbsp;&nbsp;Test mode: Metadata will NOT be updated.<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Setting global/locking_type to&nbsp;&nbsp;1<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Setting global/locking_dir to /var/lock/lvm<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;File-based locking enabled.<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Locking /var/lock/lvm/P_orphans WB
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Locking /var/lock/lvm/V_VolGroup00 W<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;/dev/hda1: No label detected<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;/dev/hda2: No label detected<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;/dev/hda3: No label detected<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;/dev/hda5: lvm2 label detected<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;/dev/hdb: lvm2 label detected
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;/dev/hda5: lvm2 label detected<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;/dev/hdb: lvm2 label detected<br>&nbsp;&nbsp;Restored volume group VolGroup00<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Unlocking /var/lock/lvm/V_VolGroup00<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Unlocking /var/lock/lvm/P_orphans<br>&nbsp;&nbsp;&nbsp;&nbsp;Test mode: Wiping internal&nbsp;&nbsp;cache
<br>&nbsp;&nbsp;&nbsp;&nbsp;Wiping internal VG cache<br>[root at mythserver lvm]# vgcfgrestore -vvf /etc/lvm/archive/VolGroup00_00000.vg Vo<br>lGroup00<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Setting global/locking_type to 1<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Setting global/locking_dir to /var/lock/lvm
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;File-based locking enabled.<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Locking /var/lock/lvm/P_orphans WB<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Locking /var/lock/lvm/V_VolGroup00 W<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;/dev/hda1: No label detected<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;/dev/hda2: No label detected<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;/dev/hda3: No label detected
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;/dev/hda5: lvm2 label detected<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;/dev/hdb: lvm2 label detected<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;/dev/hda5: lvm2 label detected<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;/dev/hdb: lvm2 label detected<br>&nbsp;&nbsp;Restored volume group&nbsp;&nbsp;VolGroup00<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Unlocking /var/lock/lvm/V_VolGroup00
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Unlocking /var/lock/lvm/P_orphans<br>[root at mythserver lvm]# lvscan<br>&nbsp;&nbsp;inactive&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;'/dev/VolGroup00/LogVol00' [364.21 GB] inherit<br>[root at mythserver lvm]# lvchange -tv -ay /dev/VolGroup00/LogVol00<br>&nbsp;&nbsp;Test mode: Metadata will NOT be updated.
<br>&nbsp;&nbsp;&nbsp;&nbsp;Using logical volume(s) on command line<br>&nbsp;&nbsp;&nbsp;&nbsp;Activating logical volume &quot;LogVol00&quot;<br>&nbsp;&nbsp;&nbsp;&nbsp;Found volume group &quot;VolGroup00&quot;<br>&nbsp;&nbsp;&nbsp;&nbsp;Test mode: Wiping internal cache<br>&nbsp;&nbsp;&nbsp;&nbsp;Wiping internal VG cache
<br>[root at mythserver lvm]# lvchange -v -ay /dev/VolGroup00/LogVol00<br>&nbsp;&nbsp;&nbsp;&nbsp;Using logical volume(s) on command line<br>&nbsp;&nbsp;&nbsp;&nbsp;Activating logical volume &quot;LogVol00&quot;<br>&nbsp;&nbsp;&nbsp;&nbsp;Found volume group &quot;VolGroup00&quot;<br>
&nbsp;&nbsp;&nbsp;&nbsp;Loading&nbsp;&nbsp;VolGroup00-LogVol00<br>[root at mythserver lvm]# mount -a<br>------------------------------------------------------------------------<br>That did it!&nbsp;&nbsp;We were able to copy our data off the volume and recover the whole system.&nbsp;&nbsp;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>

------=_Part_80931_29539372.1158203175226--


More information about the mythtv-users mailing list