Linux LVM users
 help / color / mirror / Atom feed
From: Heinz Mauelshagen <mauelshagen@redhat.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] How to recover a VG from another PC?
Date: Fri Jan 16 08:57:09 2004	[thread overview]
Message-ID: <20040116111312.GE2837@redhat.com> (raw)
In-Reply-To: <40067D39.20407@iku-ag.de>

Kurt,

send me <mauelshagen@redhat.com> a copy of the bzip2'ed output of
"dd if=/dev/hdc2 ibs=1k count=4k" and i'll have a go on your metadata trying
to repair it and send it back to you for VG recovery.

Cheers,
Heinz    -- The LVM Guy --

On Thu, Jan 15, 2004 at 12:44:57PM +0100, Kurt Huwig wrote:
> Hi!
> 
> I've got the following problem:
> 
> I replaced an old SUSE 7.3, Kernel 2.4.10 (or so) by a current Debian 
> with 2.4.23. There was an IDE disk:
> 
> /dev/hdc2            65      5005  39688582+  8e  Linux LVM
> 
> There was a volume group called 'ide' containing only this one partition.
> 
> Unfortunately I did the reinstall before reading the LVM manual and so 
> did not use the export-feature. What I get from 'vgscan -d' is:
> 
> <333> pv_check_volume -- CALLED  dev_name: "/dev/hdc2"  pv: 804D110
> <4444> pv_check_name -- CALLED with "/dev/hdc2"
> <55555> lvm_check_chars -- CALLED with name: "/dev/hdc2"
> <55555> lvm_check_chars -- LEAVING with ret: 0
> <4444> pv_check_name -- LEAVING with ret: 0
> <4444> pv_check_new -- CALLED
> <4444> pv_check_new -- LEAVING with ret: 0
> <4444> vg_check_name -- CALLED with VG: ide
> <55555> lvm_check_chars -- CALLED with name: "ide"
> <55555> lvm_check_chars -- LEAVING with ret: 0
> <4444> vg_check_name -- LEAVING with ret: -348
> <333> pv_check_volume -- LEAVING with ret: 0
> <22> pv_read_all_pv -- device /dev/hdc2 NOT used
> 
> but no volume group appears.
> 
> What can I do?
> 
> 
> Kurt
> -- 
> Kurt Huwig             iKu Systemhaus AG        http://www.iku-ag.de/
> Vorstand               Am Römerkastell 4        Telefon 0681/96751-0
>                        66121 Saarbrücken        Telefax 0681/96751-66
> GnuPG 1024D/99DD9468 64B1 0C5B 82BC E16E 8940  EB6D 4C32 F908 99DD 9468

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

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

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

      reply	other threads:[~2004-01-16  8:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-15  8:54 [linux-lvm] How to recover a VG from another PC? Kurt Huwig
2004-01-16  8:57 ` Heinz Mauelshagen [this message]

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=20040116111312.GE2837@redhat.com \
    --to=mauelshagen@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox