Greetingz ,
I am relatively new to the Linux platform and I am having trouble dealing with this hard drive malfunction. I am running Fedora Core 4 Stentz(2.6) on an Athlon 2400. After I heard a horrible screeching noise coming from my hard drive. I shut down the system to let it cool off. Once I reboot the drive seems to be fine but the system would give the error:

/usr/bin/rhgb-client: error while loading shared libraries: libglib-2.0.so.0: Input/Output Error

then the system forced an integrity check with fsck, which failed saying I need to run it manually.

After running fsck manually with the -y option the system boots but now

"/usr/bin/rhgb-client: error while loading shared libraries: libglib-2.0.so.0: No such file or directory"

is flooding the screen. (along with various other missing lib files during boot)

I tried to re-install libglib rpm from the cd-rom however rpm gives me the error:

rpm: error while loading shared libraries: libpopt.so.0: cannot open shared object file: No such file or directory

It appears my shared libraries became corrupt and I am uncertain as to how I can repair/re-install them.

also bash gives me the message:

-bash: dircolors: command not found

I've tried booting linux rescue, however I am not sure what to do from there.

Please let me know if you need more information. Also be descriptive as I am new to the wonderful Linux environment

ThankYou,
EleetistDeletist
-------------------------------------------------
**The Object of the Game is to End the Game**
**I Think, Therefore I Am Confused**
----------------------------------------------

I hate to be the bearer of bad news, but you really aren't going to head anywhere good there are you? firstly it sounds like there's a physical drive problem, which will never be fixed, but also as you're new to it all, recovering from an issue that deep really isn't going to happen, there could be so many individual things going on there. I could suggest that once you're in rescue mode you search for existing installations and then try a "chroot /mnt/sysimage" and try then to reinstall that rpm. Note that rhgb is just that bloated bootup screen that serves no useful purpose at all. but really, buy a new drive, and reinstall. if you have valuable data on that drive, then you may well be able to recover it running it temporarily as a slave drive.