touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

> I know that systemd boot takes ages to boot

That's certainly not "known". If you use ecryptfs, you were most likely
affected by bug 953875 which got only fixed yesterday. That would have
caused a 90 second boot delay. It's likely that this was the issue
(check if you have a commented out cryptswap in /etc/crypttab).

We actually do show progress on file system checks, but it seems we are
missing the part for fixing errors.

** Summary changed:

- [systemd] Unbootable Vivid after poweroutage + file system with errors
+ no plymouth confirmation for fixing file system errors

** Changed in: systemd (Ubuntu)
       Status: New => Triaged

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  no plymouth confirmation for fixing file system errors

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Guys,

  I started to use Vivid with systemd yesterday, and today, my system
  froze due to lack of ram memory (my problem, obviously).

  I tried to "reboot" it, without success... The reboot command did not
  succeed. I tried to reboot by clicking on Unity menu, didn't worked
  either.

  So, I pressed the power button to turn my machine off.

  Then, the Ubuntu did not booted anymore... I know that systemd boot
  takes ages to boot (upstart boots in a 2 seconds) but, this time, 5
  minutes passed and nothing.

  I rebooted my machine again, now, using upstart (Grub -> Advanced
  Options -> Upstart) and guess what? The plymouth screen (I think), was
  asking me to "press F" to fix file system errors!

  That message did not appeared when booting with systemd. Removing
  "quiet splash" did not helped, I saw only a black screen (when with
  systemd).

  Definitively systemd isn't ready for prime time on Ubuntu. I'm using
  Jessie on another machine, systemd runs just fine there.

  Regards,
  Thiago

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