From: John Robinson <john.robinson@anonymous.org.uk>
To: Carl Engstrom <engstrom@cox.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm raid can't set proper devices in super-block
Date: Mon, 12 Mar 2012 18:33:15 +0000 [thread overview]
Message-ID: <4F5E416B.9020003@anonymous.org.uk> (raw)
In-Reply-To: <loom.20120312T183628-941@post.gmane.org>
On 12/03/2012 17:38, Carl Engstrom wrote:
> resetting mdadm superblock
>
> --------------------------------------------------------------------------------
>
> Hey folks,
>
> I'm having some issues with my md array after upgrading to 11.04.
[...]
> Number Major Minor RaidDevice State
> this 1 8 17 1 active sync /dev/sdb1
>
> 0 0 8 1 0 active sync /dev/sda1
> 1 1 8 17 1 active sync /dev/sdb1
> --------
>
> the array will start with:
> mdadm -A --update=super-minor /dev/md0 /dev/sdb1 /dev/sdc1
So it starts just fine if you specify the devices...
> Anyone know what's going on?
--update=super-minor is working fine; both devices have a preferred
minor device number of zero, as they should for the array to be /dev/md0.
What happens if you
mdadm --stop /dev/md0
mdadm --assemble --scan --verbose /dev/md0
?
Where do you want to mount /dev/md0?
What messages do you get during boot-up (dmesg) about why md0 isn't
being assembled?
What's in your /etc/mdadm.conf?
If /etc/mdadm.conf says sda1 and sdb1, fix it and do whatever you need
to do on Ubuntu to rebuild your initrd/initramfs (so that your edited
mdadm.conf goes into it), then reboot.
Hope something somewhere in amongst this lot helps...
Cheers,
John.
next prev parent reply other threads:[~2012-03-12 18:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 17:38 mdadm raid can't set proper devices in super-block Carl Engstrom
2012-03-12 18:33 ` John Robinson [this message]
2012-03-14 17:04 ` Carl Engstrom
2012-03-16 23:37 ` FW: " Carl Engstrom
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=4F5E416B.9020003@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--cc=engstrom@cox.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 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).