From: "Donghui Wen" <dhwen@protegonetworks.com>
To: Michael Duggan <md5i@sei.cmu.edu>, linux-raid@vger.kernel.org
Subject: Re: RAID reconstruction problems
Date: Tue, 2 Sep 2003 11:29:16 -0700 [thread overview]
Message-ID: <003d01c37180$1db2b730$df01010a@moon> (raw)
In-Reply-To: 87wucrnb63.fsf@cs.cmu.edu
Have you partitioned the new disk before you rebuild?
Donghui
----- Original Message -----
From: "Michael Welsh Duggan" <md5i@cs.cmu.edu>
To: <linux-raid@vger.kernel.org>
Sent: Monday, September 01, 2003 8:04 PM
Subject: RAID reconstruction problems
> I currently have two small Software RAIDs, a RAID 1 for my root
> partition, and a RAID 5 for my usr partition. One of the disks in the
> arrays died, and I threw in a new disk in with the intention of
> rebuilding the arrays.
>
> The rebuilds failed, but in an extremely strange fashion. Monitoring
> /proc/mdstat, it seems that the rebuilds are going just fine. When
> they finish however, /proc/mdstat includes the new disk, but also
> declares it invalid. The system continues running in degraded mode.
>
> When I run this from the root console, I get some messages from the
> raid subsystem, including full debugging output. I have not yet
> figured out how to capture this output in order to include in this
> message, but I did write down a part of one attempt (this was by hand,
> so there may be small inconsistancies):
>
> RAID5 conf printout
> --- rd:3 wd:2 fd:1
> disk 0, s:0, o:1, n:0 rd:0 us:1 dev:ide/host0/bus0/target1/lun0/part3
> disk 1, s:0, o:0, n:0 rd:0 us:0 dev:[dev 00:00]
> disk 2, s:0, o:1, n:2 rd:2 us:1 dev:ide/host2/bus1/target0/lun0/part3
> md: bug in file raid5.c, line 1901
>
> Here is some output from my system. If any more information would be
> useful, or anyone thinks I should try something else, please let me
> know. I would like to get out of my currently degraded state!
>
>
----------------------------------------------------------------------------
----
>
> --
> Michael Welsh Duggan
> (md5i@cs.cmu.edu)
>
-
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
Have you partitioned the new disk before you rebuild?
Donghui
----- Original Message -----
From: "Michael Welsh Duggan" <md5i@cs.cmu.edu>
To: <linux-raid@vger.kernel.org>
Sent: Monday, September 01, 2003 8:04 PM
Subject: RAID reconstruction problems
> I currently have two small Software RAIDs, a RAID 1 for my root
> partition, and a RAID 5 for my usr partition. One of the disks in the
> arrays died, and I threw in a new disk in with the intention of
> rebuilding the arrays.
>
> The rebuilds failed, but in an extremely strange fashion. Monitoring
> /proc/mdstat, it seems that the rebuilds are going just fine. When
> they finish however, /proc/mdstat includes the new disk, but also
> declares it invalid. The system continues running in degraded mode.
>
> When I run this from the root console, I get some messages from the
> raid subsystem, including full debugging output. I have not yet
> figured out how to capture this output in order to include in this
> message, but I did write down a part of one attempt (this was by hand,
> so there may be small inconsistancies):
>
> RAID5 conf printout
> --- rd:3 wd:2 fd:1
> disk 0, s:0, o:1, n:0 rd:0 us:1 dev:ide/host0/bus0/target1/lun0/part3
> disk 1, s:0, o:0, n:0 rd:0 us:0 dev:[dev 00:00]
> disk 2, s:0, o:1, n:2 rd:2 us:1 dev:ide/host2/bus1/target0/lun0/part3
> md: bug in file raid5.c, line 1901
>
> Here is some output from my system. If any more information would be
> useful, or anyone thinks I should try something else, please let me
> know. I would like to get out of my currently degraded state!
>
>
----------------------------------------------------------------------------
----
>
> --
> Michael Welsh Duggan
> (md5i@cs.cmu.edu)
>
next prev parent reply other threads:[~2003-09-02 18:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-02 3:04 RAID reconstruction problems Michael Welsh Duggan
2003-09-02 16:04 ` Bernd Schubert
2003-09-02 18:29 ` Donghui Wen [this message]
2003-09-03 1:51 ` Michael Welsh Duggan
2003-09-04 17:07 ` Bernd Schubert
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='003d01c37180$1db2b730$df01010a@moon' \
--to=dhwen@protegonetworks.com \
--cc=linux-raid@vger.kernel.org \
--cc=md5i@sei.cmu.edu \
/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).