archive mirror
 help / color / mirror / Atom feed
From: Brian McCullough <>
To: LVM general discussion and development <>
Subject: Re: [linux-lvm] Recovering "broken" disk ( 17th )
Date: Mon, 18 Oct 2021 15:45:08 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Mon, Oct 18, 2021 at 09:49:44AM -0500, Roger Heflin wrote:
> You will need a lvm backup file for the pvcreate --uuid I believe (there
> may be some option to get around needing the backup file).
> That will put the header back on if you either have an lvm backup and/or
> archive file, you might also need a vgcfgrestore afterwards depending on if
> anything else is missing.
> I have never done it, but it looks possible to make a lvm backup file by
> reading it directly off the disk with dd, so that you will have a file that
> pvcreate is ok with, that is if there is no way to force it without a
> backup file.
> But, this should get the pv back showing up with whatever sectors that you
> successfully recovered.

Thank you, Roger.

I might be able to do that on the original machine, which won't boot at
the moment because of this failure, but I have been using a working
machine so far to use ddrestore etc.

Yes, as you said, I was able to use dd to copy off the vgconfig data
into a file.  So you think that I might be able to use that as the
reference in pvcreate?  That makes some sense.

I started this out asking ( but not clearly ) whether the data on the
disk appeared to be in the correct place and whether what was there was
correct, but I think that I answered that for myself with the
comparison to the working PV partition.

Thanks again,

linux-lvm mailing list
read the LVM HOW-TO at

  reply	other threads:[~2021-10-19  6:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-18  2:17 [linux-lvm] Recovering "broken" disk ( 17th ) Brian McCullough
2021-10-18 14:49 ` Roger Heflin
2021-10-18 19:45   ` Brian McCullough [this message]
2021-10-19 10:06     ` Roger Heflin
2021-10-20 13:38       ` Brian McCullough
2021-10-20 18:01         ` Roger Heflin
2021-10-20 18:04           ` Roger Heflin
2021-10-21  6:13             ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).