For me the problem originated from using unetbootin to install. When I
went to using a CD, all was well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1236642
Title:
failed to execute /init
To man
This is far from expired.
My desktop has an 3 disks. one is an SSD (for the / filesystem). I was unable
to install Ubuntu 64 bits on it because of this problem. Tried 12.04 and 13.10
both as a CD install and USB. always the same message. It seems there is no
/init script in the initramfs.
Grub
Same bug after some updates in ubuntu 13.10. I had to reistall after
having tried all methods of all gurus around. Reinstall over same OS
failed with same error. No idea why. It seems that someone in the web
solved this error putting back the link in the /lib/lib64 folder.
ln -s /lib/x86_64-linux
[Expired for grub2 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: grub2 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1236642
T
It appears this affected other users too, based on this thread.
http://askubuntu.com/questions/355345/failed-to-execute-init-kernel-
panic-not-syncing-no-init-found
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Further information:
This bug might be better filed against unetbootin, because when I
install from a DVD, it works flawlessly!
I am going to proceed on with my install, but I may have a chance to
test things after I determine that I can ditch my 13.04 partition.
Thanks for all the help!
Rob
-
Phillip,
You suggestion about bind mounting allowed update-intiramfs to work, but
the no /init error persists.
I think the key lies in the fact that 32 bit installs work, but not 64
bit ones, but I'm not quite sure where to go from here.
Thanks for the assistance.
Rob
--
You received this bug
Thanks Phillip,
I discovered something interesting. The problem seems to go away if I
install a 32 bit OS instead of 64 bit. Right now I'm installed with
Ubuntu 13.10 32 bit on that same partition, and everything is hunky
doory. I do want to change over to 64 bit, so I'm going to go back and
in
Bind mount /dev, /proc, and /sys before chrooting:
sudo mount --bind /dev /mnt/dev, etc
You might also want to check the drive's SMART status in the disk
utility to make sure it isn't failing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I decided to try installing 13.04, 64 bit, to see what would happen and
the results are identical. So this is not an OS issue, or it is there
in 13.04 as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
I went and tried the daily build from today, and the first reboot I did
recovery mode so I could see what was happening. I noticed the kernel
panic was different than the ones I get subsequently. I thought I took
a photo of it, but the camera button didn't get pushed properly, and I
missed it. E
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
I'm not sure what you mean by "when connected into the / directory of
the 13.10 partition". Did you mount it and chroot into it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1236642
Title:
failed
Here is my grub.cfg.
I'm still trying to figure out how to run update-initramfs when booted
from Ubuntu 13.04.
It seems to be the chicken and egg problem. From 13.04 when connected
into the / directory of the 13.10 partition, I get:
sudo update-initramfs -c -k 3.11.0-11-generic
[sudo] password
/init is the script in the initramfs, not /sbin/init in your root fs, so
it sounds like your initramfs is broken. Try regenerating it with
update-initramfs, and attach your /boot/grub/grub.cfg.
** Changed in: grub2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification
One thing I did note as I was in grub2, was that the drive partitions
said something like this (hd0,msdos), and I didn't think there were any
msdos partitions. The above note seems to corroborate that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
I guess the msdos is the partition type. (I used logical, in gparted or
the installer; I can't recall which anymore.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1236642
Title:
failed to execute
This might help too:
frohro@frohro-e6410:/media/frohro/5b901d56-389b-48b1-a911-08dab37d228d$ sudo
fdisk -l
[sudo] password for frohro:
Disk /dev/sda: 128.0 GB, 128035676160 bytes
255 heads, 63 sectors/track, 15566 cylinders, total 250069680 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector
The directories and files in the root partition look similar to my other
working 13.04 partition with the exception of .old files. The
/sbin/init is there.
Here is what the initrd.img has within it:
$ lsinitramfs initrd.img | grep init
initrd.img
bin/run-init
scripts/init-top
scripts/init-top/u
19 matches
Mail list logo
