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.
I get:
Kernal Panic: not syncing: VFS: Unable to mount root fs on unknown-block(8,3)
and the process stops. I have to turn off the computer and go back and select "2.6.31-15 generic"
What is going on and what do I need to do to get back to 17 generic version?
I don't know enough about Ubuntu to know what to investigate or how to fix it. But I think I have a basic idea of the situation. The post from Web31337 seems to be assuming an entirely different situation.
You did an update within Ubuntu that included a newer version of the kernel. A backup copy of the previous working kernel was kept in case something went wrong with that update. Now something is wrong with the newer kernel and/or files it depends on. But the older kernel is OK.
Do you know whether the newer kernel (2.6.31-17) ever worked on your system? Or did it break on the very first reboot after it was installed?
I expect you are using GRUB2 and I only know GRUB, so I can't tell you how to check the actual commands that lie behind those boot time menu choices. For GRUB, all that is in a file /boot/grub/menu.lst that you could copy into a post here. That would answer everything Web31337 asked (in case there is something legit in those questions) as well as narrowing the focus for what else should be investigated.
Hello,
I am not sure what Web1337 is asking in #1 or #2 Sorry for my ignorance.
But, jonsfine, it was working in (2.6.31-16) then an update came it installed (2.6.31-17) which worked for a few sessions then not. Through trial and error I discovered I could run it again on the older version (2.6.31-15).
I appreciate the quick response from you both. Thank you.
Grub is the bootloader software which starts your computer operating system on most Linux systems. Grub2 is a newer version of Grub that is currently used only on a few distributions of Linux, Ubuntu derivates are some. If your earlier kernel worked there is no reason to update it. You update if you are having problems or if the newer kernel has something you want/need that the older one does not.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.