LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Red Hat (http://www.linuxquestions.org/questions/red-hat-31/)
-   -   Strange kernel issue after update - RHEL3 ES (http://www.linuxquestions.org/questions/red-hat-31/strange-kernel-issue-after-update-rhel3-es-411326/)

FishR 02-03-2006 02:10 PM

Strange kernel issue after update - RHEL3 ES
 
Hello all,

I am seeing a very strange issue and two boxes after recently installing the latest kernel (2.4.21-37.0.1) released for RHEL 3 via up2date.

Box 1: The kernel in use isnít even listed in /boot and cannot be found anywhere on the server (see below)

[root@box01 root]# uname -r
2.4.21-32.0.1.ELsmp

[root@box01 root]# ll /boot
total 21472
-rw-r--r-- 1 root root 48736 Jan 11 18:59 config-2.4.21-37.0.1.EL
-rw-r--r-- 1 root root 48851 Jan 11 18:51 config-2.4.21-37.0.1.ELsmp
-rw-r--r-- 1 root root 48736 Sep 7 13:40 config-2.4.21-37.EL
-rw-r--r-- 1 root root 48851 Sep 7 13:34 config-2.4.21-37.ELsmp
drwxr-xr-x 2 root root 4096 Aug 1 2005 grub
-rw-r--r-- 1 root root 288674 Jan 26 11:32 initrd-2.4.21-37.0.1.EL.img
-rw-r--r-- 1 root root 295233 Jan 26 11:32 initrd-2.4.21-37.0.1.ELsmp.img
-rw-r--r-- 1 root root 288578 Oct 11 11:55 initrd-2.4.21-37.EL.img
-rw-r--r-- 1 root root 295019 Oct 11 11:56 initrd-2.4.21-37.ELsmp.img
-rw-r--r-- 1 root root 547 Jun 15 2005 kernel.h
-rw-r--r-- 1 root root 578715 Jan 11 18:59 System.map-2.4.21-37.0.1.EL
-rw-r--r-- 1 root root 606200 Jan 11 18:51 System.map-2.4.21-37.0.1.ELsmp
-rw-r--r-- 1 root root 578588 Sep 7 13:40 System.map-2.4.21-37.EL
-rw-r--r-- 1 root root 606073 Sep 7 13:34 System.map-2.4.21-37.ELsmp
-rwxr-xr-x 1 root root 2908628 Jan 11 19:00 vmlinux-2.4.21-37.0.1.EL
-rwxr-xr-x 1 root root 3547796 Jan 11 18:52 vmlinux-2.4.21-37.0.1.ELsmp
-rwxr-xr-x 1 root root 2908624 Sep 7 13:40 vmlinux-2.4.21-37.EL
-rwxr-xr-x 1 root root 3543696 Sep 7 13:34 vmlinux-2.4.21-37.ELsmp
-rw-r--r-- 1 root root 1252578 Jan 11 18:59 vmlinuz-2.4.21-37.0.1.EL
-rw-r--r-- 1 root root 1365912 Jan 11 18:51 vmlinuz-2.4.21-37.0.1.ELsmp
-rw-r--r-- 1 root root 1252644 Sep 7 13:40 vmlinuz-2.4.21-37.EL
-rw-r--r-- 1 root root 1363903 Sep 7 13:34 vmlinuz-2.4.21-37.ELsmp


-----------------------------------------------------------------------------

Box 2: The kernel in use is still installed on the box but the latest one isnít being chosen by default when the box is rebooted.

[root@box02 root]# uname -r
2.4.21-32.0.1.EL

[root@box02 root]# ll /boot
total 45368
-rw-r--r-- 1 root root 48399 Aug 18 2004 config-2.4.21-20.EL
-rw-r--r-- 1 root root 48543 Dec 20 2004 config-2.4.21-27.0.1.EL
-rw-r--r-- 1 root root 48543 Jan 12 2005 config-2.4.21-27.0.2.EL
-rw-r--r-- 1 root root 48617 May 17 2005 config-2.4.21-32.0.1.EL
-rw-r--r-- 1 root root 48736 Jan 11 18:59 config-2.4.21-37.0.1.EL
-rw-r--r-- 1 root root 48851 Jan 11 18:51 config-2.4.21-37.0.1.ELsmp
-rw-r--r-- 1 root root 48736 Sep 7 13:40 config-2.4.21-37.EL
-rw-r--r-- 1 root root 48851 Sep 7 13:34 config-2.4.21-37.ELsmp
-rw-r--r-- 1 root root 48022 Oct 3 2003 config-2.4.21-4.EL
drwxr-xr-x 2 root root 1024 Feb 2 10:41 grub
-rw-r--r-- 1 root root 173468 Oct 29 2004 initrd-2.4.21-20.EL.img
-rw-r--r-- 1 root root 173108 Jan 3 2005 initrd-2.4.21-27.0.1.EL.img
-rw-r--r-- 1 root root 177270 Feb 23 2005 initrd-2.4.21-27.0.2.EL.img
-rw-r--r-- 1 root root 177364 Jun 3 2005 initrd-2.4.21-32.0.1.EL.img
-rw-r--r-- 1 root root 176762 Feb 2 10:40 initrd-2.4.21-37.0.1.EL.img
-rw-r--r-- 1 root root 178364 Feb 2 10:40 initrd-2.4.21-37.0.1.ELsmp.img
-rw-r--r-- 1 root root 177520 Oct 11 12:06 initrd-2.4.21-37.EL.img
-rw-r--r-- 1 root root 179327 Oct 11 12:06 initrd-2.4.21-37.ELsmp.img
-rw-r--r-- 1 root root 173801 Oct 29 2004 initrd-2.4.21-4.EL.img
-rw-r--r-- 1 root root 543 Feb 2 10:16 kernel.h
drwx------ 2 root root 12288 Oct 29 2004 lost+found
-rw-r--r-- 1 root root 23108 Sep 11 2003 message
-rw-r--r-- 1 root root 21282 Sep 11 2003 message.ja
lrwxrwxrwx 1 root root 27 Feb 2 10:16 System.map -> System.map-2.4.21-32.0.1.EL
-rw-r--r-- 1 root root 574734 Aug 18 2004 System.map-2.4.21-20.EL
-rw-r--r-- 1 root root 575960 Dec 20 2004 System.map-2.4.21-27.0.1.EL
-rw-r--r-- 1 root root 576055 Jan 12 2005 System.map-2.4.21-27.0.2.EL
-rw-r--r-- 1 root root 577960 May 17 2005 System.map-2.4.21-32.0.1.EL
-rw-r--r-- 1 root root 578715 Jan 11 18:59 System.map-2.4.21-37.0.1.EL
-rw-r--r-- 1 root root 606200 Jan 11 18:51 System.map-2.4.21-37.0.1.ELsmp
-rw-r--r-- 1 root root 578588 Sep 7 13:40 System.map-2.4.21-37.EL
-rw-r--r-- 1 root root 606073 Sep 7 13:34 System.map-2.4.21-37.ELsmp
-rw-r--r-- 1 root root 570887 Oct 3 2003 System.map-2.4.21-4.EL
-rwxr-xr-x 1 root root 2892240 Aug 18 2004 vmlinux-2.4.21-20.EL
-rwxr-xr-x 1 root root 2896340 Dec 20 2004 vmlinux-2.4.21-27.0.1.EL
-rwxr-xr-x 1 root root 2900436 Jan 12 2005 vmlinux-2.4.21-27.0.2.EL
-rwxr-xr-x 1 root root 2904532 May 17 2005 vmlinux-2.4.21-32.0.1.EL
-rwxr-xr-x 1 root root 2908628 Jan 11 19:00 vmlinux-2.4.21-37.0.1.EL
-rwxr-xr-x 1 root root 3547796 Jan 11 18:52 vmlinux-2.4.21-37.0.1.ELsmp
-rwxr-xr-x 1 root root 2908624 Sep 7 13:40 vmlinux-2.4.21-37.EL
-rwxr-xr-x 1 root root 3543696 Sep 7 13:34 vmlinux-2.4.21-37.ELsmp
-rwxr-xr-x 1 root root 2900380 Oct 3 2003 vmlinux-2.4.21-4.EL
-rw-r--r-- 1 root root 1243768 Aug 18 2004 vmlinuz-2.4.21-20.EL
-rw-r--r-- 1 root root 1248105 Dec 20 2004 vmlinuz-2.4.21-27.0.1.EL
-rw-r--r-- 1 root root 1248207 Jan 12 2005 vmlinuz-2.4.21-27.0.2.EL
-rw-r--r-- 1 root root 1252854 May 17 2005 vmlinuz-2.4.21-32.0.1.EL
-rw-r--r-- 1 root root 1252578 Jan 11 18:59 vmlinuz-2.4.21-37.0.1.EL
-rw-r--r-- 1 root root 1365912 Jan 11 18:51 vmlinuz-2.4.21-37.0.1.ELsmp
-rw-r--r-- 1 root root 1252644 Sep 7 13:40 vmlinuz-2.4.21-37.EL
-rw-r--r-- 1 root root 1363903 Sep 7 13:34 vmlinuz-2.4.21-37.ELsmp
-rw-r--r-- 1 root root 1236945 Oct 3 2003 vmlinuz-2.4.21-4.EL

None of the other 8 boxes I installed this kernel on are experiencing this issue.

On these two I had to clean up /boot prior to installing the new kernel so Iím wondering if I didnít remove files properly OR just completely screwed something up that can hopefully be corrected easily.

Any thoughts? Also, what is the correct way to clean up /boot when it gets full?

Thank you in advance.
-Ryan

ppuru 02-03-2006 02:49 PM

how is /boot doing on diskspace (df -h) on the erratic servers

FishR 02-03-2006 02:57 PM

Quote:

Originally Posted by ppuru
how is /boot doing on diskspace (df -h) on the erratic servers

Box1
21MB in use (not sure how full this is as the mount isn't listed when I enter df -h)

Box2
49MB in use (52% in use)

ppuru 02-03-2006 04:08 PM

to check the kernels that exist on your system, use the rpm command

rpm -q kernel

Be very careful when you remove the kernel packages. If you remove all of them ... (not sure if this is possible, never tried), you will never be able to boot up your server.

FishR 02-03-2006 05:53 PM

Quote:

Originally Posted by ppuru
to check the kernels that exist on your system, use the rpm command

rpm -q kernel

Be very careful when you remove the kernel packages. If you remove all of them ... (not sure if this is possible, never tried), you will never be able to boot up your server.

When I've cleared up /boot all I've ever done is remove all files relating to kernels older than the past 2 or 3. This is the first time I've ever experienced any issues with it though. Is there some "special" way to do it properly???

ppuru 02-03-2006 06:02 PM

rpm -e is the command to remove a package.


All times are GMT -5. The time now is 06:31 PM.