All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: Chris Maxwell <cmaxwell@dal.ca>, linux-raid@vger.kernel.org
Subject: Re: Assistance Reviewing Proposed Recovery Measures
Date: Sat, 20 Aug 2016 11:16:39 +0100	[thread overview]
Message-ID: <57B82E07.4080109@youngman.org.uk> (raw)
In-Reply-To: <alpine.LRH.2.11.1608191717050.23388@bluenose.cs.dal.ca>

On 19/08/16 21:18, Chris Maxwell wrote:
> However, the it also says
> 
>> Recreating should be considered a *last* resort, only to be used when
>> everything else fails. People getting this wrong is one of the primary
>> reasons people lose data. It is very commonly used way too early in
>> the fault finding process. You have been warned! It's better to send
>> an email to the linux-raid mailing list with detailed information
>> (mdadm --examine from all component drives plus log entries from when
>> the failure happened, including mdadm and kernel version) and ask for
>> advice than to try to use --create --assume-clean and getting it wrong.
> 
> 
> 
> So before I messed things up even worse, I figured I would consult the
> experts to see what my next step should be.
> 
Download Phil Turmel's lsdrv. It should be easy to find with google. If
your default Python is 3, just edit the shebang line to make it run.

SAVE THE HARD COPY IN A SAFE PLACE!!!

If anything does go wrong (Sarah's comments about wiping superblocks etc
etc unnerve me) this *should* have all the information you need to
recreate the drives and recover what's recoverable.

(Oh - and the linux raid wiki is a bit of a cobweb site at the moment
:-( so take anything on it with a pinch of salt - it could well be out
of date.)

Also download the latest mdadm from Neil Brown's site. Most distros are
a bit out of date, and the bug fixes might matter.

Cheers,
Wol

  parent reply	other threads:[~2016-08-20 10:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-19 20:18 Assistance Reviewing Proposed Recovery Measures Chris Maxwell
2016-08-20  2:48 ` Sarah Newman
2016-08-20 10:16 ` Wols Lists [this message]
2016-08-22 12:09 ` Phil Turmel

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=57B82E07.4080109@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=cmaxwell@dal.ca \
    --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.