All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tod <tod@stthomasepc.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] vgdisplay can't see volume group after upgrade
Date: Tue, 06 May 2008 20:59:53 -0400	[thread overview]
Message-ID: <4820FF09.4000309@stthomasepc.org> (raw)

I'm trying to upgrade (yum) from FC6 to FC8.  I started by upgrading to 
FC7 but that hosed something giving me a kernel panic trying to find 
/dev/root so I figured I'd push ahead to FC8 to see if that would 
resolve my problem.

I have one small /boot partition on my first drive the rest of it and a 
second drive is all lvm.  Once I discovered the problem with the FC8 
upgrade I rebooted back to my FC6 kernel.  Everything boots fine but 
vgdisplay shows nothing.  When I run system-config-lvm it sees the 
second lvm partition of my first drive unallocated, as well as the 
entire second drive.

I can back everything up and just reinstall but I've upgraded fedora 
using yum before and while there were problems I always found a way to 
make it work.  This one has me stumped.  I believe the kernel panic 
_might_ be coming from the fact the kernel doesn't recognize my managed 
volumes.  Maybe the lvm meta information is trashed?

If anybody can help I'd appreciate it.  Any diagnostics or hints would 
be appreciated.  I can reinstall but I'd like to get it working on my 
own so I can learn something.

I'll be happy to post any system information necessary if it will help. 
  Also, I did prepare for the upgrade by applying labels and validating 
fstab, and grub.conf before proceeding.

Thanks - Tod

                 reply	other threads:[~2008-05-07  1:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4820FF09.4000309@stthomasepc.org \
    --to=tod@stthomasepc.org \
    --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.