linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robin Hill <robin@robinhill.me.uk>
To: linux-raid@vger.kernel.org
Subject: Re: recovering a mirrored arry.
Date: Fri, 5 Feb 2010 22:42:25 +0000	[thread overview]
Message-ID: <20100205224225.GA8099@cthulhu.home.robinhill.me.uk> (raw)
In-Reply-To: <20100205185043.GA6956@light.rap.dk>

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

On Fri Feb 05, 2010 at 07:50:44PM +0100, Keld Simonsen wrote:

> On Fri, Feb 05, 2010 at 04:25:02PM +0000, Kristleifur Daðason wrote:
> > On Fri, Feb 5, 2010 at 1:19 AM, Keld Simonsen <keld@keldix.com> wrote:
> > > On Wed, Feb 03, 2010 at 03:57:58AM +0100, Keld Simonsen wrote:
> > > Hi
> > >
> > >
> > > can anybody help me with this? I am stuck with recovering my system here.
> > > is it a sensible thing ro do?
> > >
> > > best regards
> > > keld
> > >
> > >> Hi
> > >>
> > >> I got 2 arrays in error of the raid10 type.
> > >>
> > >> I think this is because my motherboard died, and then the fs were
> > >> corrupted.
> > >>
> > >> My thoughts were that actually one of the copies could be correct.
> > >> So I would like to try out the consistency of each part of the raid10
> > >> (it is 2-partition arrays), and then if I find one that is consistent, then
> > >> resync the faulty one with the good one.
> > >>
> > >> How do I do this?
> > >>
> > >> it seems that I cannot just assemble an array with a missing part.
> > >> If I assemble the full array, is there then a risk of the bad one
> > >> corrupting the good one? And can I declare one of the disks faulty
> > >> then test the other one, then declare nbr 2 disk for faulty and
> > >> declare the first one as good?
> > >>
> > >> I dont see anything on the wiki on this.
> > >>
> > >> best regards
> > >> keld
> > > --
> > > To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> > > the body of a message to majordomo@vger.kernel.org
> > > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > >
> > 
> > 
> > I wish I could help more, but check out this from the mdadm man page:
> > 
> >        To create a "degraded" array in which some devices are missing,
> > simply give
> >        the word "missing" in place of a device name.  This  will
> > cause  mdadm  to
> >        leave  the  corresponding  slot  in  the array empty.  For a
> > RAID4 or RAID5
> >        array at most one slot can be "missing"; for a  RAID6  array
> > at  most  two
> >        slots.   For a RAID1 array, only one real device needs to be
> > given.  All of
> >        the others can be "missing".
> 
> I tried missing, but mdadm said that it could not find missing as a device,
> for assemble mode.
> 
No, as the manual page says, "missing" is only used for creating an
array, not for assembling.

If you only give a single device in the assemble command then mdadm
_ought_ to only use that to assemble the array.  I'm not 100% sure that
it does it though - probably worth testing with loopback devices first.

The other option would be to use "create" to create new degraded arrays
containing only the single disks.  You'd need to make sure you used the
same settings as for the old array though.

Alternately, physically disconnect the drives in turn and assemble the
array with the single drive.

Cheers,
    Robin
-- 
     ___        
    ( ' }     |       Robin Hill        <robin@robinhill.me.uk> |
   / / )      | Little Jim says ....                            |
  // !!       |      "He fallen in de water !!"                 |

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2010-02-05 22:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-03  2:57 recovering a mirrored arry Keld Simonsen
2010-02-05  1:19 ` Keld Simonsen
2010-02-05 16:25   ` Kristleifur Daðason
2010-02-05 18:50     ` Keld Simonsen
2010-02-05 22:06       ` Kristleifur Daðason
2010-02-05 22:38         ` Keld Simonsen
2010-02-05 22:40           ` Kristleifur Daðason
2010-02-05 22:40       ` Guy Watkins
2010-02-05 22:42       ` Robin Hill [this message]
2010-02-09 11:52         ` Keld Simonsen

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=20100205224225.GA8099@cthulhu.home.robinhill.me.uk \
    --to=robin@robinhill.me.uk \
    --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).