From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] VG lost, no lvmconf => Help !
Date: Thu Jan 24 08:47:02 2002 [thread overview]
Message-ID: <20020124154339.A8972@sistina.com> (raw)
In-Reply-To: <3C4EDF1A.3000409@cgg.com>; from gduquesnay@cgg.com on Wed, Jan 23, 2002 at 05:04:42PM +0100
Can you send "vgscan -d" to me in personal email (mge@sistina.com)?
What does lvm-1.0.1-1 mean. We don't have such version.
Please check with for eg. "vgdisplay -h".
On Wed, Jan 23, 2002 at 05:04:42PM +0100, Guillaume Duquesnay wrote:
> 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
<SNIP>
> Many thanks,
>
> Guillaume
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
--
Regards,
Heinz -- The LVM Guy --
*** 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2002-01-24 8:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-23 10:08 [linux-lvm] VG lost, no lvmconf => Help ! Guillaume Duquesnay
2002-01-24 8:47 ` Heinz J . Mauelshagen [this message]
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=20020124154339.A8972@sistina.com \
--to=mauelshagen@sistina.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