From: "Daniel L. Miller" <dmiller@amfes.com>
To: linux-raid@vger.kernel.org
Subject: Re: Raid-10 mount at startup always has problem
Date: Sun, 09 Sep 2007 18:53:32 -0700 [thread overview]
Message-ID: <46E4A39C.8040509@amfes.com> (raw)
In-Reply-To: <46D49F1A.7030409@tmr.com>
Bill Davidsen wrote:
> Daniel L. Miller wrote:
>> Hi!
>>
>> I have a four-disk Raid-10 array that I created and mount with
>> mdadm. It seems like every re-boot, either the array is not
>> recognized altogether, or one of the disks is not added. Manually
>> adding using mdadm works.
>
> What superblock version and partition type did you use? mdadm -D please.
Thanks for the reply. I've been wondering why no one answered me - then
discovered your answer in my mailbox! Must have been hiding somewhere .
. . .
Anyway -
mdadm -D /dev/md0
/dev/md0:
Version : 00.90.03
Creation Time : Tue Oct 3 19:11:53 2006
Raid Level : raid10
Array Size : 312581632 (298.10 GiB 320.08 GB)
Used Dev Size : 156290816 (149.05 GiB 160.04 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Sun Sep 9 18:51:17 2007
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Layout : near=2, far=1
Chunk Size : 32K
UUID : 9d94b17b:f5fac31a:577c252b:0d4c4b2a
Events : 0.10811466
Number Major Minor RaidDevice State
0 8 0 0 active sync /dev/sda
1 8 16 1 active sync /dev/sdb
2 8 32 2 active sync /dev/sdc
3 8 48 3 active sync /dev/sdd
And you didn't ask, but my mdadm.conf:
DEVICE partitions
ARRAY /dev/.static/dev/md0 level=raid10 num-devices=4
UUID=9d94b17b:f5fac31a:577c252b:0d4c4b2a
Daniel
next prev parent reply other threads:[~2007-09-10 1:53 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 18:14 Raid-10 mount at startup always has problem Daniel L. Miller
[not found] ` <46D49F1A.7030409@tmr.com>
2007-09-10 1:53 ` Daniel L. Miller [this message]
2007-09-10 2:04 ` Richard Scobie
[not found] ` <46E4A5F0.9090407@sauce.co.nz>
2007-09-10 2:11 ` Daniel L. Miller
2007-10-24 14:22 ` Daniel L. Miller
2007-10-24 16:25 ` Doug Ledford
2007-10-24 20:01 ` Bill Davidsen
2007-10-25 5:43 ` Daniel L. Miller
2007-10-25 6:40 ` Doug Ledford
2007-10-26 9:15 ` Luca Berra
2007-10-26 16:53 ` Gabor Gombas
2007-10-27 7:57 ` Luca Berra
2007-10-26 19:26 ` Doug Ledford
2007-10-27 7:50 ` Luca Berra
2007-10-27 15:07 ` Gabor Gombas
2007-10-27 20:47 ` Doug Ledford
2007-10-28 13:37 ` Luca Berra
2007-10-28 17:55 ` Doug Ledford
2007-10-29 0:21 ` Bill Davidsen
2007-10-29 7:41 ` Luca Berra
2007-10-29 13:22 ` Bill Davidsen
2007-10-29 15:21 ` Doug Ledford
2007-10-29 15:54 ` Gabor Gombas
2007-10-29 14:31 ` Doug Ledford
2007-10-29 5:59 ` Daniel L. Miller
2007-10-29 8:18 ` Luca Berra
2007-10-29 15:47 ` Doug Ledford
2007-10-29 21:29 ` Luca Berra
2007-10-29 23:15 ` Doug Ledford
2007-10-30 0:03 ` Daniel L. Miller
2007-11-01 13:56 ` Bill Davidsen
2007-12-17 14:58 ` Daniel L. Miller
2007-10-29 17:08 ` Doug Ledford
2007-10-29 18:56 ` Richard Scobie
2007-10-25 6:12 ` Neil Brown
2007-10-25 6:51 ` Doug Ledford
2007-10-25 13:13 ` Daniel L. Miller
2007-10-25 13:33 ` Daniel L. Miller
2007-10-26 6:12 ` Neil Brown
2007-10-25 14:46 ` Bill Davidsen
2007-10-25 16:13 ` Daniel L. Miller
2007-10-26 5:59 ` 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=46E4A39C.8040509@amfes.com \
--to=dmiller@amfes.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;
as well as URLs for NNTP newsgroup(s).