Shakthi Kannan wrote: > ----- > | What after that, should i go and re-install glibc-2.3.3 along with its > | dependent packages or it is not required ? > \-- > > When you are able to log into the system, just use it. libc is what > you have restored back by copying. Why do you want to re-install? > > I boot the system with Ubuntu x86_64, Live CD, and mounted the root file system (/dev/cciss/c0d0p4) and found ld-linux-x86-64.so.2 was already present. # ls /mnt1/lib64/ld-* ld-2.3.3.so ld-linux-x86-64.so.2 ld-lsb-x86-64.so.1
Then i just copied all the /lib/* and /lib64/* from another system, Then i rebooted and found the above error ##### boot errors### blogd: no message logging because /var file system is not accessible Boot logging started on /dev/tty1(/dev/console) at Thu Nov 29 13:36:25 2007 Master Resource Control: previous runlevel: N, switching to runlevel: 3 Master Resource Control: runlevel 3 has been reached blogd: no message logging because /var file system is not accessible ####### As we had to power down the system (we could't issue any shutdown commands), i thought it might be beacuse FS might have a problem and require manual fsck'ing. Again booted the system with Ubuntu Live CD and run fsck.ext3, e2fsck on all slices, checked the *free file system size, which was ok, and then again try to boot the system. But no luck same error as above given. This time booted the system with SLES 9.0 SP3 and run rescue, and run fsck.ext3/e2fsck once again on all slices inlcuding /var (/dev/cciss/c0d0p6), but same error, this time i also verified /etc/fstab also which appeared to be Ok. Then i move ahead and try to use the "Repair Installed System" option available in the SLES. All the system verification tests passed except that, some of the package could not verified, i tried to repair them (which cause them to re-install), but installation of many of the programs failed! By this time i had a very little hope, time was running away, as this is a key production training system. I started moving the application installation data (installed under (/) FS) to another slices (/dev/cciss/c0d1). Fortunately i had, two big slices (/dev/cciss/c0d1p1 / /dev/cciss/c0d1p2) RAID5, where I moved, most of the data from /dev/cciss/c0d0/p*. I thought not to format any OS slices ( / , /var, /usr) and just re-install SLES 9. But all goes fine except during the RPMs installation the same RPMs (which failed during Repair option) got failed again, to install. Since i had already taken backup, i re-installed the SLES, with format option :( The issue is I still have two boxes with glibc-2.3.3 and glibc-2.6.1 installed host3:/ # rpm -qa|grep -i glib glibc-i18ndata-2.3.3-98.61 glibc-32bit-9-200512100800 glibc-locale-32bit-9-200512100801 glibc-2.6.1-18 glibc-locale-2.3.3-98.61 glib-32bit-9-200501041713 glibc-info-2.3.3-98.61 glibc-devel-2.3.3-98.61 glibc-devel-32bit-9-200512100801 glib-1.2.10-586.2 glibc-2.3.3-98.61 glib2-2.2.3-117.2 glib2-32bit-9-200507121454 glibc-2.4-31.2 Could anyone help, to properly remove glibc-2.6.1 ? Thanks a lot for your patience :) Best regards, Yash _______________________________________________ ilugd mailinglist -- ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd Next Event: http://freed.in - February 22/23, 2008 Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi http://www.mail-archive.com/ilugd@lists.linux-delhi.org/