Linux LVM users
 help / color / mirror / Atom feed
From: "Tim-Patrick Märk" <tpmaerk@gmx.net>
To: linux-lvm@sistina.com
Subject: [linux-lvm] Erroneously formatted PV; 'vgscan -- ERROR "vg_read_with_pv_and_lv(): current PV" can't get data of volume group'...
Date: Tue Feb 11 18:44:01 2003	[thread overview]
Message-ID: <000301c2d22f$ae474f40$0400000a@lenina> (raw)

Heinz,

thank you very much!

I built a kernel with LVM2/ device-mapper (and XFS) on my emergency
system and ran 'vgscan' and 'vgchange --partial -a y' as you said.
The LVs were mounted read-only, so I copied the root-LV to another
partition (ext2), booted it and restored the old LVM metadata using
'vgcfgrestore'.
Some "minor" problems (related to properly patching the kernel etc.)
occured during this process, but all in all it worked well and now I'm
very happy to have my data back :)!

Tank you again!


> 
> Tim-Patrick,
> 
> with your root on LV setup you either need:
> 
> 
> an emergency boot media with LVM1 on it _and_ /etc/lvmconf/* backup in
> order to restore you LVM metadata using vgcfgrestore presuming you
setup
> your partitions exactly the way they were before ("vgscan;vgchange
-ay" a=
> fter
> metadata restore)
> 
> - or -
> 
> an emergency boot media with LVM2/device-mapper on it to
> run "vgscan ; vgchange --partial -a y" in order to
> access your partioal VG without the gone partition
> 
> - or -
> 
> that LVM2 boot media to restore the metadata.
> 
> - or -
> 
> to attach your HDDs to another LVM equipped system to repair the
> volume group configuration
> 
> Regards,
> Heinz    -- The LVM Guy --
> 
> 
> *** Software bugs are stupid.
>     Nevertheless it needs not so stupid people to solve them ***
> 
>
=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-
=3D=
>
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D
-=
> =3D-=3D-
> 
> Heinz Mauelshagen                                 Sistina Software
Inc.
> Senior Consultant/Developer                       Am Sonnenhang 11
>                                                   56242 Marienrachdorf
>                                                   Germany
> Mauelshagen@Sistina.com                           +49 2626 141200
>                                                        FAX 924446
>
=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-
=3D=
>
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D
-=
> =3D-=3D-

             reply	other threads:[~2003-02-11 18:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-11 18:44 Tim-Patrick Märk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-09 12:55 [linux-lvm] Erroneously formatted PV; 'vgscan -- ERROR "vg_read_with_pv_and_lv(): current PV" can't get data of volume group' Tim-Patrick Märk
2003-02-10  7:47 ` 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='000301c2d22f$ae474f40$0400000a@lenina' \
    --to=tpmaerk@gmx.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox