touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

Keeping notes: I added "LABEL=mystery /var ext4 defaults 0 0" to
/etc/fstab to try and reproduce this.

 - On a standard cloud image (server-ish, no graphical plymouth) boot
waits for the device to appear for 90s, times out, and I get into the
emergency shell. So that works alright.

 - On a standard desktop image (graphical plymouth) I see the running
dots for 90s, then they stop. I need to switch to Alt+F7 to see the
emergency shell, because plymouth does not get stopped. So that's
something to fix. Is that the case for you as well? I. e. is it just
that the emergency shell doesn't appear by itself but you can switch VT
to it? Or do the plymouth dots just go on and on? Where can I download
that desktop ISO?

-- 
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/1471258

Title:
  Invalid fstab entry leads to an hanging system rather than a debug
  command line

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  While playing with the new desktop iso I had a case of buggy fstab
  entry, that leads to a system hanging out boot, it should send you to
  a debug shell or friendly recovery instead

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1471258/+subscriptions