All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Greaves <david@dgreaves.com>
To: "Jon Lurås" <jon@irisinfo.net>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Change disk problem
Date: Sun, 08 Jun 2008 12:26:45 +0100	[thread overview]
Message-ID: <484BC1F5.3000009@dgreaves.com> (raw)
In-Reply-To: <WorldClient-F200806081212.AA12040517@irisinfo.net>

Jon Lurås wrote:
> Hello 
> 
> Thank you for your input.
> 
> I gave to little information in the original mail. I had tried to 'add'
> the new disk. It shows up like this - se below. The bad thing is that then
> the device '/dev/hdj1' suddenly changes to 'spare'...
> and everything looks very bad :-(

OK, you also wrote (forgot to cc the list)
Jon Lurås wrote:
> Hi again
>
> A little more information:
> The only solution I found to the problem which arised after the 'add' og
> /dev/hdk1 is
> "mdadm --create /dev/md0 --verbose --level=5 --chunk=64 --raid-devices=3
> /dev/hdi1 /dev/hdj1 missing"
>
> The it looks like the original 'mdadm --detail /dev/md0' result.
>
> Jon

So I'm now quite confused.

Can you tell us what you did a step at a time.
This is what should have happened:

1 Original disk failed.
2 md0 went into degraded and mdadm --monitor sent you an email
3 you shutdown and replaced /dev/hdk (?)
4 you partitioned /dev/hdk to make hdk1
5 you used --add to add hdk1 to the array
6 all was well

now you seem to have done several 'interesting' things in addition (like issuing
a --create).
However, if you can go back to the original --detail given, a simple --add
should resolve your problems...

You may want to check your dmesg to make sure you don't have a hardware issue.

> demeter:/etc# mdadm --detail /dev/md0
> /dev/md0:
>         Version : 00.90.00
>   Creation Time : Sat Jun  7 22:04:01 2008
>      Raid Level : raid5
>      Array Size : 490223232 (467.51 GiB 501.99 GB)
>     Device Size : 245111616 (233.76 GiB 250.99 GB)
>    Raid Devices : 3
>   Total Devices : 4
> Preferred Minor : 0
>     Persistence : Superblock is persistent
> 
>     Update Time : Sun Jun  8 12:05:02 2008
>           State : active, degraded
>  Active Devices : 1
> Working Devices : 3
>  Failed Devices : 1
>   Spare Devices : 2
> 
>          Layout : left-symmetric
>      Chunk Size : 64K
> 
>            UUID : 7edd5dfe:14b3ffb2:304b0607:0d821dcd
>          Events : 0.8
> 
>     Number   Major   Minor   RaidDevice State
>        0      56        1        0      active sync   /dev/hdi1
>        1       0        0        1      removed
>        2       0        0        2      removed
> 
>        3      57        1        3      spare   /dev/hdk1
>        4      56       65        4      spare   /dev/hdj1

This doesn't look good.

what does --examine say about each of the components?

David
--
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

  parent reply	other threads:[~2008-06-08 11:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <S1753847AbYFHHWg/20080608072236Z+62@vger.kernel.org>
2008-06-08  7:58 ` Change disk problem Jon Lurås
2008-06-08 10:00   ` David Greaves
     [not found]     ` <WorldClient-F200806081212.AA12040517@irisinfo.net>
2008-06-08 11:26       ` David Greaves [this message]
2008-06-08 13:14         ` Jon Lurås
2008-06-08 13:20           ` Justin Piszcz

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=484BC1F5.3000009@dgreaves.com \
    --to=david@dgreaves.com \
    --cc=jon@irisinfo.net \
    --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.