I apperantly did some bad stuff to my system, so I've got a few questions on fixing it.

I had an old 2.4.20 kernel which kept locking up. I decided since it was vunerable and locking up, I'd upgrade to 2.6.10. Unfortunatally, I've had to do cold reboots because of the lockups since then. This is what I believe is causing my other errors...

I recompiled gcc, which under the old kernel had been segmentation faulting compiling some applications, but could still compile hello world apps. It compiled, but when I tried to delete the directory I had unzipped it to, I couldn't delete the file INSTALL, even as root, it seemed to me like a filesystem error, so I went to init 1 and ran fsck.

It said I had 3 bad spots that could be fixed with reiserfsck --rebuild-tree, but when I ran reiserfsck with that option, it only displayed the help.

So my questions are,

1. Why is gcc segfaulting on so many apps, currently blackbox wm.
2. How can I run fsck so that it will rebuild the filesystem and fix the errors.
3. In doing this, I've been watching my RAM, which has always had about 100 Megs Free, but for some reason, swap space is used. Is there a program to push everything from swap to RAM?

-Thanks

Hi,

Hopefully I can help a little!

You'll probably find that in order to run this, you'll first have to unmount the filesystem. If I remember correctly, at init 1 only the root filesystem is mounted, but if you only have one large partition...you're probably going to need to boot from floppy/cdrom.

If you did unmount the fs, did you remember to specify a device (e.g. /dev/hda1) for the command to perform the check on?

The system will swap out unneeded data to keep free system ram to maintain system responsiveness etc.



Good question, could possibly be a hardware fault, but probably not. Have you checked things like /var/log/messages and /var/log/syslog?

Cheers,

Steve

The command would be :
reiserfsck --rebuild-tree /dev/hd(your device + partition)

and not:
fsck reiserfsck --rebuild-tree (or any other wrong command you did type)

What is your glibc version ?
/lib/libc.so.6 | grep version

And your gcc version :
gcc -v
(post the whole output please)

what processor and what's the temperature of it?

Oh! I forgot to post when I got this fixed. Well here's everything that happened in case someone else has this problem...

1. I installed slackware 9.0, my favorite version, because it came on one CD, that was probably a bad idea.

2. I was very stupid for about 2 months, and left myself open to that huge hole in the 2.4.20 kernels before I finally decided to upgrade because of lockups occurring because of the kernel.

3. I compiled a 2.6.7 kernel and stuck that in lilo, but I still got lockups, and I had some driver issues so I decided to fall back to 2.4.20

4. I decided 2.6.10 was the way to go and compiled that, got it running smoothly, but apparently something in tmp or swap was bad . . .

5. After so many lockups, and so many cold reboots, the hard drive had become corrupted. I began to get bad links to files in the allocation table making files that I couldn't see the info for, and that couldn't be deleted, even as root.

6. The kernel eventually needed to access something, actually I think it was X that died first, but eventually, everything fell apart and it just locked up/reboted.

7. I let it run through it's rebooting, until it stopped about half way through for no apparent reason. I rebooted only to have a kernel panic claiming a bad eip value, spitting out all sorts of register values and stack traces.

8. I tried rebooting again, and I got "ERROR CRC ERROR IN 'LINUX'", at this point I became very frightened

9. I fell back, again, to my 2.4.20 kernel, and ran fsck, it said there were errors and I had to rebuild the tree.

10. I reboted and ran from an old gentoo CD, reiserfsck /dev/hda. It rebuilt the entire tree and said it found 14 bad links in the allocation table.

11. I rebooted and everything was fine, except for the files that I lost, most of which were just source files in things like naim, etc


Hope this helps someone.