Arch Linux

Lorddusty

Member

Registered: 2013-12-28

Posts: 8

Re: [Solved] Kernel panics with "No init found" after upgrade

Hi,

ran into the same issue and it took me a little more to resolve this.
Finally I found the actual reason was, that a package for kde replaced the symlink /usr/lib64 -> /usr/lib with a real directory /usr/lib64. Moving the corresponding files to the right location in /usr/lib and recreating the symlink correctly, made mkinitcpio creating the correct initramfs contents ...

BR
LordDusty

Sanne

Member

Registered: 2012-03-13

Posts: 87

Re: [Solved] Kernel panics with "No init found" after upgrade

...a package for kde replaced the symlink /usr/lib64 -> /usr/lib with a real directory /usr/lib64.

What package? If from the official repositories, it should be reported as a bug, I think. If from AUR, the maintainer should be notified.

---

If our currency were not money but appreciation and acknowledgement for what we do for others, for the community, for the benefit of all, we would have paradise on earth.

Jauch

Member

From: Portugal

Registered: 2010-12-14

Posts: 57

Re: [Solved] Kernel panics with "No init found" after upgrade

Good, LordDusty.

So this was the reason why I had to "delete" the /usr/lib64 folder and "re-install" the filesystem in order to the mkinitcpio to work properly.

Well done

But is very important to follow the Sanne advice, because on a next update of this package, the problem could arise again...

Cheers
Eduardo

ryuzy

Member

Registered: 2014-01-12

Posts: 7

Re: [Solved] Kernel panics with "No init found" after upgrade

Hi,

ran into the same issue and it took me a little more to resolve this.
Finally I found the actual reason was, that a package for kde replaced the symlink /usr/lib64 -> /usr/lib with a real directory /usr/lib64. Moving the corresponding files to the right location in /usr/lib and recreating the symlink correctly, made mkinitcpio creating the correct initramfs contents ...

BR
LordDusty

The same thing happened to me.
When today I updated the kernel I received the kernel panic with No init found, Failed to execute /init.
I booted in chroot and, like you said, I had a folder /usr/lib64 instead of a symbolic link.
Deleting the folder (copying the files first) and recreating the link solved the kernel panic.
I think that the driver of my canon mx390 installed from AUR caused this, but I'm not sure of it.

Anyway, thank you very much for the solution!