Community Forum

Tim
Tim
Offline
Resolved
0 votes
After installing updates and rebooting the machine I now get:

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

I have installed the machine twice now - I checked the hardware using the HP tools for my ML110G5 before my second install.

ClearOS runs fine in gateway mode until I install updates. Then it fails on boot.

Any idea why?
Monday, October 01 2012, 01:30 PM
Share this post:
Responses (9)
  • Accepted Answer

    Saturday, January 05 2013, 06:54 PM - #Permalink
    Resolved
    0 votes
    Ah! Update... :) The actual fix is in this post: 6.3.0 Install Latest Updates, Reboot, Kernel Panic - Unable to mount root fs
    Answer as provided by " Michael Sporer " - Thanks! B)
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, January 05 2013, 06:28 PM - #Permalink
    Resolved
    0 votes
    How do we boot into the old kernel, when it's unbootable?
    The reply is currently minimized Show
  • Accepted Answer

    bminux
    bminux
    Offline
    Wednesday, October 03 2012, 10:09 AM - #Permalink
    Resolved
    0 votes
    hello,

    Just boot with the old kernel and then --> yum reinstall kernel.x86_64

    The first two lines are in the config file /etc/grub.conf

    bminux.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, October 03 2012, 09:38 AM - #Permalink
    Resolved
    0 votes
    Would somebody be so kind as to spell out bminux's answer just a little more? I'm having this frustrating issue as well, and I didn't quite understand what he meant by the first two lines,

    "Grub.conf nok. Line --> initrd /initramfs-2.6.32-279.5.2.v6.x86_64.img not present.

    file /boot/initramfs-2.6.32-279.5.2.v6.x86_64.img not present.

    yum reinstall kernel.x86_64."

    I grasp the third line. What are the first two lines instructing me to do? And we're doing this when booted to the old kernel or to rescue mode off media?

    Thanks all!
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, October 03 2012, 09:27 AM - #Permalink
    Resolved
    0 votes
    Thanks for that.

    Worked a treat.
    The reply is currently minimized Show
  • Accepted Answer

    bminux
    bminux
    Offline
    Wednesday, October 03 2012, 08:50 AM - #Permalink
    Resolved
    0 votes
    Hello,

    Same issue.

    Grub.conf nok. Line --> initrd /initramfs-2.6.32-279.5.2.v6.x86_64.img not present.

    file /boot/initramfs-2.6.32-279.5.2.v6.x86_64.img not present.

    yum reinstall kernel.x86_64.

    --> OK.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, October 03 2012, 07:57 AM - #Permalink
    Resolved
    0 votes
    Thanks for the reply, unfortunately it didn't work for me.

    No errors were reported following those steps but I'm still experiencing exactly the same problem, although for now I have edited my grub.conf to default to the previous kernel version which is working o.k. as a temporary fix.

    Any more ideas?
    The reply is currently minimized Show
  • Accepted Answer

    georger
    georger
    Offline
    Wednesday, October 03 2012, 02:31 AM - #Permalink
    Resolved
    0 votes
    Andrew Mills wrote:
    I am having exactly the same problem (kernel 2.6.32-279.5.2.v6.x86_64).

    I am able to boot by selecting the previous version (kernel 2.6.32-279.2.1.v6.x86_64) at startup.

    I have noticed that GRUB uses an initrd image for the previous version but not for the new version, not sure if that has anything to do with it or not.

    Also, I have both the /boot and / partitions configured with software RAID and not sure if that is contributing to the problem.

    Any help greatly appreciated.

    I recall having a similar problem on 5.2... Install, update, reboot, fail.
    I solved it following advice I found on another thread:
    1. Boot from CD and start rescue mode
    2. Allow the rescue program to detect the partitions and run the following commands:

    grub
    root (hd0,0)
    setup (hd0)
    quit
    exit

    Haven't tested with v6. YMMV.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, October 02 2012, 11:32 AM - #Permalink
    Resolved
    0 votes
    I am having exactly the same problem (kernel 2.6.32-279.5.2.v6.x86_64).

    I am able to boot by selecting the previous version (kernel 2.6.32-279.2.1.v6.x86_64) at startup.

    I have noticed that GRUB uses an initrd image for the previous version but not for the new version, not sure if that has anything to do with it or not.

    Also, I have both the /boot and / partitions configured with software RAID and not sure if that is contributing to the problem.

    Any help greatly appreciated.
    The reply is currently minimized Show
Your Reply