Public bug reported:
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
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1431138
Title:
[systemd] Unbootable Vivid after poweroutage + file system with errors
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431138/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
