From: Bob Tracy <rct@gherkin.frus.com>
To: linux-alpha@vger.kernel.org
Subject: Re: [BUG] 4.14 cannot find configured disks/partitions
Date: Wed, 29 Nov 2017 23:49:29 -0600 [thread overview]
Message-ID: <20171130054929.GC14814@gherkin.frus.com> (raw)
On Tue, Nov 28, 2017 at 11:49:55PM -0600, Bob Tracy wrote:
> (...)
>
> Upon trying to reboot on my 4.13 kernel, I discovered *it's* now broken
> as well, thanks to a recent udev update :-(. Now I get a bunch of
> timeouts for all the filesystems (including the swap partition) not
> mounted immediately at boot time. "journalctl -xb" is littered with
> applicable messages of the form
>
> dev-sdaX.device: Job dev-sdaX.device/start timed out.
> Timed out waiting for device dev-sdaX.device.
>
> In systemd's emergency mode, I can manually mount (or swapon as
> appropriate) the various sdaX partitions.
I *thought* this particular scenario sounded familiar. Nearly three
years ago, this problem showed up when "systemd" and "udev" became
dependent on CONFIG_FHANDLE being set in kernel builds. I didn't
suddenly start unsetting it again, so what changed in 2017?
--Bob
next reply other threads:[~2017-11-30 5:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 5:49 Bob Tracy [this message]
[not found] <20171124051010.GA18422@gherkin.frus.com>
[not found] ` <20171129054955.GA9467@gherkin.frus.com>
2017-12-01 21:16 ` [BUG] 4.14 cannot find configured disks/partitions Michael Cree
2017-12-02 0:22 ` Bob Tracy
2017-12-02 4:49 ` Bob Tracy
-- strict thread matches above, loose matches on Subject: below --
2017-11-30 5:50 Bob Tracy
2017-11-30 5:48 Bob Tracy
2017-11-30 5:48 Bob Tracy
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=20171130054929.GC14814@gherkin.frus.com \
--to=rct@gherkin.frus.com \
--cc=linux-alpha@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