touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

Pretty much the entire log is from the initramfs, the root fs'
/sbin/init indeed doesnt' seem to get called.

Can you please check ls -l /sbin/init in your VM? It should be a symlink
to /lib/systemd/systemd.

Also, could you boot with "break=bottom", and check ls -l
/root/sbin/init ? Does that exist, or was it removed/modified in some
funky way?

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

** Summary changed:

- Ubuntu 15.04 VM doesn't boot after switching permanently to systemd
+ fails to boot with "Attempted to kill init"

** Tags added: systemd-boot

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

Title:
  fails to boot with "Attempted to kill init"

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  My Ubuntu 15.04 VM (running under VMware) doesn't boot anymore after permanently switching to systemd.
  I've switched to systemd with "apt install systemd-sysv --purge" (it only purged the upstart package) and with the default "Ubuntu" entry the boot fails after about 2.5 sec with a kernel panic ("Attempted to kill init"). But it works when edit the grub entry (in the grub shell) and add "init=/lib/systemd/systemd".

  Attached is the serial output (with "debug" but no "init=" parameter).

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