Forums

Resolved
0 votes
Hi.

ClearOS Community release 6.6.0 (Final) i686

The system will not reboot after automatic kernel update late last week.

Feb 20 03:16:28 Updated: kernel-firmware-2.6.32-504.8.1.v6.noarch
Feb 20 03:18:34 Updated: dracut-004-356.el6.noarch
Feb 20 03:18:34 Updated: dracut-kernel-004-356.el6.noarch
Feb 20 03:18:44 Installed: kernel-2.6.32-504.8.1.v6.i686

I found /boot/grub/grub.conf had been updated but there was no initrd entry in the file for the 2.6.32-504.8.1.v6.i686 kernel and the initramfs file (presumabely /boot/initramfs-2.6.32-504.8.1.v6.i686.img) was not generated.

I checked the dracut log and there was nothing for 2.6.32-504.8.1.v6.i686.

I attempted to create the initramfs-2.26.32-504.8.1.v6.i686.img file with dracut using what had been downloaded for 2.6.32-504.8.1.v6 but it results in a file that is half the size of my other initramfs files. Attempting to boot using this file still results in a kernel panic after modules errors.

[log]# cat dracut.log
Sat Feb 21 15:20:32 CST 2015 Info: Executing /sbin/dracut
Sat Feb 21 15:20:32 CST 2015 Err: Will not override existing initramfs (/boot/initramfs-2.6.32-431.23.3.v6.i686.img) without --force
Sat Feb 21 15:24:03 CST 2015 Info: Executing /sbin/dracut -f /boot/initramfs-2.6.32-504.8.1.v6.i686.img 2.6.32-504.8.1.v6.i686
...

How can I create a working initramfs manually or is there something I can download to workaround/fix this?

I do have a system running the x64 version of this kernel 2.6.32-504.8.1.v6.x86_64 which successfully completed the parallel update.

Thanks.
Tuesday, February 24 2015, 10:15 PM
Share this post:
Responses (6)
  • Accepted Answer

    Thursday, February 26 2015, 07:46 PM - #Permalink
    Resolved
    0 votes
    It is not the latest available but is the latest compiled so please can you try installing this driver to replace the r8169 one in the kernel?
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, February 26 2015, 05:01 PM - #Permalink
    Resolved
    0 votes
    Thanks for the info. The machine does have RealTek hardware.

    RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, February 26 2015, 03:11 PM - #Permalink
    Resolved
    0 votes
    The 2.6.32-431 series (RHEL6.5) was not the best kernel series. We held it back on the Professional Edition for quite some time and ended up supplementing it with newer drivers. The 2.6.32-504 series (RHEL 6.6) seems to be much much better so far.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, February 26 2015, 02:30 PM - #Permalink
    Resolved
    0 votes
    Robin,

    By any chance are you on HP hardware with either Intel or Realtek PCI NICs?

    We've had two reports in the last two weeks about kernel panics on this hardware (I'll see if I can get specific models).

    What I do know:

    2.6.32-358.23.2.v6 is OK
    2.6.32-431.23.3.v6 is exhibiting kernel panics
    2.6.32-504.8.1.v6 - I don't have any information at this point in time

    B
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, February 26 2015, 01:08 AM - #Permalink
    Resolved
    0 votes
    Thanks, Tim. That worked great.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, February 25 2015, 12:22 AM - #Permalink
    Resolved
    0 votes
    If you still have the old kernel installed you can select it at boot time to get back to a working system through the boot/grub menu

    To re-create the initramfs / initrd files usually the easiest way is to remove that specific kernel version and just reinstall as they are setup when the kernel package is installed

    yum remove kernel-2.6.32-504.8.1.v6.i686
    yum install kernel-2.6.32-504.8.1.v6.i686

    From memory the ClearOS kernels are built without dracut (default is still to use mkinitrd) and the post-setup script creates initramfs using the /sbin/new-kernel-pkg command. Something like:-
    new-kernel-pkg --mkinitrd --depmod --install 2.6.32-504.8.1.v6.i686
    The reply is currently minimized Show
Your Reply