From: "Stuart D. Gathman" <stuart@bmsi.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Rebuilding ext4 filesystem on an LV
Date: Thu, 8 Jul 2010 15:13:39 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.1007081510460.10077@bmsred.bmsi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1007081459130.10077@bmsred.bmsi.com>
On Thu, 8 Jul 2010, Stuart D. Gathman wrote:
> Method 2:
> With both new and failed drive connected, use dd_rescue or equivalent to
> copy (most/some of) the failed drive to the new drive. Remove failed
> drive and bring up VG. If UUID was not readable on failed drive, use
> pvcreate to restore it on new drive.
I should mention that an external case-free USB adapter is the best way
to attempt recovery of failed drives. You can even run the IDE/SATA/Power
cable to a box in the freezer (and the USB adapter can sit on top of the
freezer and a long USB cable go to your computer) - which often helps recover
data from failing drives.
--
Stuart D. Gathman <stuart@bmsi.com>
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.
next prev parent reply other threads:[~2010-07-08 19:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 1:30 [linux-lvm] Rebuilding ext4 filesystem on an LV Ken Bass
2010-07-05 5:54 ` Bryan Whitehead
2010-07-05 8:52 ` Ken Bass
2010-07-05 10:06 ` Bryan Whitehead
2010-07-05 15:39 ` Ken Bass
2010-07-05 18:27 ` Stuart D. Gathman
2010-07-05 21:16 ` Ken Bass
2010-07-06 16:17 ` Malahal Naineni
2010-07-08 2:46 ` Ken Bass
2010-07-08 18:59 ` Malahal Naineni
2010-07-08 19:06 ` Stuart D. Gathman
2010-07-08 19:13 ` Stuart D. Gathman [this message]
2010-07-12 18:57 ` Ken Bass
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=Pine.LNX.4.64.1007081510460.10077@bmsred.bmsi.com \
--to=stuart@bmsi.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 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).