All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guillaume Duquesnay <gduquesnay@cgg.com>
To: linux-lvm@sistina.com
Subject: [linux-lvm] VG lost, no lvmconf => Help !
Date: Wed Jan 23 10:08:02 2002	[thread overview]
Message-ID: <3C4EDF1A.3000409@cgg.com> (raw)

Here's my startup config :
on a single SCSI disk :
- linux 2.4.17 was booting on an lvm partiton, VG main, with LV : root, 
usr, boot, and  var.
- an old linux system, 2.4.17 also, but classical ext2-based.

The LVM linux system was created by copying the root partitions of the 
ext2 system (as described in the LVM doc). Everything was working great 
with the LVM-based system, but i kept the old ext2 system as a rescue 
linux. Then, I did a vgextend to a remaining PV to my VG, and it boot 
and works already.

Problems arrived when i tried to add a SCSI CD burner : lvm didn't find 
the PVs, nor the VG, causing a kernel panic at boot time, and so did the 
ext2 linux. I was unable to fix that problem (SCSI id checked, ...), i 
removed that SCSI device, and then only the ext2 system did boot again. 
My vg was no longer detected.

So, here's where i am : under the ext2 system, i have no lvmtab for my 
VG, neither a recent main.conf, and my vg is no more detected, so i 
cannot recover my vg with vgcfgrestore. I did scan the 2 LVM PVs, and 
they are ok.
So my question is :
is there a way to recover my VG with the datas contained in the PVs ?

info :

The system is a Linux-2.4.17 based kernel, with lvm-1.0.1-1

Here's my log :

////////------pvscan-------
# pvscan
pvscan -- reading all physical volumes (this may take a while...)
pvscan -- inactive PV "/dev/sda1"  is associated to an unknown VG (run 
vgscan)
pvscan -- inactive PV "/dev/sda3"  is associated to an unknown VG (run 
vgscan)
pvscan -- total: 2 [5.39 GB] / in use: 2 [5.39 GB] / in no VG: 0 [0]

///////------lvmdiskscan-------
-]# lvmdiskscan
lvmdiskscan -- reading all disks / partitions (this may take a while...)
lvmdiskscan -- /dev/sda1 [       3.99 GB] Primary  LVM partition [0x8E]
lvmdiskscan -- /dev/sda2 [       2.60 GB] Primary  LINUX native 
partition [0x83]lvmdiskscan -- /dev/sda3 [       1.39 GB] Primary  LVM 
partition [0x8E]
lvmdiskscan -- /dev/sda4 [     494.19 MB] Primary  LINUX swap partition 
[0x82]
lvmdiskscan -- 1 disk
lvmdiskscan -- 0 whole disks
lvmdiskscan -- 0 loop devices
lvmdiskscan -- 0 multiple devices
lvmdiskscan -- 0 network block devices
lvmdiskscan -- 4 partitions
lvmdiskscan -- 2 LVM physical volume partitions

///////------vgscan--------
]# vgscan
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
vgscan -- WARNING: This program does not do a VGDA backup of your volume 
group

///////------vgdisplay-----
]# vgdisplay
vgdisplay -- no volume groups found


///////------pvdata-------
]# pvdata -v -V -L /dev/sda1 | grep -v empty
--- Volume group ---
VG Name
VG Access             read/write
VG Status             NOT available/resizable
VG #                  0
MAX LV                256
Cur LV                4
Open LV               0
MAX LV Size           255.99 GB
Max PV                256
Cur PV                2
Act PV                2
VG Size               5.38 GB
PE Size               4.00 MB
Total PE              1376
Alloc PE / Size       1277 / 4.99 GB
Free  PE / Size       99 / 396.00 MB
VG UUID               ML3C0g-bpt6-2He5-AK6f-5DNt-2LVV-bEm05U

--- List of logical volumes ---

--- Logical volume ---
LV Name                /dev/main/boot
VG Name                main
LV Write Access        read/write
LV Status              NOT available
LV #                   1
# open                 0
LV Size                40.00 MB
Current LE             10
Allocated LE           10
Allocation             next free
Read ahead sectors     120
Block device           58:0
read_ahead: 120

--- Logical volume ---
LV Name                /dev/main/root
VG Name                main
LV Write Access        read/write
LV Status              NOT available
LV #                   2
# open                 0
LV Size                1.00 GB
Current LE             256
Allocated LE           256
Allocation             next free
Read ahead sectors     120
Block device           58:1
read_ahead: 120

--- Logical volume ---
LV Name                /dev/main/usr
VG Name                main
LV Write Access        read/write
LV Status              NOT available
LV #                   3
# open                 0
LV Size                3.00 GB
Current LE             768
Allocated LE           768
Allocation             next free
Read ahead sectors     120
Block device           58:2
read_ahead: 120

--- Logical volume ---
LV Name                /dev/main/var
VG Name                main
LV Write Access        read/write
LV Status              NOT available
LV #                   4
# open                 0
LV Size                972.00 MB
Current LE             243
Allocated LE           243
Allocation             next free
Read ahead sectors     120
Block device           58:3
read_ahead: 120

pvdata -- logical volume struct at offset   4 is empty
....

and i have the same for /dev/sda3

///////////----------------

So, how can i use this stuff to recreate a good VG info and make my 
system back ?
Many thanks,

Guillaume

             reply	other threads:[~2002-01-23 10:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-23 10:08 Guillaume Duquesnay [this message]
2002-01-24  8:47 ` [linux-lvm] VG lost, no lvmconf => Help ! Heinz J . Mauelshagen
2002-01-24  9:18   ` Guillaume Duquesnay
2002-01-24 10:17     ` Heinz J . Mauelshagen
2002-01-24 11:55       ` [Re: [linux-lvm] VG lost, no lvmconf => Help ! ] Corrupted PV UUID Guillaume Duquesnay
2002-01-25  4:12         ` Heinz J . Mauelshagen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3C4EDF1A.3000409@cgg.com \
    --to=gduquesnay@cgg.com \
    --cc=linux-lvm@sistina.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.