Public bug reported:
Hi,
on several of my machines (encrypted, 16.04 and 16.10) it *sometimes* happens,
that systemd is stuck in booting telling
"A start job is running for dev-mapp...ypt.device (5min 40s / no limit)"
(endless loop, counting the time up)
(only) rebooting helps, but that's annoying and keeps machines from
automated booting.
Additional problem one:
That damned systemd shortens the output to the terminal line length and instead
of telling the device name to give a hint where the problems come from it just
says dev-mapp...ypt.device
Additional problem two:
I've activated systemd's debug shell on Terminal 9 in order to debug the
problem, but the debug shell is rendered useless by systemd, since it blasts
it's messages about the problem to tty9 as well, thus making it impossible to
work there.
Additional problem three:
These device entries seem to be generated dynamically from fstab/crypttab and
not exist as files, so it is not even visible, what's the contents of these
tasks.
Additional problem four:
I did not find a description of a debugging procedure.
So I do not even see how to debug that weird mess. Why on earth has
ubuntu moved to such a confused heap of undebuggable spaghetti code?
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: systemd 231-9ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
Uname: Linux 4.8.0-39-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Mar 1 10:18:15 2017
InstallationDate: Installed on 2016-04-22 (312 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp.
Bus 001 Device 003: ID 046d:c31d Logitech, Inc. Media Keyboard K200
Bus 001 Device 002: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110
Optical USB Mouse]
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-39-generic
root=UUID=d0b47754-d5ca-49ec-8190-92a24e58e373 ro rootflags=subvol=@ nosplash
noplymouth nomodeset text
SourcePackage: systemd
UpgradeStatus: Upgraded to yakkety on 2016-10-17 (135 days ago)
dmi.bios.date: 03/16/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.50
dmi.board.name: N3150-NUC
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/16/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug yakkety
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1668906
Title:
systemd occasionally hangs forever while booting: A start job is
running for ...
Status in systemd package in Ubuntu:
New
Bug description:
Hi,
on several of my machines (encrypted, 16.04 and 16.10) it *sometimes*
happens, that systemd is stuck in booting telling
"A start job is running for dev-mapp...ypt.device (5min 40s / no
limit)" (endless loop, counting the time up)
(only) rebooting helps, but that's annoying and keeps machines from
automated booting.
Additional problem one:
That damned systemd shortens the output to the terminal line length and
instead of telling the device name to give a hint where the problems come from
it just says dev-mapp...ypt.device
Additional problem two:
I've activated systemd's debug shell on Terminal 9 in order to debug the
problem, but the debug shell is rendered useless by systemd, since it blasts
it's messages about the problem to tty9 as well, thus making it impossible to
work there.
Additional problem three:
These device entries seem to be generated dynamically from fstab/crypttab and
not exist as files, so it is not even visible, what's the contents of these
tasks.
Additional problem four:
I did not find a description of a debugging procedure.
So I do not even see how to debug that weird mess. Why on earth has
ubuntu moved to such a confused heap of undebuggable spaghetti code?
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: systemd 231-9ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
Uname: Linux 4.8.0-39-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Mar 1 10:18:15 2017
InstallationDate: Installed on 2016-04-22 (312 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp.
Bus 001 Device 003: ID 046d:c31d Logitech, Inc. Media Keyboard K200
Bus 001 Device 002: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110
Optical USB Mouse]
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-39-generic
root=UUID=d0b47754-d5ca-49ec-8190-92a24e58e373 ro rootflags=subvol=@ nosplash
noplymouth nomodeset text
SourcePackage: systemd
UpgradeStatus: Upgraded to yakkety on 2016-10-17 (135 days ago)
dmi.bios.date: 03/16/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.50
dmi.board.name: N3150-NUC
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/16/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1668906/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
