[SOLVED] can't boot linux after moving drives - "Kernel panic - not syncing: No init found"
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
can't boot linux after moving drives - "Kernel panic - not syncing: No init found"
Hello.
This is my first post here. I usually find answers just reading, but this time I need to ask for help.
I moved my boot drive and windows drive to a different controller on my motherboard, as well as move the drives that make my linux RAID to different ports, but in the same controller. I ended up with the Kernel panic error.
I then read that when moving drives fstab and lilo.config need to be changed accordingly. I did that by entering though a live cd. Now the problem is booting into Linux and running the command lilo, as I've read I have to after changing lilo.config.
If this actually isn't going to fix the problem. Then I would really appreciate any help on the matter.
Possibly boot the Slackware CD1 and choose your present
/ fs where your drive is actually located. Then you would
be in your system and "lilo" should work.
Another method is to boot with Slackware CD1 then chroot
into your system.
As for the RAID you'll need to reassemble it once you get
the system sorted out.
As stated above use rescue mode.You can also use trail and error method like trying root(tab--->)[to get the device naming] at grub prompt.Also kernel tab key...
Thanks you guys. I tried your suggestions, but it only half worked. I was able to use the lilo command, but it couldn't overwrite the old install for some reason. So I went searching some more and found a script to reinstall lilo and that solved everything. I appreciate your help though.
by the way, to any onlookers
the script in slackware was "liloconfig".
It skips the installation all the way to the lilo setup part. Solved everything.
I realize now that the drive names didn't change either. Even though sda was moved to a different controller and shouldn't be sda anymore(more like sde), it still held as sda.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.