On 9 August 2010 12:08, James Bensley <jwbensley@xxxxxxxxx> wrote:
> Hi Keith, thanks for your detailed reply. I haven't tried this yet..
>
> What I have done is follow this tutorial to build the latest kernel
> (http://wiki.centos.org/HowTos/Custom_Kernel) which in the end game me
> an rpm of it for installation however when it came to install the rpm
> the follow was displayed;
>
> package kernel-2.6.18-194.8.1.el5.x86_64 is already installed
> file /boot/.vmlinuz-2.6.18-194.8.1.el5.hmac from install of
> kernel-2.6.18-194.8.1.el5.x86_64 conflicts with file from package
> kernel-2.6.18-194.8.1.el5.x86_64
> file /boot/System.map-2.6.18-194.8.1.el5 from install of
> kernel-2.6.18-194.8.1.el5.x86_64 conflicts with file from package
> kernel-2.6.18-194.8.1.el5.x86_64
> file /boot/config-2.6.18-194.8.1.el5 from install of
> kernel-2.6.18-194.8.1.el5.x86_64 conflicts with file from package
> kernel-2.6.18-194.8.1.el5.x86_64
> file /boot/symvers-2.6.18-194.8.1.el5.gz from install of
> kernel-2.6.18-194.8.1.el5.x86_64 conflicts with file from package
> kernel-2.6.18-194.8.1.el5.x86_64
> file /boot/vmlinuz-2.6.18-194.8.1.el5 from install of
> kernel-2.6.18-194.8.1.el5.x86_64 conflicts with file from package
> kernel-2.6.18-194.8.1.el5.x86_64
>
>
> However none of these files exist in /boot?
>
> [nf5002@eros ~]$ ls -la /boot
> total 5727
> drwxr-xr-x 4 root root 1024 Aug 9 12:04 .
> drwxr-xr-x 25 root root 4096 Aug 9 11:46 ..
> -rw-r--r-- 1 root root 62395 Jun 11 2008 config-2.6.18-92.el5
> drwxr-xr-x 2 root root 1024 Aug 9 11:34 grub
> -rw------- 1 root root 2544058 Oct 27 2008 initrd-2.6.18-92.el5.img
> drwx------ 2 root root 12288 Oct 27 2008 lost+found
> -rw-r--r-- 1 root root 80032 Nov 22 2007 message
> -rw-r--r-- 1 root root 92749 Jun 11 2008 symvers-2.6.18-92.el5.gz
> -rw-r--r-- 1 root root 1162656 Jun 11 2008 System.map-2.6.18-92.el5
> -rw-r--r-- 1 root root 1859484 Jun 11 2008 vmlinuz-2.6.18-92.el5
>
> This must some how relate to the fact the boot is on a different
> device, so where does CentOS think /boot is? I mean, the system is
> booting, has been for a few years so its working? If I unmount /boot I
> can't ls /boot, its empty?
>
> [nf5002@eros ~]$ df -h
> Filesystem Size Used Avail Use% Mounted on
> /dev/sda1 28G 8.3G 18G 33% /
> /dev/sdb1 119M 12M 103M 10% /boot
>
> /dev/sda2 is a 3.3TB ext4 partition, so /dev/sda uses GPT hence /boot
> being on a seperate device.
>
> --
> Regards,
> James.
>
> http://www.jamesbensley.co.cc/
>
> There are 10 kinds of people in the world; Those who understand
> Vigesimal, and J others...?
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
>
Okay James let's take a step back for a minute....
Your previous posts do show kernel-2.6.18-194.8.1.el5 as being
installed so far as the RPM database is aware but your /boot listing
and grub config do not show it....
Unless you have *very* specific circumstances there is no need to roll
your own kernel and in terms of easing support it is preferred to use
the vendor kernel and kmods for any modules not part of it that are
required....
Does verifying the kernel RPM show anything missing?
rpm -V kernel-2.6.18-194.8.1.el5
*So long as* uname does not show the kernel version as the current one
try to do:
yum reinstall kernel-2.6.18-194.8.1.el5
This *should* reinstall that kernel and with the files in place grubby
should pick it up in the grub rebuild...
After reinstalling the kernel check grub.cfg and /boot and see if they
are pointing to the most recent kernel.
Once you are on that we can work on the ext4 issue (following the
advice in the RHEL release note advisories). So long as your kernel
version is old it will cause issues with such recent development.
James
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
