On Mon, 2005-08-22 at 13:22 -0400, Robin Mordasiewicz wrote:
> On Mon, 22 Aug 2005, Johnny Hughes wrote:
> > On Mon, 2005-08-22 at 13:02 -0400, Robin Mordasiewicz wrote:
> >> On Mon, 22 Aug 2005, Dave Gutteridge wrote:
> >>
> >>>> I've had this exact same problem, and I uninstalled yum reinstalled it
> >>>> and it work for a day and then back to the same. I've also had it
> >>>> working temporarily by doing a yum clean-all then yum makecache. But
> >>>> next day it went back to doing the same old hang up. I'm not sure if
> >>>> this is a yum problem or a centos problem.
> >>>>
> >>>
> >>> I was having this exact issue recently. Or at least, Yum was hanging at the
> >>> same stage as what you describe.
> >>>
> >>> It was recommended to me on this list to do the following:
> >>>
> >>> cd /var/lib/rpm
> >>> rm __db.00*
> >>> rpm --rebuilddb
> >>>
> >>> This seems to have cleared up the problem for me. It might work for you.
> >>
> >> Are you running x86_64 ?
> >> Or is anyone here running x86_64 CentOS 4 and having success with yum
> >> update ?
> >
> > I run x86_64 with no problems ...
> > What kind of install is it, Workstation or Server?
> > After the upgrade where RPM is upgraded, it is actually a good idea to
> > rebuild the database.
> > The machine I use to autobuild all updates is an x86_64 machine that
> > runs with 6 chroots.
>
> The install was a kickstart install with mostly defaults. I dont think you
> can specify server/desktop variations in the kickstart, and I dont know if
> that would make a difference, other than default package selection ?
>
Just wondering if you are installing a bunch of i386 stuff (Open Office,
etc., or mostly just x86_64 stuff) It shouldn't matter, you should be
able to install packages and upgrade all the items with no issues.
> I did a default install from the DVD and it should not make the mahcine
> useless to run "yum update"
>
That is true ... useless machines are not part of our goals :)
> I would like to figure out what it is that is broken. I am not an expert
> in this field, and having troubles narrowing it down.
>
Ok, this sounds like some kind of driver issue with SATA. What kernel
are you running (uname -r)?
What kind of machine (model of motherboard and/or machine)?
Do you have the latest BIOS update for the motherboard and the SATA
controller.
Is the controller for the hard drive(s) built onto the motherboard or is
it a separate controller?
Are you running RAID or LVM2 (or both)?
> It is definitely not faulty hardware, although it could be hardware
> incompatibilities, but CentOS-3 worked perfectly fine.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.centos.org/pipermail/centos/attachments/20050822/aa275429/attachment.bin
