All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Muster <paul.muster@gmx.net>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] cannot access LVM1 any more
Date: Sat, 20 Oct 2007 18:01:03 +0200	[thread overview]
Message-ID: <471A263F.80706@gmx.net> (raw)
In-Reply-To: <20071002145032.118800@gmx.net>

Hello, there,


I still need help regarding this topic. Do you need some more 
information? Then please tell me.

In the meantime the system has been reinstalled, but a clone copy of the 
old system exists. I am trying to rescue the old data. When working on 
this I found a vgcfgbackup-file with valid-looking data. It begins with

---
# Generated by LVM2: <Date>

contents = "Text Format Volume Group"
version = 1
---

When trying "vgcfgrestore -f </above/described/file> volg1" on a Knoppix 
5.0.1 with LVM version 2.02.05 (Details at the end of quoted posting) I get

PV /dev/hde2 is a different format (seqno lvm1)
Restore failed.

What can I do to get my data back?


Thanks

Paul


Paul Muster wrote:
> Hello everybody,
> 
> 
> I have a really big problem: I cannot access my LVM1 PVs, VGs an LVs any more. So the system does not boot up.
> 
> The system was installed with Debian Woody and LVM1. I created 1 PV, 1 VG and some LVs. Later (maybe when changing to Sarge or Etch) I moved to LVM2, so I thought, I could remove the package lvm10 from the system. At some time I added another PV to the VG, resized one of the LVs.
> 
> Maybe because of one of this or when changing from Kernel 2.4 to 2.6.18 I obviously lost support for LVM1.
> 
> The last messages from the running system were:
> 
> # vgdisplay 
>     Invalid LV in extent map (PV /dev/sda3, PE 1080, LV 5, LE 0) 
>     Couldn't fill logical volume maps. 
>     Invalid LV in extent map (PV /dev/sda3, PE 1080, LV 5, LE 0) 
>     Couldn't fill logical volume maps. 
>     Volume group "volg1" not found
> 
> As said before, after a reboot the system did not come up again telling me, it cannot find the LVs.
> 
> 
> Please help me as I need the system and don't want to reinstall it. If you need some more information, please drop me a mail.
> 
> 
> Maybe there is a live-CD with old LVM1-support available with which I could boot, activate the old LVM, chroot to it and reinstall the lvm10-Package? (I would need the module megaraid since the PVs are on an hardware-RAID.)
> 
> 
> Thanks a lot in advance.
> 
> Paul
> 
> 
> Some details:
> 
> # fdisk -l /dev/sda 
>  
> Disk /dev/sda: 73.4 GB, 73410805760 bytes 
>  254 heads, 63 sectors/track, 8960 cylinders 
>  Units = cylinders of 16002 * 512 = 8193024 bytes 
>  
>     Device Boot      Start         End      Blocks   Id  System 
>  /dev/sda1   *           1         244     1952212+  83  Linux 
>  /dev/sda2             245        4485    33932241   8e  Linux LVM 
>  /dev/sda3            4486        8960    35804475   8e  Linux LVM 
>  
> There are two PVs, because some time the 36GB disk was replaced by a 7GB one. 
>  
> # pvdisplay 
>     --- Physical volume --- 
>     PV Name               /dev/sda2 
>     VG Name               volg1 
>     PV Size               32,36 GB / not usable 48,95 MB 
>     Allocatable           yes (but full) 
>     PE Size (KByte)       32768 
>     Total PE              1034 
>     Free PE               0 
>     Allocated PE          1034 
>     PV UUID               O17ru0-C8v2-3iLh-6isM-Z3n5-mn41-6nhDky 
>  
>    --- Physical volume --- 
>     PV Name               /dev/sda3 
>     VG Name               volg1 
>     PV Size               34,15 GB / not usable 53,31 MB 
>     Allocatable           yes 
>     PE Size (KByte)       32768 
>     Total PE              1091 
>     Free PE               11 
>     Allocated PE          1080 
>     PV UUID               pe1zVS-YN39-Rw1k-Esfg-WIdG-cl5h-OhDZmF 
>  
> One VolumeGroup on the PVs: 
>  
> # vgdisplay 
>     --- Volume group --- 
>     VG Name               volg1 
>     System ID             Knoppix1091952233 
>     Format                lvm1 
>     VG Access             read/write 
>     VG Status             resizable 
>     MAX LV                256 
>     Cur LV                5 
>     Open LV               5 
>     Max PV                256 
>     Cur PV                2 
>     Act PV                2 
>     VG Size               66,41 GB 
>     PE Size               32,00 MB 
>     Total PE              2125 
>     Alloc PE / Size       2114 / 66,06 GB 
>     Free  PE / Size       11 / 352,00 MB 
>     VG UUID               J75sG2-mUcD-aUet-g4EV-y3AS-UNfb-2LRwhj 
>  
> with some LVs inside: 
>  
> # lvdisplay 
>     --- Logical volume --- 
>     LV Name                /dev/volg1/logv1 
>     VG Name                volg1 
>     LV UUID                000000-0000-0000-0000-0000-0000-000000 
>     LV Write Access        read/write 
>     LV Status              available 
>     # open                 1 
>     LV Size                1,97 GB 
>     Current LE             63 
>     Segments               1 
>     Allocation             normal 
>     Read ahead sectors     1024 
>     Block device           254:0 
>  
> [...] 

And from another posting:

> # pvscan --version
>   LVM version:     2.02.05 (2006-04-21)
>   Library version: 1.02.05 (2006-04-19)
>   Driver version:  4.6.0
> 
> also only tells:
> 
> # pvscan
>   Invalid LV in extent map (PV /dev/sda3, PE 1080, LV 5, LE 0)
>   Couldn't fill logical volume maps.
>   Invalid LV in extent map (PV /dev/sda3, PE 1080, LV 5, LE 0)
>   Couldn't fill logical volume maps.
>   No matching physical volumes found
> 

  parent reply	other threads:[~2007-10-20 16:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-02 14:50 [linux-lvm] cannot access LVM1 any more Paul Muster
2007-10-02 14:54 ` Paul Muster
2007-10-20 16:01 ` Paul Muster [this message]
2007-10-20 20:47   ` Alasdair G Kergon
2007-10-31 11:24     ` Paul Muster

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=471A263F.80706@gmx.net \
    --to=paul.muster@gmx.net \
    --cc=linux-lvm@redhat.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.