me@prestoncrawford.com wrote:

I don't know why I'm having this problem, but I know I didn't have it with Fedora. Basically I installed a couple days ago. Upon reboot one time I got an error stating something to the effect that libc.so.6 was unable to receive messages of type LHS or something like that. I added a second hard drive (to separate data from the OS) in case this happened again and I reinstalled. Well, it happened again this morning, just a couple days later. No idea why. But when it happens I can't recover the system. I can't update the system. All I can do is reinstall. Anything that uses Glibc (pretty much everything) quits functioning and gives this error.

Anyone else seen this? I can't imagine that this would be a hardware problem. I did a memory test the first time and all the memory checked out. I'm running on a new hard drive now (with the old one being a data drive like I said earlier). So I can't imagine that would be the problem. But for whatever reason the files for libc get hosed so the OS just quits working.

Preston

Sounds like a data corruption problem. I've only seen this type of problem when I used kernel.org 2.6.x-mm kernels with the make-4k-stacks-permanent.patch installed and using the nvidia video driver, but your situation suggests a regulation install with a SuSE kernel. Some hardware details would be of interest, the filesystem type you are using, Fedora uses ext3, I don't know if you stuck with that, if so I would suggest you try reiserfs instead. I normally use a boot CD (knoppix or timos rescuecd) to run reiserfsck (when I did that, it confirmed that my reiserfs was trashed). It may be possible with the SuSE boot CD/DVD to do a filesystem check. Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer Linux Only Shop.