linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Christopher Hoover <ch@murgatroid.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: unable to assemble (mostly?) clean array
Date: Mon, 9 Dec 2013 10:55:07 +1100	[thread overview]
Message-ID: <20131209105507.0273bf9e@notabene.brown> (raw)
In-Reply-To: <CACw0PsYr+u=YqXQJtUBLDzoppXPWCoRRLUqvgPLE4_L+V68iZw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 889 bytes --]

On Sun, 8 Dec 2013 15:32:42 -0800 Christopher Hoover <ch@murgatroid.com>
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

You missed a "/dev" there!

Did you try just giving all the devices to mdadm and letting it pick the best?

 mdadm --assemble --force /dev/md0 /dev/sd[defg]1

?

NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2013-12-08 23:55 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 [this message]
2013-12-09  0:02 ` Adam Goryachev
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=20131209105507.0273bf9e@notabene.brown \
    --to=neilb@suse.de \
    --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 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).