From: Adam Goryachev <adam@websitemanagers.com.au>
To: Christopher Hoover <ch@murgatroid.com>, linux-raid@vger.kernel.org
Subject: Re: unable to assemble (mostly?) clean array
Date: Mon, 09 Dec 2013 11:02:37 +1100 [thread overview]
Message-ID: <52A5089D.3080109@websitemanagers.com.au> (raw)
In-Reply-To: <CACw0PsYr+u=YqXQJtUBLDzoppXPWCoRRLUqvgPLE4_L+V68iZw@mail.gmail.com>
On 09/12/13 10:32, Christopher Hoover wrote:
> hi folks,
>
> what's the safest way to get this array back into r/o mode?
>
> thanks,
> -ch
> ch@murgatroid.com
>
>
> ch@snaggle:~$ sudo mdadm --examine /dev/sd[defg]1 | egrep 'Event|^/dev/sd'
>
> /dev/sdd1:
>
> Events : 286024
>
> /dev/sde1:
>
> Events : 286011
>
> /dev/sdf1:
>
> Events : 286024
>
> /dev/sdg1:
>
> Events : 286024
>
> ch@snaggle:~$ sudo mdadm --assemble --force /dev/md0 /dev/sdd1
> /dev/sde1 /sdg1
>
> mdadm: cannot open device /sdg1: No such file or directory
>
> mdadm: /sdg1 has no superblock - assembly aborted
>
I'm no expert on this, but two questions:
Did you mean /dev/sdg1 ?
Why not use sdd1, sdf1 and sdg1 since they have the correct event counts?
Then add sde1 and allow to resync?
sudo mdadm --manage /dev/md0 --stop
sudo mdadm --assemble /dev/md0 /dev/sd[dfg]1
sudo mdadm --manage /dev/md0 --run
Try that, and provide any output
PS, it seems you would only need a minimum of 2 drives, and you have
three with matching event counts, so it should be fine.
Regards,
Adam
--
Adam Goryachev
Website Managers
P: +61 2 8304 0000 adam@websitemanagers.com.au
F: +61 2 8304 0001 www.websitemanagers.com.au
next prev parent reply other threads:[~2013-12-09 0:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-08 23:32 unable to assemble (mostly?) clean array Christopher Hoover
2013-12-08 23:55 ` NeilBrown
2013-12-09 0:02 ` Adam Goryachev [this message]
2013-12-09 0:32 ` Christopher Hoover
2013-12-09 1:02 ` NeilBrown
2013-12-09 1:08 ` Christopher Hoover
2013-12-09 1:33 ` NeilBrown
2013-12-09 3:00 ` Christopher Hoover
2013-12-09 3:41 ` NeilBrown
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=52A5089D.3080109@websitemanagers.com.au \
--to=adam@websitemanagers.com.au \
--cc=ch@murgatroid.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.