Kernel Panic After 3.0.2.4 Update

[yuljk]

Hi guys - Performed an update from 3.0.2.3 to 3.0.2.4 - after rebooting I receive a kernel panic.



I can boot using the older kernel from the GRUB menu. Tried the update a couple of times - same issue each time.

Many thanks

[TheGr8Wonder]

When booting from older kernels, how much free space is on all of your volumes?

Is this also a VM or a physical hardware device?

[yuljk]

Many thanks for the prompt response.

Here is the output of df -H

Code: Select all

Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/vg_00-lv_root
                      8.4G  3.1G  4.9G  39% /
tmpfs                 2.1G     0  2.1G   0% /dev/shm
/dev/sda1             508M  166M  316M  35% /boot
/dev/mapper/vg_00-lv_tmp
                      1.1G  2.8M  967M   1% /tmp
/dev/mapper/vg_00-lv_var
                       22G  3.6G   17G  18% /var
none                  2.1G   50k  2.1G   1% /var/spool/MailScanner/incoming

The machine is a VM running on ESXi 6.5 U1 and the virtual machine hardware version is the latest.
Previous updates have applied without issue - first time I've seen a kernel panic when updating.

Regards

[TheGr8Wonder]

Can you run this command as sudo/root, to list all of the kernels on your box?

Code: Select all

rpm -q kernel

[TheGr8Wonder]

I also suggest you take the time to run a health check on all of the volumes within your eFa machine, and fix any potential errors, and attempt the upgrade again. I can give you those commands if you are not sure.

[yuljk]

Kernels installed :-

Code: Select all

kernel-2.6.32-642.13.1.el6.x86_64
kernel-2.6.32-696.el6.x86_64
kernel-2.6.32-696.1.1.el6.x86_64
kernel-2.6.32-696.3.1.el6.x86_64
kernel-2.6.32-696.10.2.el6.x86_64

Do I just run fsck from single user mode for file system integrity checks?

Many thanks for your help!

[TheGr8Wonder]

Not a problem at all!!

You'll want to run the check in single user mode, so it makes sure your device isn't doing anything it shouldn't be. You'll want to run it on all of the volumes you have outlined in your other snippet.

Once that is done, you should also attempt to remove all other kernels except the one you're running, and the one that it is attempting to upgrade to.

[yuljk]

Ran fsck against all volumes after unmounting in single user mode and all reported clean.

Then cleaned up old kernels but 1 with

Code: Select all

package-cleanup --oldkernels --count=1

and finally ran

Code: Select all

rpm -e 'newkernalnamehere'

to get back to just the original kernel.

Update ran and successfully updated!

Many thanks for your assistance, much appreciated.

The traffic graph is excellent by the way - good work guys

[TheGr8Wonder]

Glad it's working now!!

And you're very welcomed!