Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: bobzer <bobzer@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: problem with raid after reboot
Date: Mon, 10 Dec 2012 08:58:33 -0500	[thread overview]
Message-ID: <50C5EA89.40804@turmel.org> (raw)
In-Reply-To: <CADzS=aqXh08P+ujEoJPMBxPiZ-PeEdk3x3iRW1ymAvhtpZcDmA@mail.gmail.com>

Hi Mathieu,

On 12/09/2012 11:13 PM, bobzer wrote:
> hi had to reboot my raid 5 server. but now it doesnt't want to
> reassemble correctly
> 
> i have a raid 5 of 3 disk and a lvm on top of that. i know my data are
> there but i'm afraid of enter the dead command :-)
> 
> so here is the information about my raid, if someone could help or
> explain me something or just give a clue to follow.
> i remember that, this already happend to me ... exactly the same but i
> don't remember how i did (promes that this time right everything down)
> because it's already happend i'm afraid there is a bigger problem in my raid...
> 
> help me please :-)

It looks like the superblocks didn't get updated together due to your
improper reboot.  (Event counts don't match.)

I suggest you stop the array and reassemble with "--force", like so:

mdadm --stop /dev/md0
mdadm --assemble --force /dev/md0 /dev/sd[bcd]1

The "--force" option will instruct mdadm to ignore the event count mismatch.

You probably want to investigate why your array wasn't properly stopped
during shutdown.

HTH,

Phil


  reply	other threads:[~2012-12-10 13:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-10  4:13 problem with raid after reboot bobzer
2012-12-10 13:58 ` Phil Turmel [this message]
     [not found]   ` <CADzS=aq_83Nr55m+LFywx6LqHdwwkfzfBM+tPv8gcf6ono_j8g@mail.gmail.com>
2012-12-10 15:04     ` Phil Turmel

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=50C5EA89.40804@turmel.org \
    --to=philip@turmel.org \
    --cc=bobzer@gmail.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