Public bug reported:
Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
machines (with 8GB RAM and Crucial BX200 SSD).
There is a problem running on this machine, but the problem report here
is specifically about how systemd makes this impossible to debug.
Symptoms:
* Installation proceeds normally. I installed with 4 partitions: 10GB /, 20GB
/var, 202GB unused, 8GB swap
* On reboot strange things happen. The system doesn't come up fully; sometimes
it reports "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s!
[systemd-udevd:1148]"
So I try to boot again this time following "Advanced options for
Ubuntu", "Ubuntu, with Linux 4.4.0-31-generic (recovery mode)"
It appears to boot fine. From the Recovery Menu I select "root: Drop to
root shell prompt", then "Press Enter for maintenance". All is good so
far: I get a prompt.
However while I sit looking at this screen, after about two minutes a
bunch of systemd messages scroll up. I captured them as best as I can
with a camera:
[ OK ] Reached target Timers.
[ OK ] Reached target Login Prompts.
[ OK ] Started Stop ureadahead data collection 45s after completed startup
[ OK ] Reached target System Time Synchronized.
[ OK ] Reached target Sockets.
Starting Create Volatile Files and Directories...
[ OK ]Started Set console scheme.
[ OK ] Started Tell Plymouth To Write Out Runtime Data.
[FAILED] Failed to start Create Volatile Files and Directories.
See 'systemctl status systemd-tmpfiles-setup.service' for details.
[FAILED] Failed to start LSB: AppArmor initialization.
See 'systemctl status apparmor.service' for details.
Starting Raise network interfaces...
[ OK ] Started Raise network interface.
[ OK ] Reached target Network.
[ OK ] Reached target Network is Online.
Starting iSCSI initiator daemon (iscsid)...
[ OK ] Started Set console font and keymap.
[ OK ] Started iSCSI initiator daemon (iscsid).
Starting Login to default iSCSI targets...
[ OK ] Created slice system-getty.slice.
[ OK ] Started Login to default iSCSI targets.
[ OK ] Reached target Remote File Systems (Pre).
[ OK ] Reached target Remote File Systems.
At this point it hangs for a few more seconds. Then a few more lines
flash up onto the screen - too fast to see, although I think one of the
lines has the ctrl-D for maintenance message.
Then I can see the Recovery Menu again, *but the keyboard apparently
does not work*. That is, I cannot move the selection up or down: it
appears completely dead at this point. Alt-F2 switches me to a screen
which is completely black apart from flashing cursor, and Alt-F1 puts me
back to the frozen recovery menu.
However, hitting Enter *does* give me a command line prompt again! But
then pressing up and down selects the recovery menu. It appears that the
shell and the recovery menu are both fighting over the keyboard. By
pressing cursor down repeatedly, it appears about 50% of them cause the
recovery menu to move.
This is completely pants: if I boot into recovery mode, I *don't* want
systemd nonsense, I want to see a sequential series of bootup steps; and
when I get a shell, I want that shell to be mine on the console with no
interference - and not taken away again.
Lots of people say "systemd sucks", but I am submitting this in the hope
that providing a *specific* way that it sucks might help get it fixed.
(I have had a number of other cases of system recovery being frustrated
by systemd, but this time I thought I would at least document the
specifics)
** Affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609475
Title:
recovery mode completely broken by systemd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1609475/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
