You are not logged in.
Hi,
Yesterday, I have actualized the system with usually pacman -Suy.
Today, I cannot boot up the system, where appears the following message:
Failed to execute /init
Kernel panic - not syncing: No init found. Try passing init= option to kernel.
I will be very happy for any suggestion for solve this problem.
Offline
Try adding init=/sbin/init to your kernel line, it's strange that you need to do that though.
Offline
I added init=/sbin/init to kernel line in menu.lst file of grub.
Now, the message is:
Failed to execute /init
Failed to execute /sbin/init. Attempting defualts ...
Kernel panic - not syncing: No init found. Try passing init= option to kernel.
Offline
Is /sbin/init there? It is owned by the sysvinit package, maybe that package didn't cleanly install? I'd boot a live cd, chroot into your arch install and reinstall sysvinit. You should also be able to remove the init= option if everything works correctly.
Offline
Yes, there is /sbin/init. But, pacman have actualized the sysvinit package. It's possible that this package is not properly installed. Now, I don't know how reinstall it. If possible, I would like that you explain or indicate how to do this with a livecd.
Offline
after the update to 2.6.22.6-2 I see random kernel panics.
I get
kinit: cannot open root device
Rebooting solves the problem, but 3-4 reboots I get again same error.
Offline
Yes, there is /sbin/init. But, pacman have actualized the sysvinit package. It's possible that this package is not properly installed. Now, I don't know how reinstall it. If possible, I would like that you explain or indicate how to do this with a livecd.
I'll assume your arch root is at /dev/sda1 and that that is an ext3 volume:
Boot the live cd and chroot into your arch install:
mkdir /media/arch
mount -t ext3 -o defaults,rw /dev/sda1 /media/arch
chroot /media/arch
run pacman to reinstall the sysvinit package:
pacman -S sysvinit
and answer yes to the "is already up to date" message, if finished you can reboot into arch.
I'm not sure this'll fix your problem though, but it might.
Last edited by Ramses de Norre (2007-09-22 16:19:34)
Offline
Ramses de Norre, thanks for your help.
Well, I followed this procedure, and the sysvinit package was actualized, but the problem isn't solved.
Thus, I reinstalled all the system, that was installed 1 year ago.
I think that such errors in packages are due to the change in repos from current to core.
Offline