So can this be backported to utopic? It's kind of a serious bug since it
renders the system unbootable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1421117
Title:
fails to boot with Attempted to
This bug was fixed in the package initramfs-tools - 0.103ubuntu13
---
initramfs-tools (0.103ubuntu13) vivid; urgency=medium
* hooks/busybox: Create /bin/chroot symlink, to fix absolute symlinks when
busybox-static is not installed. (LP: #1421117)
-- Martin Pitt
initramfs-tools already depends busybox-initramfs. What's missing is the hook
to symlink bin/chroot to busybox in the initrd.
Supporting /sbin/init being a symlink was not fixed for all cases in bug
#1351295. There was only a readlink symlink added but the chroot call in the
following line was
** Changed in: initramfs-tools (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1421117
Title:
fails to boot with Attempted to kill init in VMWare,
Correct, ubuntu defaults to pulling in busybox-static into initramfs if
available. In practice, we pretty much require it for all our initramfs
and rarely don't have it. Maybe it should become a hard dependency on
ubuntu?
However, given that we support booting with either systemd or upstart,
I managed to some more output to the serial log (booted with
console=ttyS1,115200 only, no console=tty0):
starting version 219
[1.851984] sd 2:0:0:0: [sda] Assuming drive cache: write through
/init: line 307: chroot: not found
Target filesystem doesn't have requested /sbin/init.
/init: line
Michael confirmed on IRC that with an explicit ln -s busybox
${DESTDIR}/bin/chroot in /usr/share/initramfs-tools/hooks/busybox it
works. It's indeed a bit curious where the existing hardlink comes
from..
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided = Medium
** Changed in:
FTR, that happens if busybox-static is *not* installed; that's in
ubuntu-standard, which explains why most people have it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1421117
Title:
fails to boot
For the record, the chroot is done here:
# Work around absolute symlinks
if [ -d ${rootmnt} ] [ -h ${rootmnt}${checktarget} ]; then
case $(readlink ${rootmnt}${checktarget}) in /*)
checktarget=$(chroot ${rootmnt} readlink
${checktarget})
