RE: First corrupt partician tables, then lvm control data lost

"Erik Ch. Ohrnberger" <Erik@server.echohome.org> · Tue, 6 Jul 2004 05:15:47 -0400

Title: Message

Additionally, pvscan reports the following:
pvscan 
-- reading all physical volumes (this may take a while...)
pvscan -- inactive 
PV "/dev/hdg1"  is associated to unknown VG "u00_vg" (run vgscan)
pvscan 
-- inactive PV "/dev/hdh1"  is associated to unknown VG "u00_vg" (run 
vgscan)
pvscan -- inactive PV "/dev/hde1"  is associated to unknown VG 
"u00_vg" (run vgscan)
pvscan -- total: 3 [204.96 GB] / in use: 3 [204.96 GB] 
/ in no VG: 0 [0]

What 
must I do to re-associate the pv into the vg?

  -----Original Message-----
From: Erik Ch. 
  Ohrnberger [mailto:Erik@EchoHome.org] On Behalf Of 
  lvm@echohome.org
Sent: Monday, July 05, 2004 8:56 
  PM
To: 'linux-lvm@redhat.com'
Subject: First corrupt 
  partician tables, then lvm control data lost

  Well, I've slowly 
  been coming to grips with recovering with what to me is a pretty serious 
  hard disk calamity.

  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.

  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.  I also found a tool, TestDisk 
  at http://www.cgsecurity.org by 
  Christophe GRENIER <grenier@cgsecurity.org>, 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.

  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 Lvm, 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.

  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.

  First things 
  first, I tried vgscan, and got the following results:

  vgscan -- reading 
  all physical volumes (this may take a while...)
vgscan -- ERROR 
  "vg_read_with_pv_and_lv(): current PV" can't get data of volume group "u00_vg" 
  from physical volume(s)
vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" 
  successfully created
vgscan -- WARNING: This program does not do a VGDA 
  backup of your volume group

  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?

  Thanks in advance for the help.

  Erik.

_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/