All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Greaves <david@dgreaves.com>
To: John Hendrikx <hjohn@xs4all.nl>
Cc: linux-raid@vger.kernel.org
Subject: Re: Degraded array on every reboot
Date: Fri, 22 Jun 2007 14:15:52 +0100	[thread overview]
Message-ID: <467BCB88.9000603@dgreaves.com> (raw)
In-Reply-To: <4755.10.3.3.3.1182516663.squirrel@swilver.dyndns.org>

John Hendrikx wrote:
> I'm not sure why this keeps going wrong, but I do know I made a mistake
> when initially reconstructing the array.  What I did was the following:
> 
> # mdadm /dev/md1 --add /dev/hde
> 
> Releazing that I didn't want to add the complete drive (/dev/hde) but only
> one of its partitions (/dev/hde1) I then did (while it was still
> rebuilding):
> 
> # mdadm /dev/md1 --fail /dev/hde
> # mdadm /dev/md1 --remove /dev/hde

I'm not 100% sure but it *may* have rebuilt the superblock.

do:
  mdadm --examine /dev/hde
  mdadm --examine /dev/hde1

If hde has a superblock then that could be picked up before the hde1 one.

(ah, read more of your email and you were on the right tracks :) )

To fix this do:
  mdadm --zero-superblock /dev/hde

Once all this is done you may want to run a check on the array.

There's probably other stuff going on with partition table caches too - blockdev 
-rereadpt may make a difference... but I suspect the --zero-superblock will just 
fix it all on the next boot.

David

  reply	other threads:[~2007-06-22 13:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-22 12:51 Degraded array on every reboot John Hendrikx
2007-06-22 13:15 ` David Greaves [this message]
2007-06-22 22:49 ` Neil Brown

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=467BCB88.9000603@dgreaves.com \
    --to=david@dgreaves.com \
    --cc=hjohn@xs4all.nl \
    --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.