From: Robin Hill <robin@robinhill.me.uk>
To: Gimpbully <gimpbully@gmail.com>
Cc: Phil Turmel <philip@turmel.org>, Sam Bingner <sam@bingner.com>,
"<linux-raid@vger.kernel.org>" <linux-raid@vger.kernel.org>
Subject: Re: array went wonky
Date: Fri, 3 May 2013 08:40:07 +0100 [thread overview]
Message-ID: <20130503074007.GA27548@cthulhu.home.robinhill.me.uk> (raw)
In-Reply-To: <724CACBC-1D7E-4EE0-91FE-97D5ADC0CD59@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2791 bytes --]
On Thu May 02, 2013 at 07:29:38AM -0700, Gimpbully wrote:
> Sorry, I realize I had md127 started. So I stopped it and did the
> assemble and got the following (the problem is sdf isn't supposed to
> be a spare at all, it's supposed to be a ddrescue'd sdc:
>
> eduardo ~ # mdadm --stop /dev/md127
> mdadm: stopped /dev/md127
> eduardo ~ # mdadm --assemble --force /dev/md127 /dev/sd{f,g,e,a}1
> mdadm: /dev/md127 assembled from 3 drives and 1 spare - not enough to start the array.
> eduardo ~ #
>
>
> eduardo ~ # mdadm --examine /dev/sd{f,g,e,a}1 | egrep 'Event|/dev/sd'
> /dev/sdf1:
> Events : 25979
> this 5 8 81 5 spare /dev/sdf1
> 0 0 8 33 0 active sync /dev/sdc1
> 2 2 8 65 2 active sync /dev/sde1
> 4 4 8 1 4 active sync /dev/sda1
> 5 5 8 81 5 spare /dev/sdf1
> /dev/sdg1:
> Events : 25979
> this 1 8 17 1 active sync /dev/sdb1
> 0 0 8 33 0 active sync /dev/sdc1
> 1 1 8 17 1 active sync /dev/sdb1
> 2 2 8 65 2 active sync /dev/sde1
> 4 4 8 1 4 active sync /dev/sda1
> 5 5 8 81 5 spare /dev/sdf1
> /dev/sde1:
> Events : 25979
> this 2 8 65 2 active sync /dev/sde1
> 0 0 8 33 0 active sync /dev/sdc1
> 2 2 8 65 2 active sync /dev/sde1
> 4 4 8 1 4 active sync /dev/sda1
> 5 5 8 81 5 spare /dev/sdf1
> /dev/sda1:
> Events : 25979
> this 4 8 1 4 active sync /dev/sda1
> 0 0 8 33 0 active sync /dev/sdc1
> 2 2 8 65 2 active sync /dev/sde1
> 4 4 8 1 4 active sync /dev/sda1
> 5 5 8 81 5 spare /dev/sdf1
>
Okay, so we have:
sda - original disk
sde - original disk
sdf - supposed to be ddrescue of original sdc
sdg - ddrescue of original sdb
From the metadata, it would appear that sdf is not in fact a ddrescue of
sdc, so I'd suggest going back and redoing that. Check afterwards that
the metadata reported by "mdadm --examine" on the two disks matches.
Cheers,
Robin
--
___
( ' } | Robin Hill <robin@robinhill.me.uk> |
/ / ) | Little Jim says .... |
// !! | "He fallen in de water !!" |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2013-05-03 7:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-13 5:41 array went wonky Gimpbully
2013-04-13 14:20 ` Sam Bingner
2013-04-13 15:46 ` Robin Hill
2013-04-13 16:09 ` John White
2013-04-30 2:33 ` Gimpbully
2013-04-30 6:20 ` Sam Bingner
2013-04-30 14:45 ` Phil Turmel
2013-04-30 14:48 ` Gimpbully
2013-05-01 18:59 ` Gimpbully
2013-05-02 14:18 ` Gimpbully
2013-05-02 14:29 ` Gimpbully
2013-05-03 6:47 ` Gimpbully
2013-05-03 14:24 ` Phil Turmel
2013-05-03 7:40 ` Robin Hill [this message]
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=20130503074007.GA27548@cthulhu.home.robinhill.me.uk \
--to=robin@robinhill.me.uk \
--cc=gimpbully@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=philip@turmel.org \
--cc=sam@bingner.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).