linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: Daniel Sanabria <sanabria.d@gmail.com>
Cc: Chris Murphy <lists@colorremedies.com>,
	Wols Lists <antlists@youngman.org.uk>,
	Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Inactive arrays
Date: Tue, 13 Sep 2016 09:04:59 -0600	[thread overview]
Message-ID: <CAJCQCtSL4N6dtMOJVFHocVD3QKCvFmejgt-973M0jjcHMvo-Mg@mail.gmail.com> (raw)
In-Reply-To: <CAHscji2pAt1_yPpXj6gKE-sin0Db3RAo56srM8cye5ub4rSLXg@mail.gmail.com>

On Tue, Sep 13, 2016 at 12:51 AM, Daniel Sanabria <sanabria.d@gmail.com> wrote:
>> What version of parted?
>
> parted (GNU parted) 3.2

That should reliably fix the GPT, assuming it's appropriate to fix it
- which isn't necessarily a good assumption. The backup GPT is located
in about the same place as the mdadm v2 metadata. So one can step on
the other, depending on how the array is created (on whole devices or
on partitions). The problem with unwinding this is if any of these
structures becomes stale without having the signature wiped, it
becomes important to find out for certain which one is valid and which
one is stale.

>
>> Are these two drives on the same
>> controller?
>
> yes afaict

I'd check all the cables (the connections in particular) drive to
controller and that the controller is seated. Seems sorta unlikely
you'd have the same kind of problem on two drives at the same time
that's a hardware problem unless they share something the other drives
don't; or if some event has modified both drives the same way. Thing
is, invalid argument during seek for read? Kinda sounds like a
hardware problem.

-- 
Chris Murphy

  reply	other threads:[~2016-09-13 15:04 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-02  7:36 Inactive arrays Daniel Sanabria
2016-08-02 10:17 ` Wols Lists
2016-08-02 10:45   ` Daniel Sanabria
2016-08-03 19:18     ` Daniel Sanabria
2016-08-03 21:31       ` Wols Lists
2016-09-11 18:48     ` Daniel Sanabria
2016-09-11 20:06       ` Daniel Sanabria
2016-09-12 19:41         ` Daniel Sanabria
2016-09-12 21:13           ` Daniel Sanabria
2016-09-12 21:37             ` Chris Murphy
2016-09-13  6:51               ` Daniel Sanabria
2016-09-13 15:04                 ` Chris Murphy [this message]
2016-09-12 21:39             ` Wols Lists
2016-09-13  6:56               ` Daniel Sanabria
2016-09-13  7:02                 ` Adam Goryachev
2016-09-13 15:20                 ` Chris Murphy
2016-09-13 19:43                   ` Daniel Sanabria
2016-09-13 19:52                     ` Chris Murphy
2016-09-13 20:04                       ` Daniel Sanabria
2016-09-13 20:13                         ` Chris Murphy
2016-09-13 20:29                           ` Daniel Sanabria
2016-09-13 20:36                           ` Daniel Sanabria
2016-09-13 21:10                             ` Chris Murphy
2016-09-13 21:46                               ` Daniel Sanabria
2016-09-13 21:26                             ` Wols Lists
2016-09-14  4:33                         ` Chris Murphy
2016-09-14 10:36                           ` Daniel Sanabria
2016-09-14 14:32                             ` Chris Murphy
2016-09-14 14:57                               ` Daniel Sanabria
2016-09-14 15:15                                 ` Chris Murphy
2016-09-14 15:47                                   ` Daniel Sanabria
2016-09-14 16:10                                     ` Chris Murphy
2016-09-14 16:13                                       ` Chris Murphy
2016-09-14 18:16                                         ` Daniel Sanabria
2016-09-14 18:37                                           ` Chris Murphy
2016-09-14 18:42                                           ` Wols Lists
2016-09-15  9:21                                             ` Brad Campbell

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=CAJCQCtSL4N6dtMOJVFHocVD3QKCvFmejgt-973M0jjcHMvo-Mg@mail.gmail.com \
    --to=lists@colorremedies.com \
    --cc=antlists@youngman.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=sanabria.d@gmail.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).