I did use it from the system menu. It changed lilo conf to uuid only not fstab. No they haven't move the partitions around as they are just users not computer knowledgeable at all. It is one hard drive and not easily removed.

I studied the link more that I provided in my original post until I understood what was going on. I then did the steps to change fstab and lilo config to use UUID and it works! I got the system to boot up finally!

Here is the link again in case anyone is wondering:
https://www.slacky.eu/forum ...

Specifically the command was:

The comand to reinstall glibc....had to add on the packages directory cause that was missing in the comand thenktor posted. Also expanded the command like he said to what version of glibc was in the directory. So like I said it started to work and then threw that error.

I tried the command again and this time it starts to act like it's going to reinstall...then I get the following:

ldconfig did not correct the error. Still recieving the same error as originally reported.

I tried running that command to upgrade/reinstall glibc but it says file does not exist. Is that the correct command? The reason I ask is that when I go into that directory and do ls I see glibc in there. I see glibc-2.13-x86_64-6_slack13.37.txz. running ldconfig now.

Nothing has been erased as far as I can tell. /sbin/init is there in sda1. lilosetup.py did not produce anything different ...no extended verbiage or anything. Now my friend is saying that they applied all updates before rebooting :evil: So, the story changed and the truth came out. Can you provide ...

fsck did not resolve the problem. What next?

Running fsck now. It's at 29% and going slowly. Will post results when finished. Thank you everyone for your help so far!