ArchThis Forum is for the discussion of Arch 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.
installed Arch a few days ago and i get an error message when I try to boot:kinit; cannot open root device hda3(3,3)
kinit: init not found!
kernel panic-no syncing: attempted to kill init
I have checked all the obvious and have also posted on Arch's web page forum, but no help. i am using lilo as the boot loader and it looks fine. Any help would b appreciated!!!! Thanks
This maybe obvious, but did you recently upgrade the kernel and forget to run lilo (as a command in your terminal) before trying to boot again. I'm not sure what the error looks like if this happens, but I figure it's probably an easy mistake to make if you're using lilo. If so then take a look here. I think if you can boot with a livecd and chroot into arch, you just need to run lilo, but since I don't use it I don't know for sure.
I've also had a message like this after installing a new kernel (in Arch). The problem for me was that I'd left the "initrd" line in the (grub) file, whereas I was not using initrd in the new kernel. I just got a rid of it and all was OK.
Also, it might help if you post your lilo file, and also say if you're using the Arch kernel (2.4 or 2.6) or whether you're using your own.
Thanks for you're replies gentelmen> i am running Arch kernel 2.6.18. i have tried everything you have suggested and i also did a clean install using grub as boot loader and the same thing happens.
i had this problem recently and i fixed by recompiling my kernel in the installation because i was missing some drivers for the ext3 filesystem. Depending on what filesystems you are using you may have to add the corresponding drivers. Typically installers do this automatically but every once and a while they miss something.
Thanks for you're replies gentelmen> i am running Arch kernel 2.6.18. i have tried everything you have suggested and i also did a clean install using grub as boot loader and the same thing happens.
can you post your boot load configuration file? did you check the new mkinitcpio system? afaik 2.6.18 has no support for the old initramfs stuff.
regards,
slackie1000
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.