From: Stefan Priebe <s.priebe@profihost.ag>
To: Jes Sorensen <Jes.Sorensen@redhat.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: imsm raid is always readonly on boot
Date: Tue, 07 Feb 2012 18:42:11 +0100 [thread overview]
Message-ID: <4F316273.7030109@profihost.ag> (raw)
In-Reply-To: <4F314CBC.8010102@redhat.com>
Hi Jes,
Am 07.02.2012 17:09, schrieb Jes Sorensen:
> /dev/md126 looks to be the container, not the actual raid device, from
> what your mdadm.conf says.
booted from a rescue CD using 2.6.32 kernel.
~# mdadm -D --scan
ARRAY /dev/md/imsm0 metadata=imsm UUID=24cdb70d:101f4c4b:23dfa5cb:3f176b6a
ARRAY /dev/md/RaidStefan_0 container=/dev/md/imsm0 member=0
UUID=84aa9982:ed593d80:ee7c7f53:e2944038
~# cat /proc/mdstat
Personalities : [raid1]
md126 : active (auto-read-only) raid1 sda[1] sdb[0]
156288000 blocks super external:/md127/0 [2/2] [UU]
md127 : inactive sdb[1](S) sda[0](S)
5544 blocks super external:imsm
unused devices: <none>
so md126 is the real raid.
> What does your /proc/mdstat say?
When booted from disk - output while in initramfs:
~# cat /proc/mdstat
Personalities : [raid1]
md126 : active (read-only) raid1 sda[1] sdb[0]
156288000 blocks super external:/md127/0 [2/2] [UU]
md127 : inactive sdb[1](S) sda[0](S)
5544 blocks super external:imsm
unused devices: <none>
Stefan
next prev parent reply other threads:[~2012-02-07 17:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 11:58 imsm raid is always readonly on boot Stefan Priebe - Profihost AG
2012-02-07 16:09 ` Jes Sorensen
2012-02-07 17:42 ` Stefan Priebe [this message]
2012-02-07 17:45 ` Jes Sorensen
2012-02-07 18:24 ` Stefan Priebe
2012-02-07 20:24 ` Jes Sorensen
2012-02-07 21:47 ` John Robinson
2012-02-08 1:57 ` NeilBrown
2012-02-08 8:30 ` Stefan Priebe - Profihost AG
2012-02-08 8:45 ` NeilBrown
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=4F316273.7030109@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=Jes.Sorensen@redhat.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).