From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: linux-raid@vger.kernel.org
Subject: Re: imsm raid is always readonly on boot
Date: Tue, 07 Feb 2012 17:09:32 +0100 [thread overview]
Message-ID: <4F314CBC.8010102@redhat.com> (raw)
In-Reply-To: <4F3111D9.2060303@profihost.ag>
On 02/07/12 12:58, Stefan Priebe - Profihost AG wrote:
> Hi,
>
> i'm running 3.0.18 as kernel (renamed to 2.6.40) and mdadm 3.2.2.
>
> I'm trying to get an intel fake raid running but it is always set to
> readonly on boot after running
> mdadm --assemble --scan --run --force --auto=yes
>
> But i've absolutely no idea why.
>
> My mdadm.conf:
> # by default (built-in), scan all partitions (/proc/partitions) and all
> # containers for MD superblocks. alternatively, specify devices to scan,
> using
> # wildcards if desired.
> #DEVICE partitions containers
>
> # auto-create devices with Debian standard permissions
> CREATE owner=root group=disk mode=0660 auto=yes
>
> # automatically tag new arrays as belonging to the local system
> HOMEHOST <ignore>
>
> # instruct the monitoring daemon where to send mail alerts
> MAILADDR root
>
> # definitions of existing MD arrays
> ARRAY metadata=imsm UUID=24cdb70d:101f4c4b:23dfa5cb:3f176b6a
> ARRAY /dev/md126 container=24cdb70d:101f4c4b:23dfa5cb:3f176b6a member=0
> UUID=84aa9982:ed593d80:ee7c7f53:e2944038
>
>
> ~# cat /sys/block/md126/md/array_state
> readonly
>
> What's wrong? Thanks!
/dev/md126 looks to be the container, not the actual raid device, from
what your mdadm.conf says.
What does your /proc/mdstat say?
Cheers,
Jes
next prev parent reply other threads:[~2012-02-07 16:09 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 [this message]
2012-02-07 17:42 ` Stefan Priebe
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=4F314CBC.8010102@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=s.priebe@profihost.ag \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.