All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heinz Mauelshagen <mauelshagen@redhat.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Problems importing volume group
Date: Sat Feb 14 05:17:00 2004	[thread overview]
Message-ID: <20040214101743.GD22753@redhat.com> (raw)
In-Reply-To: <2022.63.106.141.106.1076694581.squirrel@www.fusion-hosting.net>

Chris,

looks like the installation toasted your PVs (writing partition tables
to the drives?).

Run vgcfgrestore (you've got a backup of /etc/lvmconf/*, right?).

Regards,
Heinz    -- The LVM Guy --


On Fri, Feb 13, 2004 at 12:49:41PM -0500, Chris Wells wrote:
> Hello all,
> 
> I'm still a newbie to LVM but I've followed a FAQ in exporting my VG (I
> had to replace a failing system drive - not in the VG).  When I replaced
> the drive and tried to import the volume group, I get the following
> errors:
> 
> vgimport kbvg /dev/hde /dev/hdf
> vgimport -- ERROR "pv_check_consistency(): PE size" checking physical
> volume consistency of "/dev/hde"
> vgimport -- ERROR "pv_check_consistency(): PE size" checking physical
> volume consistency of "/dev/hdf"
> vgimport -- ERROR: no valid physical volumes found to import volume group
> "kbvg"
> 
> When I do a pvscan, I get:
> 
> pvscan
> pvscan -- reading all physical volumes (this may take a while...)
> pvscan -- inactive PV "/dev/hde"  is in EXPORTED VG "kbvg" [0 / 0 free]
> pvscan -- inactive PV "/dev/hdf"  is in EXPORTED VG "kbvg" [0 / 0 free]
> pvscan -- total: 2 [37.46 MB] / in use: 2 [37.46 MB] / in no VG: 0 [0]
> 
> 
> I get these errors even when replacing the old drive and trying to import
> back.  Any ideas on what I can do next or what the problem could be?  Or..
> at least, does anyone know of any tools which I can use to retrieve data
> from these drives?
> 
> Any help is greatly appreciated!
> 
> -- 
> Thanks,
>    Chris Wells
>    Fusion Hosting & Design
>    Lexington, KY
>    chris@fusion-hosting.net
>    http://www.fusion-hosting.net
>    Phone: (859) 492-6439
> 
> 
> _______________________________________________
> 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/

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Red Hat, Inc.
Consulting Development Engineer                   Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@RedHat.com                            +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2004-02-14 10:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-13 12:49 [linux-lvm] Problems importing volume group Chris Wells
2004-02-14  5:17 ` Heinz Mauelshagen [this message]
2004-02-15  1:56   ` Chris Wells
2004-02-16  4:22     ` Heinz 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=20040214101743.GD22753@redhat.com \
    --to=mauelshagen@redhat.com \
    --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.