16 Mar
2018
16 Mar
'18
4:10 p.m.
I'm running Debian Stable on a few different machines and have not seen
this on any of them.
On Fri, Mar 16, 2018 at 12:07 PM, D. R. Evans <doc.evans(a)gmail.com> wrote:
Thierry de Coulon wrote on 03/16/2018 09:22 AM:
--
John Pisini
Systems Administrator
TFCCS
617-450-3988
Disclaimer for email:
The information contained in this electronic message and any attachments to
this message is intended for the exclusive use of the addressee(s) and may
contain confidential or privileged information. This e-mail is not
intended to, and shall not, constitute an electronic signature giving rise
to a binding legal contract, unless expressly stated otherwise in the body
of the e-mail by the sender.
On Friday 16 March 2018 15.13:31 Baron wrote:
and
Hi Guys,
(...)
Problem: On boot up, maybe every second or third
time, I get a black
screen with "[*** ] Start job running - ~0.XX seconds. 1:30."
This has, I'm pretty sure, to do with systemd. I got that several time yes, when you don't know about it it's
quite difficult to solve.
I agree, I have similar issues... sometime boots are clean, sometimes
various
boot-time tasks take a noticeable number of seconds while a "Start job
running" message is displayed, and sometimes that message waits for the
entire
90 seconds before timing out and the boot continues to completion.
Unlike the original poster, though, if I wait the system does eventually
boot
into what seems to be a fully-working state (even if some of the boot tasks
say "Failed" after the 90-second timeout).
It all seems completely unpredictable here. I have several systems running
debian stable (although only one using TDE), and they all behave like this.
So I just put it down to some race condition(s) in systemd that I suppose
will
get fixed at some point but for now is just something that I have to put
up with.
It doesn't appear to be in any way related to TDE, though.
Doc
--
Web: http://enginehousebooks.com/drevans