Ben Dugan on 21 Jun 2005 01:16:15 -0000


[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

[PLUG] Corrupted library file name



I was rebooting a system running Redhat 7.3 (old, I know) and I was thrown into the "run fsck manually" path. So I did (run fsck manually) and was confronted with a very large number (>100) errors, bad inodes, etc. On the next reboot, after these repairs, the system is freezing at a point where it looks for libext2fs.so.2.4. I have enough of a system that I can look into the /lib directory, where I see a file with the name: libext2"s.so.4 (that's a quote char between the 2 and the s).


I don't see any other files with bad names like this one, and I'm hoping there's some way I can mv or otherwise correct this name and get this system back on the air, at least long enough to run postgres once to do a pgdump on a database that's on this machine.

Any suggestions?

At the moment I can't find the old 7.3 boot CD, either, though I suppose I might find an iso for this online.

In a related question: How is this device (/dev/hda2) write-protected if mount says its (rw) and I'm superuser?

Ben


___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug