[CentOS] RE:tryingtoupgradefromCentos4.0tocurrent--repairRPMdatabase

David Campbell decampbell1 at comcast.net
Sun Aug 21 13:38:32 UTC 2005


ok here is the list
[root at mail /]# ls -l /boot |grep vmlinuz
-rw-r--r--  1 root root 1435513 Jun  8 18:39 vmlinuz-2.6.9-11.EL
-rw-r--r--  1 root root 1433883 Feb 19 20:18 vmlinuz-2.6.9-5.0.3.EL
-rw-r--r--  1 root root 1434068 Apr 19 19:09 vmlinuz-2.6.9-5.0.5.EL
[root at mail /]#

they appear to be there..could they be corrupted?




-----Original Message-----
From: centos-bounces at centos.org [mailto:centos-bounces at centos.org]On
Behalf Of Robert
Sent: Sunday, August 21, 2005 8:44 AM
To: CentOS mailing list
Subject: Re: [CentOS]
RE:tryingtoupgradefromCentos4.0tocurrent--repairRPMdatabase


At some point, your RPM database was screwed, right? Why don't you see
if those three kernels are really installed:

[root at mavis ~]# ls -l /boot | grep vmlinuz
-rw-r--r-- 1 root root 1435513 Jun 8 17:39 vmlinuz-2.6.9-11.EL
-rw-r--r-- 1 root root 1401894 Jun 8 18:33 vmlinuz-2.6.9-11.ELsmp
-rw-r--r-- 1 root root 1433883 Feb 19 19:18 vmlinuz-2.6.9-5.0.3.EL
-rw-r--r-- 1 root root 1400375 Feb 19 20:30 vmlinuz-2.6.9-5.0.3.ELsmp
-rw-r--r-- 1 root root 1434068 Apr 19 18:09 vmlinuz-2.6.9-5.0.5.EL
-rw-r--r-- 1 root root 1400547 Apr 19 18:35 vmlinuz-2.6.9-5.0.5.ELsmp
[root at mavis ~]#

According to your query below, you should have the three files above
that DO NOT end with "smp" and you should be able to boot any of the
three. (Which you indicated earlier didn't work.)
Based on the indications you're giving, that RPM data is still out of
touch with reality.


David Campbell wrote:

>OK I did the rpm -q --qf '[%{name}-%{version}-%{release}.%{arch}\n]' kernel
>
>and got the following
>
>kernel-2.6.9-5.0.3.EL.i686
>kernel-2.6.9-5.0.5.EL.i686
>kernel-2.6.9-11.EL.i686
>
>
>Thanks
>Dave
>
>
>-----Original Message-----
>From: centos-bounces at centos.org [mailto:centos-bounces at centos.org]On
>Behalf Of David Campbell
>Sent: Sunday, August 21, 2005 7:13 AM
>To: CentOS mailing list
>Subject: RE: [CentOS]
>RE:tryingtoupgradefromCentos4.0tocurrent--repairRPMdatabase
>
>
>Hey, Johnny,
>I have a newbie question for you... not that the previous stuff isn't but
>what is the difference between a regular kernel and an smb kernel?
>
>
>-----Original Message-----
>From: centos-bounces at centos.org [mailto:centos-bounces at centos.org]On
>Behalf Of David Campbell
>Sent: Sunday, August 21, 2005 7:01 AM
>To: CentOS mailing list
>Subject: RE: [CentOS] RE:
>tryingtoupgradefromCentos4.0tocurrent--repairRPMdatabase
>
>
>wow... that was scary.. I did the edit, verified that I had no typos. save
>and rebooted... said "file not found".  So had to manually type the load
>sequence in at command line to get the server back up... will verify the
>installed kernels now...
>
>
>
>-----Original Message-----
>From: centos-bounces at centos.org [mailto:centos-bounces at centos.org]On
>Behalf Of Johnny Hughes
>Sent: Sunday, August 21, 2005 6:40 AM
>To: CentOS ML
>Subject: RE: [CentOS] RE: trying
>toupgradefromCentos4.0tocurrent--repairRPMdatabase
>
>
>On Sun, 2005-08-21 at 06:29 -0400, David Campbell wrote:
>
>
>>Ok, thanks.. is there a way I can tell for sure which kernels I have
>>installed. I have tried rpm -i and the 686 kernel name and it says already
>>installed.. tried it with the 586 also and got same results... also tried
>>rpm -e for each and it said "not installed"  though I did the rpm -i again
>>and it said it was, so I found it strange.
>>
>>Thanks
>>
>>Dave
>>
>>
>>
>Use the following commands to see the arches of your installed kernels:
>
>rpm -q --qf '[%{name}-%{version}-%{release}.%{arch}\n]' kernel
>
>and
>
>rpm -q --qf '[%{name}-%{version}-%{release}.%{arch}\n]' kernel-devel
>
>(you would substitute kernel-smp and kernel-smp-devel if you had an smp
>kernel installed)
>
>
>
>>-----Original Message-----
>>From: centos-bounces at centos.org [mailto:centos-bounces at centos.org]On
>>Behalf Of Johnny Hughes
>>Sent: Sunday, August 21, 2005 6:22 AM
>>To: CentOS ML
>>Subject: RE: [CentOS] RE: trying to
>>upgradefromCentos4.0tocurrent--repairRPMdatabase
>>
>>
>>On Sun, 2005-08-21 at 05:59 -0400, David Campbell wrote:
>>
>>
>>>Here is what grub.conf says..
>>>
>>>
>>>
>>># 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/VolGroup00/LogVol00
>>>#          initrd /initrd-version.img
>>>#boot=/dev/hda
>>>default=0
>>>timeout=5
>>>splashimage=(hd0,0)/grub/splash.xpm.gz
>>>hiddenmenu
>>>title CentOS 4.0 (2.6.9-5.0.3.EL)
>>>        root (hd0,0)
>>>        kernel /vmlinuz-2.6.9-5.0.3.EL ro root=/dev/VolGroup00/LogVol00
>>>
>>>
>>rhgb
>>
>>
>>>quiet
>>>        initrd /initrd-2.6.9-5.0.3.EL.img
>>>~
>>>
>>>
>>>
>>>
>>>
>>>Thanks
>>>
>>>Dave
>>>
>>>
>>>
>>>
>>Dave,
>>You need the i686 kernel and not the i586 kernel.
>>
>>Make your grub.conf look like this (leave all the remarked stuff, that
>>begins with #, alone) :
>>
>>default=1
>>timeout=5
>>splashimage=(hd0,0)/grub/splash.xpm.gz
>>hiddenmenu
>>title CentOS 4.0 (2.6.9-5.0.3.EL)
>>        root (hd0,0)
>>        kernel /vmlinuz-2.6.9-5.0.3.EL ro root=/dev/VolGroup00/LogVol00
>>
>>
>rhgb
>
>
>>quiet
>>        initrd /initrd-2.6.9-5.0.3.EL.img
>>
>>title CentOS 4 (2.6.9-11.EL)
>>        root (hd0,0)
>>        kernel /vmlinuz-2.6.9-11.EL ro root=/dev/VolGroup00/LogVol00 rhgb
>>quiet
>>        initrd /initrd-2.6.9-11.EL.img
>>
>>#-----------------------------------------------
>>
>>If, for some reason the new kernel doesn't boot, shift to default=0 in
>>grub.conf.
>>
>>
>>
>>
>>>-----Original Message-----
>>>From: centos-bounces at centos.org [mailto:centos-bounces at centos.org]On
>>>Behalf Of Craig White
>>>Sent: Sunday, August 21, 2005 12:12 AM
>>>To: CentOS mailing list
>>>Subject: RE: [CentOS] RE: trying to upgrade
>>>fromCentos4.0tocurrent--repairRPMdatabase
>>>
>>>
>>>On Sat, 2005-08-20 at 20:21 -0400, David Campbell wrote:
>>>
>>>
>>>>Output is as follows
>>>>
>>>>
>>>>kernel-2.6.9-11.EL
>>>>kernel-2.6.9-5.0.3.EL
>>>>kernel-2.6.9-5.0.5.EL
>>>>kernel-utils-2.4-13.1.66
>>>>kernel-utils-2.4-13.1.48
>>>>
>>>>The only available kernel that shows in the boot is the 2.6.9-5.0.3EL
>>>>
>>>>
>>>----
>>>why not 'cat /boot/grub/grub.conf' and 'ls -l /boot' and we'll give you
>>>the changes to make to /boot/grub/grub.conf
>>>
>>>Craig
>>>
>>>
>
>-- Johnny Hughes
>< http://www.hughesjr.com/ >
>
>
>_______________________________________________
>CentOS mailing list
>CentOS at centos.org
>http://lists.centos.org/mailman/listinfo/centos
>
>_______________________________________________
>CentOS mailing list
>CentOS at centos.org
>http://lists.centos.org/mailman/listinfo/centos
>
>_______________________________________________
>CentOS mailing list
>CentOS at centos.org
>http://lists.centos.org/mailman/listinfo/centos
>
>
>

_______________________________________________
CentOS mailing list
CentOS at centos.org
http://lists.centos.org/mailman/listinfo/centos




More information about the CentOS mailing list