Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #212521
| From | Étienne Mollier <etienne.mollier@mailoo.org> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Systemd start that won't stop |
| Date | 2019-08-09 19:00 +0200 |
| Message-ID | <ytgpd-503-29@gated-at.bofh.it> (permalink) |
| References | <ytf9M-4ii-15@gated-at.bofh.it> <ytfCO-4IF-15@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
Kenneth Parker, on 2019-08-09:
> On Fri, Aug 9, 2019, 11:30 AM Curt Howland <Howland@priss.com> wrote:
> > Hi. New Buster install.
> >
> > While X11 is working just fine, the console is unusable, due to a
> > startup message that never stops:
> >
> > [ ***] A start job is running for Hold until boot process finishes (2h 54m 38s / no limit)
> >
> > This goes on until the laptop is shut down.
> >
> > How do I find the errant process? The start-up messages fly by, but I
> > don't see any failures, or any indication of what process it is that
> > won't stop starting.
Good day
You may be able to get a few information out of the following,
maybe see what's on hold:
$ sudo systemctl list-units
But it is the first time I hear about this specific "start job"
"running for Hold" behaviour. I'm not sure about what to look
at. A blind shot at the following might bring some additional
information too:
$ sudo journalctl -xe
In case you were encountering some hardware issue (but I doubt
so for the moment), perhaps a look at the following could be
welcome:
$ sudo dmesg
And of course, from Kenneth:
> Are any of your File Systems out of space?
Kind regards,
--
Étienne Mollier <etienne.mollier@mailoo.org>
5ab1 4edf 63bb ccff 8b54 2fa9 59da 56fe fff3 882d
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Systemd start that won't stop Curt Howland <Howland@priss.com> - 2019-08-09 17:40 +0200
Re: Systemd start that won't stop Kenneth Parker <sea7kenp@gmail.com> - 2019-08-09 18:10 +0200
Re: Systemd start that won't stop Étienne Mollier <etienne.mollier@mailoo.org> - 2019-08-09 19:00 +0200
Re: Systemd start that won't stop Curt Howland <Howland@priss.com> - 2019-08-09 20:10 +0200
Re: Systemd start that won't stop Étienne Mollier <etienne.mollier@mailoo.org> - 2019-08-09 21:00 +0200
Re: Systemd start that won't stop Richard Hector <richard@walnut.gen.nz> - 2019-08-10 09:40 +0200
Re: Systemd start that won't stop Sven Joachim <svenjoac@gmx.de> - 2019-08-09 21:40 +0200
Re: Systemd start that won't stop Étienne Mollier <etienne.mollier@mailoo.org> - 2019-08-09 22:10 +0200
Re: Systemd start that won't stop Greg Wooledge <wooledg@eeg.ccf.org> - 2019-08-09 22:30 +0200
Re: Systemd start that won't stop Étienne Mollier <etienne.mollier@mailoo.org> - 2019-08-09 23:20 +0200
Re: Systemd start that won't stop Sven Joachim <svenjoac@gmx.de> - 2019-08-09 23:00 +0200
Re: Systemd start that won't stop Felix Miata <mrmazda@earthlink.net> - 2019-08-09 23:30 +0200
Re: Systemd start that won't stop Mart van de Wege <mvdwege@gmail.com> - 2019-08-11 19:50 +0200
Re: Systemd start that won't stop <tomas@tuxteam.de> - 2019-08-11 20:20 +0200
Re: Systemd start that won't stop Mart van de Wege <mvdwege@gmail.com> - 2019-08-11 22:50 +0200
Re: Systemd start that won't stop <tomas@tuxteam.de> - 2019-08-11 23:40 +0200
Re: Systemd start that won't stop Reco <recoverym4n@enotuniq.net> - 2019-08-11 22:50 +0200
Re: Systemd start that won't stop <tomas@tuxteam.de> - 2019-08-11 23:40 +0200
Re: Systemd start that won't stop David Wright <deblis@lionunicorn.co.uk> - 2019-09-17 20:50 +0200
csiph-web