[Bug 1652462] Re: No init after do-release-upgrade from 14.04 to 16.04 (kernel panic)

[Graeme Bragg]

I have just been recovering a system that failed to upgrade from 14.04
to 16.04 with the same error as the OP. The solution was to chroot in
from a liveCD following the Update Failure instructions.

After an apt-get update, apt-get upgrade, apt-get dist-upgrade and apt-
get -f install the system could be booted normally, albeit without a
working X-environment and package dependancy issues.

The package dependancy issues (mostly in Latex-related packages, with it
trying to both upgrade and install tex-common as part of an "apt-get -f
install", and libboost) were resolved by removing the offending packages
and their dependancies with "dpkg --remove --force-remove-reinstreq
<packagename>".

apt-get update and upgrade then worked and the system booted with a
working X-Environment.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-release-upgrader in
Ubuntu.
https://bugs.launchpad.net/bugs/1652462

Title:
  No init after do-release-upgrade from 14.04 to 16.04 (kernel panic)

Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  I tried to upgrade from an up-to-date and working Ubuntu 14.04 to
  16.04 using do-release-upgrade.  The process seemed to complete
  successfully except for a couple of errors regarding fcitx packages,
  which I choose to ignore and fix later.

  I then proceeded to reboot, but the system hanged during the shutdown
  so I decided to hard reboot.

  However, I was greeted by a kernel panic preceded by straightforward
  error messages :

  run-init: /sbin/init: No such file or directory
  Target filesystem doesn't have requested /sbin/init.
  run-init: /sbin/init: No such file or directory
  run-init: /etc/init: Permission denied
  run-init: /bin/init: No such file or directory
  /bin/sh: 0: Can't open splash
  Kernel panic — not syncing: Attempted to kill init! exitcode=0x00007f00
  etc. (last two lines mentioned for SEO purposes)

  Indeed, these files don't exist.  It seems /var/log/apt/history.log
  doesn't log "do-release-upgrade", so I have no clue about what went
  wrong during the upgrade.

  FWIW, I can keep the laptop in this state for a couple of days and
  check or try whatever is proposed (though I'd rather avoid involving a
  live CD or similar).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1652462/+subscriptions