[SOLVED] FC 15 will not boot after upgrade kernel panic?
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Finished a successful preupgrade from FC 14 to FC15 but now the system fails to boot the new FC15 kernel 126.96.36.199-27.fc15.i686 and leave me with a flashing Caps and Scroll Lock key lights. Hitting any key on te keyborad causes the entire system to freeze and needs a power off and on to restart it.
How do I resolve this issue? Screen photo of the boot up error attached.
# grub.conf generated by anaconda
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/hda3
# initrd /initrd-version.img
title Fedora (188.8.131.52-27.fc15.i686)
kernel /vmlinuz-184.108.40.206-27.fc15.i686 ro root=LABEL=/root rhgb quiet resume=/dev/sda2 SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us rootfstype=ext4
title Fedora (220.127.116.11-91.fc14.i686)
kernel /vmlinuz-18.104.22.168-91.fc14.i686 ro root=LABEL=/root rhgb quiet resume=/dev/sda2 SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us rootfstype=ext4
title Fedora (22.214.171.124-90.fc14.i686)
kernel /vmlinuz-126.96.36.199-90.fc14.i686 ro root=LABEL=/root rhgb quiet resume=/dev/sda2 SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us rootfstype=ext4
The other kernels will not boot any longer. The server hangs while it's booting. I CAN boot the FC15 live cd though can I do it from that and can you detail the process as I've never done this before and also there is an initrd-plymouth.img there. Is that usable?
I doubt that it is, but I'm really not sure whether initrd-plymouth.img will work. I have my doubts. I know that you can't use root=UUID in grub withot an initrd, and I'm guessing the same is true for root=LABEL either.
The one that you are looking at is for the live CD.
Here is the step by step procedure:
1. Boot using live CD.
2. Open up console.
3. df -h and see if you see your system's boot directory there. If yes then cd /boot
4. Check if you see any image file in there. If yes let us know which image file you see there.
5. If not then continue with the creation of one using the command mentioned before.
6. After creation of image file, add the following line in /boot/grub/grub.conf:
title Fedora (188.8.131.52-27.fc15.i686) will be there already
root (hd0,0) will be there already
kernel /vmlinuz-184.108.40.206-27.fc15.i686 ro root=LABEL=/root rhgb quiet resume=/dev/sda2 SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us rootfstype=ext4 will be there already
initrd /name_of_the_newly_create_image_file Add this one.
You can check the syntax with the initrd given for Fedora 14 in the same file. Just check your first post in which you mentioned that.
Edit: You can also create initial RAMFS for your kernel using this command: mkinitrd vmlinuz-220.127.116.11-27.fc15.i686
Last edited by T3RM1NVT0R; 05-29-2011 at 03:50 PM.
As root now - I do not see a /boot directory only the /media/_boot one. But I can cd into /boot
and there is no image file there. Running
mkinitrd --fstab=/etc/fstab --image-version.
From there gives me the syntax usage output but no img file
Similar results from /media/_boot when substituting /media/_root/etc/fstab