set_thread_area failed when setting up thread-local storage

Hi,
I am facing a problem on FC3. I was upgrading glibc and relative components to version 4. During upgrade, rpm failed to continue and end up with cannot set up thread-local storage: set_thread_area failed when setting up thread-local storage. Now each command execute on box resulting me cannot set up thread-local storage: set_thread_area failed when setting up thread-local storage. So far i searched, i came to know that there is difference b/w FC3 and FC4 to handle threads. And i think this caused system to fail.
Is there any way, i can restore my system ? btw rpm i installing was from FC4 and FC devel. And screwed up machine is UML VM.

~Nadeem

you need to boot from a recovery disk and enter rescue mode use the disks version of rpm to force the installation of the original glibc.
something like this
rpm -e glibc* --root /mnt/sysimage --nodeps
then (adjust path and package names as neede of course)
rpm -Uvh /mnt/sources/RedHat/RPMS/glibc-x.x.x.i386.rpm --nodeps
rpm -Uvh /mnt/sources/RedHat/RPMS/glibc-common-x.x.x.i386.rpm --nodeps
rpm -Uvh /mnt/sources/RedHat/RPMS/glibc-devel-x.x.x.i386.rpm --nodeps
rpm -Uvh /mnt/sources/RedHat/RPMS/glibc-kernheaders-x.x.x.i386.rpm --nodeps

reboot might have to redo /etc/ld.so.conf


if you want to do it by hand boot from a recovery disk and cd to
/mtn/sysimage/lib or whatever and manually restore all the symbolic links to the older glibc libraries.

some stuff still won't work because you overwrote libpthread and this includes make
so build a static version of make and rebuild old glibc and install then rebuild non static make.

Originally Posted by foo_bar_foo you need to boot from a recovery disk and enter rescue mode use the disks version of rpm to force the installation of the original glibc. something like this rpm -e glibc* --root /mnt/sysimage --nodeps then (adjust path and package names as neede of course) rpm -Uvh /mnt/sources/RedHat/RPMS/glibc-x.x.x.i386.rpm --nodeps rpm -Uvh /mnt/sources/RedHat/RPMS/glibc-common-x.x.x.i386.rpm --nodeps rpm -Uvh /mnt/sources/RedHat/RPMS/glibc-devel-x.x.x.i386.rpm --nodeps rpm -Uvh /mnt/sources/RedHat/RPMS/glibc-kernheaders-x.x.x.i386.rpm --nodeps reboot might have to redo /etc/ld.so.conf

Thanks a lot for reply. Actually i already did that. But problem left is to reboot. As this a UML VM and i don't know much about VM. btw i did force rpm install by mounting its FS structure on host machine and then chroot to it. Now i am looking into UML How to ...

~Nadeem