All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian McCullough <bdmc@bdmcc-us.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Help restoring a corrupted PV partition ( 18th )
Date: Mon, 18 Oct 2021 14:08:53 -0400	[thread overview]
Message-ID: <20211018180853.GF28058@bdmcc-us.com> (raw)


I have had a disk go bad on me, causing me to lose one PV.

If I am not providing sufficient, or the proper, information, feel free
to ask for more.


I seem to have retrieved the partition using ddrescue and put it on to
a new drive, but it seems to be missing some label information, because
pvscan doesn't recognize it as a PV partition.

Using hexdump, I see the string " LVM2 " at 0x1004, but nothing before
that.  The whole 16 bytes is:

0x01000  16 d6 8e db 20 4c 56 4d  32 20 78 5b 35 41 25 72
                        L  V  M  2



I find what appears to be an LVM2 vgconfig block starting at 0x01200,
extracted that to a file and was able to read the UUID that this PV
should have.  It is one of about a dozen that make up this VG.


On another machine, I dumped a PV partition, and find "LABLEONE" at
0x200, with the same " LVM2 " at 0x01000.

I was concerned that my dump was offset, but the comparison to the
"good" one suggests that that isn't the problem, but just the missing
"LABLEONE" and related information at 0x0200.


How to fix?

If I do a "pvcreate --uuid xxxx" would this fix that recovered partition
so that pvscan and friends can work properly, and I can finally boot
that machine?


Thank you,
Brian

_______________________________________________
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-10-18 18:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-18 18:08 Brian McCullough [this message]
2021-10-18 21:40 ` [linux-lvm] Help restoring a corrupted PV partition ( 18th ) Zdenek Kabelac
2021-10-18 22:20   ` Brian McCullough

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=20211018180853.GF28058@bdmcc-us.com \
    --to=bdmc@bdmcc-us.com \
    --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.