kernel panic upgrade from 6.4 to 6.7

General support questions
logtech
Posts: 88
Joined: 2010/04/22 18:34:34

kernel panic upgrade from 6.4 to 6.7

Post by logtech » 2015/10/04 01:53:09

I have just get kernel panic when I upgraded from 6.4 to 6.7 please advice.
Attachments
kernel panic.jpg
kernel panic.jpg (108.21 KiB) Viewed 4309 times

logtech
Posts: 88
Joined: 2010/04/22 18:34:34

Re: kernel panic upgrade from 6.4 to 6.7

Post by logtech » 2015/10/04 02:11:24

ok the good news is I can still hit ESC and choose the older kernel. once I am able to boot to that kernel what should I do?

1. use yum remove kernel and then yum update
2. or just change in boot to point to that kernel I am able to boot?

logtech
Posts: 88
Joined: 2010/04/22 18:34:34

Re: kernel panic upgrade from 6.4 to 6.7

Post by logtech » 2015/10/04 02:20:45

I have decided to edit grup and delete the other two kernels that gave me kernel panic leaving the 3rd good working.

Question is if I still have to do "yum remove kernel and then yum update" ?

User avatar
TrevorH
Site Admin
Posts: 33202
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: kernel panic upgrade from 6.4 to 6.7

Post by TrevorH » 2015/10/04 02:40:59

Post the content of the file /boot/grub/grub.conf complete with the entries you were intending to delete.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

logtech
Posts: 88
Joined: 2010/04/22 18:34:34

Re: kernel panic upgrade from 6.4 to 6.7

Post by logtech » 2015/10/04 15:25:33

here we go:

# 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/sda2
# initrd /initrd-[generic-]version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.32-573.7.1.el6.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.32-573.7.1.el6.x86_64 ro root=UUID=d15a753a-53c2-4dc0-973e-27d3be2065cf rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD quiet SYSFONT=latarcyrheb-sun16 rhgb crashkernel=auto KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM
title CentOS (2.6.32-573.el6.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.32-573.el6.x86_64 ro root=UUID=d15a753a-53c2-4dc0-973e-27d3be2065cf rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD quiet SYSFONT=latarcyrheb-sun16 rhgb crashkernel=auto KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM
title CentOS (2.6.32-358.el6.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.32-358.el6.x86_64 ro root=UUID=d15a753a-53c2-4dc0-973e-27d3be2065cf rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD quiet SYSFONT=latarcyrheb-sun16 rhgb crashkernel=auto KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM
initrd /initramfs-2.6.32-358.el6.x86_64.img

User avatar
TrevorH
Site Admin
Posts: 33202
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: kernel panic upgrade from 6.4 to 6.7

Post by TrevorH » 2015/10/04 15:41:35

All your newer kernel entries are missing the initrd line in grub.conf.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

logtech
Posts: 88
Joined: 2010/04/22 18:34:34

Re: kernel panic upgrade from 6.4 to 6.7

Post by logtech » 2015/10/07 20:28:45

is there any way to find out the correct one and place in grub ?

gerald_clark
Posts: 10642
Joined: 2005/08/05 15:19:54
Location: Northern Illinois, USA

Re: kernel panic upgrade from 6.4 to 6.7

Post by gerald_clark » 2015/10/07 21:49:41

A "yum remove" of the bad kernel followed by a "yum install" of the same kernel should rebuild the initrd unless you are out of room in /boot.

User avatar
AlanBartlett
Forum Moderator
Posts: 9345
Joined: 2007/10/22 11:30:09
Location: ~/Earth/UK/England/Suffolk
Contact:

Re: kernel panic upgrade from 6.4 to 6.7

Post by AlanBartlett » 2015/10/07 22:02:14

logtech wrote:is there any way to find out the correct one and place in grub ?
Take a look to see which initramfs-*.el6.x86_64.img files currently exist in your /boot/ directory --

ls -l /boot/initramfs*

If there is only the one, initramfs-2.6.32-358.el6.x86_64.img, then you will need to re-create the ones currently missing.

Looking at the contents of your /etc/grub.conf file and assuming that there is no initramfs-2.6.32-573.7.1.el6.x86_64.img file within the /boot/ directory you would need to issue the following command --

dracut -f /boot/initramfs-2.6.32-573.7.1.el6.x86_64.img 2.6.32-573.7.1.el6.x86_64

Then re-check the contents of your /etc/grub.conf file and assuming success, repeat the step for the other kernel (2.6.32-573.el6.x86_64).

It might be wise for you to consult the dracut manual page so that you understand the commands that you will be issuing --

man dracut

Also, for information purposes, you will find that there is a /var/log/dracut.log which contains a record of all invocations of the dracut command.
Image 100% Linux and, previously, Unix. Co-founder of the ELRepo Project.

logtech
Posts: 88
Joined: 2010/04/22 18:34:34

Re: kernel panic upgrade from 6.4 to 6.7

Post by logtech » 2015/10/08 01:11:57

Thank You Alan,

I think I should be ok since:

[root@MYSERVER~]# ls -l /boot/initramfs*
-rw-r--r--. 1 root root 15507515 Mar 11 2015 /boot/initramfs-2.6.32-358.el6.x86_64.img
[root@MYSERVER~]# more /etc/grub.conf
# 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/sda2
# initrd /initrd-[generic-]version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.32-358.el6.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.32-358.el6.x86_64 ro root=UUID=d15a753a-53c2-4dc0-973e-27d3be2065cf rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD quiet SYSFONT=latarcyrheb-sun16 rhgb crashkernel=auto KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM
initrd /initramfs-2.6.32-358.el6.x86_64.img
[root@MYSERVER~]#

Looks like all is ok, and now it boots ok. Thank You Very Much for Your help. -Logtech

Post Reply