From: Paul Waldo <pwaldo@waldoware.com>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Can't add disk to failed raid array
Date: Sun, 16 Jul 2006 08:24:02 -0400 [thread overview]
Message-ID: <200607160824.04175.pwaldo@waldoware.com> (raw)
In-Reply-To: <17594.4774.17991.656057@cse.unsw.edu.au>
Thanks for the reply, Neil. Here is my version:
[root@paul log]# mdadm --version
mdadm - v2.3.1 - 6 February 2006
This is a somewhat production system, running Fedora Core 5. Official
packages containing mdadm at version 2.5.2 aren't available (to my
knowledge), and I am very hesitant to experiment with non-official
software :-(
Would "mdadm --assemble" be of use to me here? From the message "md: hdd2 has
invalid sb, not importing!", it seems I need to get an "sb" (assumed to be
super block) on that partition. Would --assemble work and not destroy the
existing good array?
As another data point, when I replaced the bad disk, I was able to
add /dev/hdd1 to /dev/md0 with no problem. md0 is a RAID 1 array and hdd1
was a spare, so there may be no relation at all...
Thanks for your help!
On Sunday 16 July 2006 6:19 am, Neil Brown wrote:
> On Saturday July 15, pwaldo@waldoware.com wrote:
> > Hi all,
> >
> > I have a RAID6 array where a disk went bad. I removed the old disk, put
> > in an identical one, and repartitioned the new disk. I am now trying to
> > add the new partition to the array, but I get this error:
> >
> > [root@paul ~]# mdadm --add /dev/md1 /dev/hdd2
> > mdadm: add new device failed for /dev/hdd2 as 2: Invalid argument
> >
> > When I perform that command, /var/log/messages says this:
> > Jul 15 20:48:39 paul kernel: md: hdd2 has invalid sb, not importing!
> > Jul 15 20:48:39 paul kernel: md: md_import_device returned -22
>
> Rings a bell, but I cannot quite place it..
>
> What version of mdadm are you running? If not 2.5.2, try that.
>
> ...
>
> > Number Major Minor RaidDevice State
> > 0 3 2 0 active sync /dev/hda2
> > 1 22 2 1 active sync /dev/hdc2
> > 3157553 0 0 5 removed
>
> ^^^^^^^
> That looks very odd. If 2.5.2 does that I'll have to look into why.
>
> NeilBrown
>
> > 3 33 2 3 active sync /dev/hde2
> > 4 34 2 4 active sync /dev/hdg2
> > 5 8 2 5 active sync /dev/sda2
> > 6 8 18 6 active sync /dev/sdb2
> >
> > [root@paul log]# uname -rv
> > 2.6.17-1.2139_FC5 #1 Fri Jun 23 12:40:16 EDT 2006
> > -
> > 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
>
> -
> 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
next prev parent reply other threads:[~2006-07-16 12:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-16 0:56 Can't add disk to failed raid array Paul Waldo
2006-07-16 10:19 ` Neil Brown
2006-07-16 12:24 ` Paul Waldo [this message]
2006-07-18 5:36 ` Neil Brown
2006-07-23 11:04 ` In Trouble--Please Help! (was Re: Can't add disk to failed raid array) Paul Waldo
2006-07-23 11:25 ` Neil Brown
2006-07-23 11:50 ` Paul Waldo
2006-07-23 11:53 ` Paul Waldo
2006-07-23 11:59 ` Neil Brown
2006-07-23 12:32 ` Paul Waldo
2006-07-24 18:26 ` Dan Williams
2006-07-24 18:35 ` Paul Waldo
2006-07-24 19:06 ` Dan Williams
2006-07-25 14:27 ` Paul Waldo
2006-07-24 23:24 ` Neil Brown
2006-08-02 19:15 ` Converting Ext3 to Ext3 under RAID 1 Dan Graham
2006-08-02 19:28 ` dean gaudet
2006-08-02 19:31 ` Paul Clements
2006-08-03 7:50 ` Michael Tokarev
2006-08-02 22:38 ` Robert Heinzmann
[not found] ` <200607160913.32005.pwaldo@waldoware.com>
[not found] ` <Pine.LNX.4.62.0607161524170.7520@uplift.swm.pp.se>
2006-07-16 14:39 ` Can't add disk to failed raid array Paul Waldo
2006-07-17 18:36 ` Paul Waldo
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=200607160824.04175.pwaldo@waldoware.com \
--to=pwaldo@waldoware.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).