linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: Daniel Sanabria <sanabria.d@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Inactive arrays
Date: Mon, 12 Sep 2016 22:39:30 +0100	[thread overview]
Message-ID: <57D72092.20704@youngman.org.uk> (raw)
In-Reply-To: <CAHscji2k9FyrOs+96XQWEUWU3W0EWxkanaHakjsGhij0hXiVGw@mail.gmail.com>

On 12/09/16 22:13, Daniel Sanabria wrote:
> apologies for the verbosity just adding some more info which is now
> making me lose hope. Using parted -l instead of fdisk gives me this:

Hmmm...

I'd wait and let some of the experts in disk recovery chime in before it
gets that far. The fact that fdisk found the partitions on sdc and sde
is a hopeful sign. And providing something hasn't scribbled all over the
disk, several of them know their way around partition tables and can
recreate them if they're not totally scrambled.

I think using fdisk on the drives was a mistake, but seeing as -l
doesn't write anything it was a harmless mistake. iirc fdisk can't
handle gpt disks, or stuff over 2TB, so that's where that problem lay.
Try using gdisk instead of parted, that might behave just that little
bit differently, and so long as it doesn't write anything, it won't do
any harm.

What does smartctl report on sdc and sde (I think you want smartctl -x,
the extended "display everything" command)?

And looking at the lsdrv stuff, were you using LVM? That's got a load of
references to LV. The snag is, I'm now getting a bit out of my depth - I
tend to "first respond" and ask for the information that I know the
experts will want. If Phil or someone else now takes a look at this
thread it'll contain all the information they need, but I think we need
to wait for them to chime in now. So hopefully they'll see this tonight
and be on hand soon... I'll come back if I think of anything new ...

Cheers,
Wol

  parent reply	other threads:[~2016-09-12 21:39 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
2016-09-12 21:39             ` Wols Lists [this message]
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=57D72092.20704@youngman.org.uk \
    --to=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).