<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>Message</TITLE>
<META content="MSHTML 6.00.2800.1400" name=GENERATOR></HEAD>
<BODY style="BACKGROUND-COLOR: #ffffff" bgColor=#ffffff background="">
<DIV><SPAN class=455511409-06072004><FONT face=Arial color=#0000ff
size=2>Additionally, pvscan reports the following:</FONT></SPAN></DIV>
<DIV><SPAN class=455511409-06072004><FONT face=Arial color=#0000ff size=2>pvscan
-- reading all physical volumes (this may take a while...)<BR>pvscan -- inactive
PV "/dev/hdg1" is associated to unknown VG "u00_vg" (run vgscan)<BR>pvscan
-- inactive PV "/dev/hdh1" is associated to unknown VG "u00_vg" (run
vgscan)<BR>pvscan -- inactive PV "/dev/hde1" is associated to unknown VG
"u00_vg" (run vgscan)<BR>pvscan -- total: 3 [204.96 GB] / in use: 3 [204.96 GB]
/ in no VG: 0 [0]<BR></FONT></SPAN></DIV>
<DIV><SPAN class=455511409-06072004><FONT face=Arial color=#0000ff size=2>What
must I do to re-associate the pv into the vg?</DIV></FONT></SPAN>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT
face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> Erik Ch.
Ohrnberger [mailto:Erik@EchoHome.org] <B>On Behalf Of
</B>lvm@echohome.org<BR><B>Sent:</B> Monday, July 05, 2004 8:56
PM<BR><B>To:</B> 'linux-lvm@redhat.com'<BR><B>Subject:</B> First corrupt
partician tables, then lvm control data lost<BR><BR></FONT></DIV>
<DIV><SPAN class=955372400-06072004><FONT face=Arial size=2>Well, I've slowly
been coming to grips with recovering with what to me is a pretty serious
hard disk calamity.</FONT></SPAN></DIV>
<DIV><SPAN class=955372400-06072004><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=955372400-06072004><FONT face=Arial size=2>I rebooted my
Linux system, as it was up and running for 48 days or so, and it just seemed
to be time to do it. When the system came back up, many of the hard disk
partician tables were lost, and it wouldn't boot.</FONT></SPAN></DIV>
<DIV><SPAN class=955372400-06072004><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=955372400-06072004><FONT face=Arial size=2>After much
research on the Internet, I found that a partician table could be re-written
and all the data in the file system maintained. </FONT></SPAN><SPAN
class=955372400-06072004><FONT face=Arial size=2>I also found a tool, TestDisk
at <A href="http://www.cgsecurity.org">http://www.cgsecurity.org</A> by
Christophe GRENIER <<A
href="mailto:grenier@cgsecurity.org">grenier@cgsecurity.org</A>>, which
seemed to do a good job of sniffing out partician tables from the remaining
file system data. Well, it did OK on the system disk, found the first
FAT partician and the ext3 partician for the root of the system. In
fact, after it wrote out the partician table, I could mount the root file
system without any sort of fsck required. Very cool.</FONT></SPAN></DIV>
<DIV><SPAN class=955372400-06072004><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=955372400-06072004><FONT face=Arial size=2>Of the LVM hard
disks, which is why I'm sending this email to the mailing list, 3 out of 4
partician tables were identified and recovered (/dev/hde1, /dev/hdf1,
/dev/hdg1). For L</FONT></SPAN><SPAN class=955372400-06072004><FONT
face=Arial size=2>vm, I always used a single primary partician, non-bootable,
which uses the entire space on the hard disk. So recovering this
partician table should be no problem, right? I used fdisk and re-created
the partician table.</FONT></SPAN></DIV>
<DIV><SPAN class=955372400-06072004><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=955372400-06072004><FONT face=Arial size=2>OK, so I've not
re-written the grub boot-loader on the system disk, but I did boot off of a
rescue CD and performed a chroot to where the root file system was mounted, so
I have a chrooted environment, and I can run access the binaries and file from
the old system hard disk. I check to make sure that the lvm module was
loaded using lsmod, and it was so, now I figured I'd see how far I could get
to recover the 130 GB of data that was on the LVM volume.</FONT></SPAN></DIV>
<DIV><SPAN class=955372400-06072004><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=955372400-06072004><FONT face=Arial size=2>First things
first, I tried vgscan, and got the following results:</FONT></SPAN></DIV>
<DIV><SPAN class=955372400-06072004><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=955372400-06072004><FONT face=Arial size=2>vgscan -- reading
all physical volumes (this may take a while...)<BR>vgscan -- ERROR
"vg_read_with_pv_and_lv(): current PV" can't get data of volume group "u00_vg"
from physical volume(s)<BR>vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d"
successfully created<BR>vgscan -- WARNING: This program does not do a VGDA
backup of your volume group<BR></FONT></SPAN></DIV>
<DIV><SPAN class=955372400-06072004><FONT face=Arial size=2>So, I'm at a loss
here. What is the next step in the recovery? How can I get my vg
and lv groups back?</FONT></SPAN></DIV>
<DIV><SPAN class=955372400-06072004><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=955372400-06072004><FONT face=Arial size=2>
Thanks in advance for the help.</FONT></SPAN></DIV>
<DIV><SPAN class=955372400-06072004><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=955372400-06072004><FONT face=Arial size=2>
Erik.</FONT></SPAN></DIV>
<DIV><SPAN class=955372400-06072004><FONT face=Arial
size=2> </DIV></BLOCKQUOTE></FONT></SPAN></BODY></HTML>