upgrade glibc destroy my box

hi all:
i have a rhl 9.0 box .today i try to upgrade glibc2.3.2-11.9 to
glibc-2.3.2-27.9 so i type the commond as follow
#rpm -Fvh glibc-common-2.3.2-27.9.i386.rpm glibc-2.3.2-27.9.i386.rpm
prepaing ============================100%
1 glibc-common=========================50%
2 glibc================================100%
error %(post) ...... (i forgot it ) ,exit status 121.
then i found many softwares not work with a error "Segment fault" .so i reboot it but when it loaded
INIT enter level 5
Id "1" respawning too fast: disabled for 5 minutes"
....
Id "5" respawning too fast: disabled for 5 minutes"
messages and the system hangs

i boot in rescue mode.then want to reinstall glibc
with
#rpm -Uvh --oldpackage glibc-common-2.3.2-11.9.i386.rpm glibc-2.3.2-11.9.i386.rpm --root=/mnt/sysimage
preparing ================================100%
1 glibc-common=============================100%
2 glibc====================================100%
rpmdb: /var/lib/rpm/Basenames:No such file or directory
rpmdb:/var/lib/rpm/Basenames:cannot sync:no such file or
directory
error:db4 error(1) from dbenv->close No such file or directory

i have search this problem in forum.
but i cant fix it .
so how can i fix it
it made me mad

thank you in advance

and
#chroot /mnt/sysimage
segment fault

try to run ldconfig
and maybe try rpm --rebuilddb

However, it sounds pretty serious

I'm seeing the same thing while trying to update glibc. At first I was blaming the Promise FastTrak SX4000 ata raid which I just got working, but now I'm not so sure. I have updated glibc on another RH9 server without incident. The server with the problem is also using lvm in addition to the raid card.

Are you using FastTrak raid or lvm by any chance?

I haven't found any way to fix the problem once it occurs except a complete re-install of the OS. Maybe someone out there has a better idea.

Finally found the solution in another thread (http://www.linuxquestions.org/questi...threadid=57607). The problem has nothing to do with the FastTrak SX4000 or lvm. There appears to be a bug in up2date that downloads the i386 glibc rpm instead of the i686 rpm. If you have a xeon processor like I do, you need to manually download and install the i686 glibc rpm. Working great now. The thread above also has the recovery procedure to restore glibc without having to re-install like I did.