From: AJ Lewis <lewis@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] vg gone after vgextend
Date: Tue, 10 Jul 2001 11:06:56 -0500 [thread overview]
Message-ID: <20010710110656.A24243@sistina.com> (raw)
In-Reply-To: <20010710093902.B30416@zendo.net>; from lvm@zendo.net on Tue, Jul 10, 2001 at 09:39:02AM -0500
[-- Attachment #1: Type: text/plain, Size: 3338 bytes --]
Goto ftp://ftp.sistina.com/pub/LVM/contrib and get
uuid_fixer-0.3-IOP10.tar.gz
Read the README. Run it on your system, then run vgscan. It should fix
your problem. If not, let me know.
On Tue, Jul 10, 2001 at 09:39:02AM -0500, Eli Criffield wrote:
> I had LVM up and working great, even on the / filesystem. I had a
> /dev/hda1 that was a 4 gig filesystem that i tared my distribution to and
> /dev/hda2 that use to be my / filesystem and /dev/hda3 that was my volume
> group. I resized /dev/hda1 down to around 30 megs and made /dev/hda2
> 4+gig. I made /dev/hda1 /boot and had a initrd to turn on LVM and boot to
> the / filesystem on /dev/rootvg/root_lv. That all worked fine.
>
> Until i added /dev/hda2 (now about 4gig) to the volumegroup rootvg. All
> looked ok when i went to reboot. On the reboot it died in the ramdisk when
> it ran vgscan.
> "vgscan -- no volume groups found"
>
> I was then stuck with a none bootable machine. I'll save you the long
> story about the trouble i had making some kind of rescue disk, but i
> finally got one to work off a cd i had a friend burn for me.
>
> Now when i run pvscan i get
> "pvscan -- inactive PV "/dev/hda3" is associated to an unknown VG (run
> vgscan)
> pvscan -- total: 14.4GB / in use 1 [14.4GB] / in no VG 0 [0]"
>
> it doesn't see /dev/hda2 that i added to the vg right before reboot, but
> thats not a problem because there was nothing on it yet anyway.
>
> pvscan -vv gives
>
> -- Physical volume ---
> PV Name /dev/hda3
> VG Name rootvg
> PV Size 14.4 GB / NOT usable 3.48 MB [LVM: 135KB]
> PV# 1
> PV Status available
> Allocatable yes
> CurLV 6
> P ESize (KByte) 4096
> Total PE 3685
> Free PE 1261
> Allocated PE 2424
> PV UUID elhLo-Mw5J-8qaE-gN2D-zEYo-Woqh-qH7H5a
> System Id eli.custom-edge.com993738446
>
>
> from what i can tell from the archives to do a vgcfgrestore is the next
> logical thing but it doesn't work for me
>
> vgcfgrestore -n rootvg /dev/hda3
> vgcfgrestore -- "/etc/lvmconf/rootvg.conf" doesn't exist
> vgcfgrestore -- a backup for volume group rootvg is not available
>
> which makes since because i booted off a rescue disk in a ram disk.
>
> vgscan still gives
> vgscan -- no volume groups found
>
> i did find this answer in the archives for a similar problem:
>
> > You need to edit the disk signatures and for each PV, insert all the
> > _other_ PV signatures in the right place.
>
> but no explanation on how to do that?
>
> Is that what i should be doing? If so how do i do that? If not what can i
> do to save this box?
>
> thanks a ton it will save a lot of hassle if i don't have to reinstall.
>
> eli
--
AJ Lewis
Sistina Software Inc. Voice: 612-638-0500
1313 5th St SE, Suite 111 Fax: 612-638-0500
Minneapolis, MN 55414 E-Mail: lewis@sistina.com
http://www.sistina.com
Current GPG fingerprint = 3B5F 6011 5216 76A5 2F6B 52A0 941E 1261 0029 2648
Get my key at: http://www.sistina.com/~lewis/gpgkey
(Unfortunately, the PKS-type keyservers do not work with multiple sub-keys)
-----Begin Obligatory Humorous Quote----------------------------------------
Hey! It compiles! Ship it!
-----End Obligatory Humorous Quote------------------------------------------
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-07-10 16:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-10 14:39 [linux-lvm] vg gone after vgextend Eli Criffield
2001-07-10 16:06 ` AJ Lewis [this message]
2001-07-10 16:39 ` Eli Criffield
2001-07-10 17:12 ` AJ Lewis
2001-07-10 18:57 ` Eli Criffield
2001-07-10 19:05 ` AJ Lewis
2001-07-10 19:13 ` Eli Criffield
2001-07-10 19:24 ` AJ Lewis
2001-07-10 19:47 ` Eli Criffield
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=20010710110656.A24243@sistina.com \
--to=lewis@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;
as well as URLs for NNTP newsgroup(s).