[SOLVED] what is the best solution to overcome kernel panic init not found?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
what is the best solution to overcome kernel panic init not found?
I recently installed slackware64-current may 18 build , after two three restarts it shows kernel panic init not found pass INIT= option . It happened to me on previous builds of slackware64 also once or twice.. normally I do a full installation as when I googled there so many results which doesn't fit right for me..
what is the best solution to overcome kernel panic init not found?
nothing I just installed the new iso and worked on it last two days and shut it down normally... and today it showed this... it happened to me on the slackwate64 14.2 beta 1 17 jan iso also after working on it for more than 4 months... that's y I installed may 18 build instead of upgrading it
Have you checked your harddrive for corruption? If this has happened before without anything triggering it (like a kernel update that you forgot to run lilo with), then it could mean that hardware issues are your problem, not Slackware.
If you didn't do anything in Slackware to break the boot process (ie, upgrading the kernel or changing conf files), then it has to be hardware. A known working installation doesn't just suddenly break without reason.
What changes did you make prior to the last reboot? Upgrades with slackpkg (there was a kernel upgrade on the 20 MAY updates, and if you didn't rerun lilo and, if you use it, regenerate your initrd, your system will break)? Adjustment of /etc/lilo.conf? /etc/inittab? /etc/fstab?
Also, what is your partition layout? Do you have everything in one partition, or are there multiples? If there are multiples, please post your /etc/fstab.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.