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.
If you don't have a separate boot partition, just prepend /boot to the above paths, i.e. /boot/vmlinuz and /boot/initrd.
Also, it seems your grub installation has gone kaput. Use the code I posted above to manually boot into your machine and then run grub-install to reinstall grub properly.
If you don't have a separate boot partition, just prepend /boot to the above paths, i.e. /boot/vmlinuz and /boot/initrd.
Also, it seems your grub installation has gone kaput. Use the code I posted above to manually boot into your machine and then run grub-install to reinstall grub properly.
No look
Trying to execute
Code:
kernel /vmlinuz<tab> root=<root device> [<any other options>]
What happened (or what was changed) before this problem appeared?
Regardless, you can boot up from a Linux live CD, mount the server's hard drive, and look for the /boot directory---check there for the kernel and initrd files.
also tell us what the hardware is and what version of Linux.
What happened (or what was changed) before this problem appeared?
Regardless, you can boot up from a Linux live CD, mount the server's hard drive, and look for the /boot directory---check there for the kernel and initrd files.
also tell us what the hardware is and what version of Linux.
@OP, follow this. It seems something misplaced your kernel and the only way to fix now is login using live cd/usb, chroot to your distro's partition:
Code:
# mount /dev/foo /mnt/yourdistro
# mount /dev/foo1 /mnt/yourdistro/boot <---- Note, this step is not required if you don't have a separate boot partition.
# mount --bind /dev /mnt/yourdistro/dev
# mount --bind /sys /mnt/yourdistro/sys
# mount --bind /proc /mnt/yourdistro/proc
# chroot /mnt/yourdistro
Once you do that, you will have access to your system.
Depending on your distro, use the relevant package manager command to reinstall kernel; may be using yum/apt/emerge/whatever.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.