[Bug 1236642] Re: failed to execute /init

Rob Frohne frohro at wallawalla.edu
Tue Oct 8 17:18:14 UTC 2013


Thanks Philip,

I hadn't figured out about the chroot.  I was just connected to it from
13.04.  Then I tried chroot, but you can't chroot from a 32 bit system to
a 64 bit root, so I am now booted from the USB Live 64 bit install and
have chrooted there okay, but it won't update.  Here is what I get:

root at ubuntu:/# sudo update-initramfs -c -k 3.11.0-11-generic
sudo: unable to resolve host ubuntu
update-initramfs: Generating /boot/initrd.img-3.11.0-11-generic
/usr/sbin/mkinitramfs: 137: /usr/sbin/mkinitramfs: cannot create
/dev/null: Permission denied
/usr/sbin/mkinitramfs: 142: /usr/sbin/mkinitramfs: cannot create
/dev/null: Permission denied
/usr/sbin/mkinitramfs: 142: /usr/sbin/mkinitramfs: cannot create
/dev/null: Permission denied
/usr/sbin/mkinitramfs: 279: /usr/sbin/mkinitramfs: cannot create
/dev/null: Permission denied
WARNING: no ldd around - install libc-bin
update-initramfs: failed for /boot/initrd.img-3.11.0-11-generic with 1.
root at ubuntu:/# which ldd
/usr/bin/ldd

I noticed from reading the thread quoted above than someone in August had
this issue, and tried the next daily build and it solved the problem for
him.  Maybe I should do that, but then I'll always wonder what was the
problem with this one.  

Any ideas?

Thanks,

Rob

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

Title:
  failed to execute /init

Status in “grub2” package in Ubuntu:
  Incomplete

Bug description:
  I installed Ubuntu 13.10 _x64bit by this method last night (10/6/2013)
  and ended up with a kernel panic with the message "failed to  execute
  /init"  and here is how I installed it:

  1)  Using 13.04 on another partition of the same hard drive, made using unetbootin a flash drive with the latest daily Ubuntu _x64 image on it.
  2)  Booted on the USB drive, selected to do an "other partitioning" scheme, and set / to 60 Gigs of the remaining free space, and swap to 4 GB.  Then went through the install with the download from the Internet selected.  When it was done and said it was ready to reboot, I tried, but got the error, which I was able to read using the boot into recovery mode option.

  I enclosed a photo of the kernel panic screen.

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



More information about the foundations-bugs mailing list