From: Jaap Winius <jwinius@umrk.nl>
To: linux-raid@vger.kernel.org
Subject: Re: Can this array be recovered?
Date: Tue, 25 Dec 2012 17:06:39 +0000 (UTC) [thread overview]
Message-ID: <kbcmeu$ste$3@ger.gmane.org> (raw)
In-Reply-To: kbcibm$ste$2@ger.gmane.org
On Tue, 25 Dec 2012 15:56:38 +0000, Jaap Winius wrote:
> # pvscan -u
> Incorrect metadata area header checksum PV /dev/md2 with UUID
> 0iEU34-XNSd-vNpu-G3uW-2F1v-wEy9-Bw199N VG
> volgrp3 lvm2 [931.51 GiB / 11.51 GiB free]
> PV /dev/md0 with UUID Lb3KzG-9tZM-5MbQ-1DUa-5ErW-DYf1-NqvMJW VG
> volgrp1 lvm2 [697.70 GiB / 5.44 GiB free]
> PV /dev/md1 with UUID uWDdXr-8fRw-aJDG-SzdQ-
> yeIl-6dsv-28vJYs lvm2 [697.70 GiB]
> Total: 3 [2.27 TiB] / in use: 2 [1.59 TiB] / in no VG: 1 [697.70 GiB]
>
> That last UUID is still associated with a bunch of volgrp2 objects in my
> current LVM configuration (the old LVM volume on /dev/md1), even though
> pvscan currently doesn't recognize it as such.
All that was needed at this point involved some LVM recovery procedures.
I did it like this:
# pvcreate --uuid uWDdXr-8fRw-aJDG-SzdQ-yeIl-6dsv-28vJYs --restorefile /
etc/lvm/archive/volgrp2_00007.vg /dev/md1
Incorrect metadata area header checksum
Incorrect metadata area header checksum
Incorrect metadata area header checksum
Incorrect metadata area header checksum
Incorrect metadata area header checksum
Physical volume "/dev/md1" successfully created
This restored my original LVM physical volume. However, the original
volume group was missing. To fix that I created one with the same name on
that same physical device:
# vgcreate -v volgrp2 /dev/md1
Wiping cache of LVM-capable devices
Wiping cache of LVM-capable devices
Adding physical volume '/dev/md1' to volume group 'volgrp2'
Archiving volume group "volgrp2" metadata (seqno 0).
Creating volume group backup "/etc/lvm/backup/volgrp2" (seqno 1).
Volume group "volgrp2" successfully created
Okay, but at this point the problem was that my logical volumes had yet
to be restored
# vgcfgrestore -f /u21/backup/bitis/etc/2012-12-24@01:02:12/lvm/backup/
volgrp2 volgrp2
Restored volume group volgrp2
This restored the volume group descriptor area from an older automatic
backup file for this volume group. It worked: my old vicepb volume was
back! Still, I couldn't mount it until I did this:
~# vgchange -ay
3 logical volume(s) in volume group "volgrp3" now active
1 logical volume(s) in volume group "volgrp2" now active
6 logical volume(s) in volume group "volgrp1" now active
Finally, this allowed me to mount my volume and make all my data
available once again.
Thanks Phil!
Chritmas cheers,
Jaap
prev parent reply other threads:[~2012-12-25 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-25 4:14 Can this array be recovered? Jaap Winius
2012-12-25 6:05 ` Phil Turmel
2012-12-25 15:24 ` Jaap Winius
2012-12-25 15:56 ` Jaap Winius
2012-12-25 17:06 ` Jaap Winius [this message]
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='kbcmeu$ste$3@ger.gmane.org' \
--to=jwinius@umrk.nl \
--cc=linux-raid@vger.kernel.org \
/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.