From: Adam Goryachev <mailinglists@websitemanagers.com.au>
To: Jivko Sabev <jsabev@nicmus.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Cannot auto assemble a raid1 array on boot
Date: Fri, 19 Oct 2012 10:11:44 +1100 [thread overview]
Message-ID: <50808CB0.8020902@websitemanagers.com.au> (raw)
In-Reply-To: <CAG9W8wCH9bfHou72_+t+JoCS3EA96opcpTOTzkc2E0oFkbX8zg@mail.gmail.com>
On 19/10/12 02:19, Jivko Sabev wrote:
> Hi,
>
> The mdadm.conf in the initrd image contains the correct devices. I.e.
> the contents of mdadm.conf in initrd are the output of
>
> mdadm --detail --scan
>
> ARRAY /dev/md0 metadata=1.2 name=mercury:0
> UUID=60ea870e:029dcf99:eaae356e:f1c12085
> ARRAY /dev/md1 metadata=1.2 name=mercury:1
> UUID=d89a52ed:0247f2e8:5edf5d09:21e7fa48
>
> Here are the contents of /proc/mdstat from the initrd shell before
> reassembling the array.
>
> md1 : inactive sde1[2](S)
> 976639672 blocks super 1.2
>
> md0 : active linear sdb1[0] sdc1[1]
> 976770537 blocks super 1.2 0k rounding
>
> unused devices: <none>
>
> It just seems to me that it is not possible to mix md devices and sata
> devices for new arrays.
I know it is possible because I have done this before ...
Try adding the device names to the mdadm.conf....
An alternative would be to create a partition table on /dev/md0 of type
fd, this way it should be handled properly by the rest of the MD auto
assemble code.
The other option might be to use a different superblock version between
the two arrays...
Other than that, I'm not too sure, maybe someone else could comment?
Perhaps you could provide the logs generated during bootup in relation
to the MD discovery etc
Regards,
Adam
--
Adam Goryachev
Website Managers
www.websitemanagers.com.au
next prev parent reply other threads:[~2012-10-18 23:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 2:35 Cannot auto assemble a raid1 array on boot Jivko Sabev
2012-10-18 3:14 ` Adam Goryachev
2012-10-18 15:19 ` Jivko Sabev
2012-10-18 23:11 ` Adam Goryachev [this message]
2012-10-23 15:43 ` Jivko Sabev
2012-10-23 22:18 ` Adam Goryachev
2012-10-24 1:33 ` NeilBrown
2012-10-25 14:37 ` Jivko Sabev
2012-10-23 18:44 ` John Robinson
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=50808CB0.8020902@websitemanagers.com.au \
--to=mailinglists@websitemanagers.com.au \
--cc=jsabev@nicmus.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).