All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: jtroan@jt-sw.com, linux-raid@vger.kernel.org
Subject: Re: Resurrecting a Dirty RAID-5
Date: Wed, 8 Jul 2015 09:19:48 -0400	[thread overview]
Message-ID: <559D2374.7040208@turmel.org> (raw)
In-Reply-To: <OFC233BA12.DDED55A2-ON85257E7C.00420655-85257E7C.0043331F@jt-sw.com>

Good morning John,

On 07/08/2015 08:14 AM, jtroan@jt-sw.com wrote:

[trim /]

> I booted from the RHEL 6.5 DVD and entered rescue mode.  Using information
> from the Linux RAID wiki [1], I was able to confirm that my sd0 and sd1
> drives are alive and have all three partitions I had originally deployed to
> them -- /boot, /, and swap space.
> 
> Following the advice on the wiki [1], I'm asking for some help in using
> mdadm via rescue mode in trying to get this dirty RAID-5 back on its feet
> with the surviving two drives.  (I've got a third drive already on hand
> that's I'll then use to bring the RAID back to full robustness.)

From this report, you should only need to do a forced assembly from the
rescue environment with the good devices.  Like so (substituting actual
names):

mdadm -Afv /dev/md2 /dev/sda2 /dev/sdb2

If that fails, paste the verbose output in your reply here.

If the above succeeds, you may shut down, plug in your new drive, and
boot into your normal environment (still degraded, but should be
bootable).  Then add the new drive's partitions to each array.

Don't do *anything* else.

HTH,

Phil

  reply	other threads:[~2015-07-08 13:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-08 12:14 Resurrecting a Dirty RAID-5 jtroan
2015-07-08 13:19 ` Phil Turmel [this message]
2015-07-09  2:57   ` jtroan
2015-07-12  5:57     ` Mikael Abrahamsson
2015-07-12 15:01       ` jtroan
2015-07-12 22:33         ` Adam Goryachev
2015-07-13  6:31           ` Can Jeuleers
2015-07-13  7:15             ` Adam Goryachev

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=559D2374.7040208@turmel.org \
    --to=philip@turmel.org \
    --cc=jtroan@jt-sw.com \
    --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.