From: NeilBrown <neilb@suse.de>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: Roman Mamedov <rm@romanrm.ru>,
linux-raid <linux-raid@vger.kernel.org>,
Alexander Zvyagin <zvyagin.alexander@gmail.com>
Subject: Re: RAID50 boot problems
Date: Wed, 24 Apr 2013 22:12:19 +1000 [thread overview]
Message-ID: <20130424221219.5fa086e3@notabene.brown> (raw)
In-Reply-To: <1164635.0.1366802387038.JavaMail.root@zimbra>
[-- Attachment #1: Type: text/plain, Size: 1670 bytes --]
On Wed, 24 Apr 2013 13:19:47 +0200 (CEST) Roy Sigurd Karlsbakk
<roy@karlsbakk.net> wrote:
> > > > /lib/udev/rules.d/64-md-raid.rules is here
> > > > http://paste.ubuntu.com/5592227/
> > >
> > > Bug tested positive also on Ubuntu Precise (12.04) and reported to
> > > https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1171945
> >
> > This will run "mdadm --incremental $tempnode" on any device for which
> > ID_FS_TYPE is set to "linux_raid_member", which certainly seems
> > reasonable.
> >
> > What does:
> > udevadm info --query=property --path=/dev/mdXXX | grep ID_FS_TYPE
> >
> > report for the raid5 arrays?
>
> root@raidtest:~# udevadm info --query=property --path=/dev/md0
> device path not found
> root@raidtest:~# udevadm info --query=property --path=/dev/md1
> device path not found
Sorry, that should be --name, not --path.
>
> > Looking bug report I see that md0 and md1 have
> > ID_FS_TYPE=linux_raid_member
> >
> > So that should be working.
> >
> > The fact that rootdelay=10 makes a difference suggests that it is
> > successfully assembling the raid0, but just taking a bit too long.
> > Maybe the script in the initrd needs "udevadm settle" just before it
> > attempts
> > to mount.
> >
> > Can you look inside the initrd and see if "udevadm settle" is used
> > anywhere?
>
> mdadm settle doesn't seem to be used there. I really don't know my way around the bootup scripts that well, so I'm unsure where to add it…
Can you put your initrd (or initramfs or whatever Ubuntu calls it) somewhere
that I can down load it? Or just email it to me, it's probably only about
10Meg.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-04-24 12:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGqvA+t8Nr7D6h35ZKVi5Wa0tF46TQHK_Af_mXO2=ByRjWRQag@mail.gmail.com>
2013-04-17 18:45 ` RAID50 boot problems Alexander Zvyagin
[not found] ` <CAGA4a+GQp1RV_1pA6PBP=dbXV3MHhU74=Mo24xqqjKfWfoWXJA@mail.gmail.com>
2013-04-19 9:40 ` Alexander Zvyagin
2013-04-19 10:35 ` Roy Sigurd Karlsbakk
2013-04-19 10:42 ` Tommy Apel
2013-04-19 10:51 ` Roy Sigurd Karlsbakk
2013-04-19 11:38 ` Alexander Zvyagin
2013-04-19 10:45 ` Roy Sigurd Karlsbakk
2013-04-19 11:45 ` Roman Mamedov
2013-04-19 15:58 ` Roy Sigurd Karlsbakk
2013-04-21 22:10 ` NeilBrown
2013-04-22 11:02 ` Roy Sigurd Karlsbakk
2013-04-23 17:34 ` Roy Sigurd Karlsbakk
2013-04-24 6:52 ` NeilBrown
2013-04-24 11:19 ` Roy Sigurd Karlsbakk
2013-04-24 12:12 ` NeilBrown [this message]
2013-04-24 12:29 ` Roy Sigurd Karlsbakk
2013-04-24 20:01 ` Roy Sigurd Karlsbakk
2013-04-24 23:35 ` NeilBrown
2013-04-24 22:44 ` Dmitrijs Ledkovs
2013-04-24 23:44 ` NeilBrown
2013-04-26 19:10 ` Roy Sigurd Karlsbakk
2013-04-26 19:24 ` Dmitrijs Ledkovs
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=20130424221219.5fa086e3@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=rm@romanrm.ru \
--cc=roy@karlsbakk.net \
--cc=zvyagin.alexander@gmail.com \
/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