From: NeilBrown <neilb@suse.de>
To: Hans Malissa <hmalissa@me.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID1 working correctly, error messages during boot
Date: Thu, 21 May 2015 21:20:49 +1000 [thread overview]
Message-ID: <20150521212049.6f9cf650@notabene.brown> (raw)
In-Reply-To: <CE885044-F8E8-4286-9CAC-1D17560F1E79@me.com>
[-- Attachment #1: Type: text/plain, Size: 2348 bytes --]
On Mon, 18 May 2015 14:29:23 -0600 Hans Malissa <hmalissa@me.com> wrote:
> I have a software-RAID1 that seems to be working correctly:
>
> # cat /proc/mdstat
> Personalities : [raid1]
> md0 : active raid1 sdc1[1] sdb1[0]
> 976629568 blocks super 1.2 [2/2] [UU]
>
> unused devices: <none>
>
> # mdadm --detail /dev/md0
> /dev/md0:
> Version : 1.2
> Creation Time : Sun May 17 15:21:30 2015
> Raid Level : raid1
> Array Size : 976629568 (931.39 GiB 1000.07 GB)
> Used Dev Size : 976629568 (931.39 GiB 1000.07 GB)
> Raid Devices : 2
> Total Devices : 2
> Persistence : Superblock is persistent
>
> Update Time : Mon May 18 10:28:36 2015
> State : clean
> Active Devices : 2
> Working Devices : 2
> Failed Devices : 0
> Spare Devices : 0
>
> Name : eprb21:0 (local to host eprb21)
> UUID : 0901fe50:444a29b6:d3caff14:e45ef9cc
> Events : 19
>
> Number Major Minor RaidDevice State
> 0 8 17 0 active sync /dev/sdb1
> 1 8 33 1 active sync /dev/sdc1
>
> But, on the other hand, when the system boots, I briefly see the following messages:
>
> doing fast boot
> Creating device nodes with udev
> udevd[174]: failed to execute ‘/sbin/mdadm’ ‘/sbin/mdadm --incremental /dev/sdb1
>
> udevd[175]: failed to execute ‘/sbin/mdadm’ ‘/sbin/mdadm --incremental /dev/sdc1 --offroot’: No such file or directory
>
> But otherwise the system appears to run normally. After booting, /dev/md0 seems to be working correctly.
> What does it mean, and should I worry about it? What can I do about it? My system is openSUSE 12.2.
> Thanks a lot,
>
I suspect that some udev scripts on the initrd say to run mdadm, but mdadm
isn't installed on the initrd.
/dev/md0 doesn't hold the root filesystem does it? mdadm is only installed
on the initrd if it is needed for root, swap, or suspend-to-disk.
If you really wanted to get rid of the messages - which are definitely
harmless - you would need to recreate the initrd either without those udev
rules files, or with mdadm.
Adding the 'md' arg to the "mkinitrd" command might be sufficient, but I
don't have a 12.2 install lying around that I can play with.
NeilBrown
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
next prev parent reply other threads:[~2015-05-21 11:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 20:29 RAID1 working correctly, error messages during boot Hans Malissa
2015-05-21 11:20 ` NeilBrown [this message]
2015-05-21 11:24 ` 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=20150521212049.6f9cf650@notabene.brown \
--to=neilb@suse.de \
--cc=hmalissa@me.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).