touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

Harry [2014-10-28 16:58 -0000]:
> Martin, do you have upstart, systemd-shim, cgmanager and libcdmanager0
> purged and are you using kernel line init=/lib/systemd/systemd ?
> 
> I cannot boot at all if I remove the kernel booting line.

Well yes -- You have no package which provides /sbin/init then, so you
need to install either upstart or systemd-sysv.

> 2) with quiet (but splash dropped) in the kernel line, I can reproduce
> the hanging very often.
> 
> 3) this is all there is visible in the screen when booting hangs:
> [1.490641] systemd[1]: job lvm2.service/start deleted to break ordering cycle starting with local-fs.target/start
> [1.492015] systemd-fsck[235]:/dev/sda1: clean, 86887/6111232 files, 1044303/24414062 blocks

Interesting, so mostl likely the fsck succeeded. So next thing: Can
you please add "systemd.debug-shell" to the kernel command line, and
when you get the hang press Alt+F9? There should be a root shell
there. Please run "systemctl" to see which unit is something other
than "loaded active", like "loading", or "failed", etc. For those it
would be very helpful if you could then do
"sudo systemctl -l status <servicename>", e. g.
"sudo systemctl -l status display-manager" and capture the output. You
can e. g. redirect the output to a file in /root or even /home/harry/,
if file systems are already mounted; if not, a photo camera shot will
do, too.

Please let me know if the above instructions are too hard for you (not
sure about how familiar you are with unix command line tools).

Thanks!

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

Title:
  systemd 215 hangs in fsck

Status in “systemd” package in Ubuntu:
  Incomplete

Bug description:
  I just installed (for testing) the newest systemd from Vivid proposed repositories.
  Yes, that is only a proposed package.
  The version is 215-5ubuntu1. Also the new plymouth was needed to do this (version 0.9.0-0ubuntu8).

  After the installation I found that every now and then booting or rebooting fails.
  It fails in a system-fsck line. So, nowhere to go from that, no tty's, no nothing.
  After each failure the next booting is successful, however.

  My setup is extremely fast, I am able to get to the desktop in about 5 seconds from grub menu.
  The setup contains Intel Core i7 4790 processor and Samsung 850 Pro SSD.

  This may also be some sort of race situation.

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