From: Allin Cottrell <cottrell@wfu.edu>
To: linux-hotplug@vger.kernel.org
Subject: Re: systemd 183, boot problem
Date: Sun, 27 May 2012 21:04:03 +0000 [thread overview]
Message-ID: <alpine.LFD.2.01.1205271652240.9130@myrtle> (raw)
In-Reply-To: <alpine.LNX.2.01.1205271449490.4860@waverley.dhcp.wfu.edu>
On Sun, 27 May 2012, Kay Sievers wrote:
> On Sun, May 27, 2012 at 9:01 PM, Allin Cottrell <cottrell@wfu.edu> wrote:
>> I just tried updating from systemd 44 + udev 182. On booting I saw:
>>
>> "Could not find module by name='<binary-garbage>'"
>> (That is, no readable module name)
>>
>> "Failed to insert ipv6"
>>
>> "Cannot create mount unit for API file system /sys/kernel/security.
>> Refusing."
>>
>> I was then dumped into emergency mode. Grubbing through the source I saw
>> that /sys/kernel/security is needed by IMA, so I reconfigured systemd-183
>> with --disable-ima, rebuilt, reinstalled and rebooted. That didn't help; I
>> landed in emergency mode again. So I ended up reinstalling 44 + 182;
>> fortunately that gave me back a usable system.
>>
>> I think the new securityfs requirement ought to be mentioned in NEWS, and
>> made conditional on enabling IMA.
>
> I don't have securityfs enabled in the kernel and it works fine here.
Before seeing your mail I tried commenting out the securityfs
requirement in the source, rebuilding and rebooting. That didn't fix
the issue (still got emergency mode) so, yes, absence of securityfs
is not the blocker. Then is absence of ipv6 the issue? (Or why isn't
systemd 183 telling me why it's refusing to start normally?)
One thing I noted was that the broken "could not find module by
name" message comes from libkmod (kmod8). Apparently when it has
received a request from systemd for the (non-existent) ipv6 module.
Allin Cottrell
prev parent reply other threads:[~2012-05-27 21:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-27 19:01 systemd 183, boot problem Allin Cottrell
2012-05-27 20:17 ` Kay Sievers
2012-05-27 21:04 ` Allin Cottrell [this message]
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=alpine.LFD.2.01.1205271652240.9130@myrtle \
--to=cottrell@wfu.edu \
--cc=linux-hotplug@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 read-only IMAP folder(s) and NNTP newsgroup(s).