Linux-LVM Archive mirror
 help / color / mirror / Atom feed
From: <linux-lvm@harrier.ch>
To: <linux-lvm@redhat.com>
Subject: [linux-lvm] LVM: Metadata on ... has wrong VG name
Date: Sun, 19 Dec 2021 07:14:08 -0500	[thread overview]
Message-ID: <39400.121121907140600191@us-mta-191.us.mimecast.lan> (raw)


G'day


Issue: How do I repair this situation?
  >sudo pvscan
   Metadata on /dev/sdd2 at 12800 has wrong VG name “fedora32 {
   id = “gJgZM9-n2Rd-V7us-RWae-cpT6-H84E-g7dAsk”
   seqno = 9
   format = “lvm2”
   status = [“RESIZEABLE”, “READ”, “WRITE”]
   flag” expected fedora.
   WARNING: Reading VG fedora on /dev/sdd2 failed.
   WARNING: PV /dev/sdd2 is marked in use but no VG was found using it.
   WARNING: PV /dev/sdd2 might need repairing.

Background:
  I am a simple long-time developer, attempting to upgrade Fedora, first exposure to LVM.
  I cloned my old drive to a new one, same size. Pretty much out-of-the-box installation - a single PV contains LVs root, home and swap

  Upon completion, I renamed the Volume Group on the original drive (/dev/sdd2) with the intent to mount both Volume Groups concurrently:
   > sudo lvm vgrename GGUoJ7-Cj8n-yYnW-DjO7-HHJQ-mMey-jOlBXx fedora32

  I'm working with a Fedora Live USB, LVM TOOLS 2.03.11(2) (2021-01-08), which I rebooted at this point

  A PVID conflict arose, which I solved by changing the PV UUID on the new drive:
   > sudo lvm pvchange -u /dev/sda2

Now I get no access to the logical volumes on the old drive with the error above.

So how do either 1) correctly propagate or 2) roll back the Volume Group Name change?

I’ve found some references to “repair”, recreating the LVM metadata, but am hesitant as I would not like to lose the contents of the old drive. /etc/lvm only has a backup from the pvchange execution on the new disk, nothing from the original due to the reboot. I got in this situation thru RTFM - I didn’t realise RTWholeFM was required. Still looking for procedures: where I went wrong, how to fix it. Nothing in the archives seems to address this directly.

Has been ages since I patched disk sectors but that's the only option I have any minor confidence in at this point. Is there a simple reference to a procedure that can help me recover this?  

Thanks


j

_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

             reply	other threads:[~2021-12-20  6:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-19 12:14 linux-lvm [this message]
2021-12-20 16:52 ` [linux-lvm] LVM: Metadata on ... has wrong VG name David Teigland
  -- strict thread matches above, loose matches on Subject: below --
2021-12-26  8:23 linux-lvm
2022-01-06 19:23 ` David Teigland

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=39400.121121907140600191@us-mta-191.us.mimecast.lan \
    --to=linux-lvm@harrier.ch \
    --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 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 read-only IMAP folder(s) and NNTP newsgroup(s).