You are not logged in.
Pages: 1
Topic closed
Start by booting the install ISO, chroot'ing into your install and re-running mkinitcpio
https://wiki.archlinux.org/index.php/Ch … rch-chroot
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
Start by booting the install ISO, chroot'ing into your install and re-running mkinitcpio
https://wiki.archlinux.org/index.php/Ch … rch-chroot
i just executed the command `mkinitcpio -p linux`, the kernel is also panic.
anything else to do ? thx
Last edited by zjykzk (2020-01-06 04:55:59)
Offline
Did you try and follow the advice of the error message and explicitly pass your init location as a kernel parameter?
And just rebuilding the intramfs and hoping is not much of a strategy. Read your logs and see what happened during the upgrade. Try downgrading the kernel. Try helping yourself.
Offline
Did you try and follow the advice of the error message and explicitly pass your init location as a kernel parameter?
And just rebuilding the intramfs and hoping is not much of a strategy. Read your logs and see what happened during the upgrade. Try downgrading the kernel. Try helping yourself.
i had downgraded the kernel and added the option parameter with '/sbin/init'. it was all failed.
it produced same error message. ;(
Offline
it found /init (of the initramfs) but there is some problem with it (syntax error or anything) so something wrong with your initramfs
to figure out what's going on you might have to take a look at it directly
Offline
fixed, some so file is missing in the initramfs-linux.img file
the checking command is
mkdir /tmp/foo
cd /tmp/foo
zcat /boot/initramfs-linux.img | cpio -i
chroot . /bin/sh
set these files'path in the field FILES in the file /etc/mkinitcpio.conf, then rebuild the initramfs.
it's done
Last edited by zjykzk (2020-01-14 03:44:31)
Offline
it found /init (of the initramfs) but there is some problem with it (syntax error or anything) so something wrong with your initramfs
to figure out what's going on you might have to take a look at it directly
I'm facing the same issue now that I've upgraded to 5.5.2... (and all the other kernel options are broken the same way) would you mind letting us know what was the missing file (.so lib?) on your initramfs?
Is this a systemic issue? (ie. broken mkinicpio scripts) or this is a weird occurrence due some rootfs differences?
Offline
Actually I've just found what my problem was.
Part of the linux drivers for my scanner overwrote the /usr/lib64 from being a symlink, hence when creating the initramfs some so files (thanks zjykzk) might have gone missing. So removing those offending files , recreating the symlink and regenerating the mkinitcpio my system booted again.
Offline
Thanks! This just got my system working again after hours of searching, initramfs-rebuilding and downgrading of packages, because I couldn't figure out why the init was failing. And of course `mkinitcpio` doesn't complain, because it's always better to leave the user with an unbootable system.
For the search engines: Kernel panic / No working init found is caused by the Brother Scanner Driver replacing a symlink with an actual directory. Because what could possibly go wrong?
Last edited by Bachsau (2023-05-26 17:23:46)
Offline
Closing this old thread (the OP has not been back since 2020).
Offline
Pages: 1
Topic closed