Quote Originally Posted by Cuddles
Ok,

In trying to find my own answers, I have concluded the following, from the above situation:

I should have mounted the /dev/hda device as r/w access, and performed a fixing fsck on the device. After, hopefully, a good fixing, and a successful fsck completion, rebooted.

But, I didn't - I just rebooted.

What I am guessing I should do is, shutdown, boot to the CD, give it cheatcodes to not use my swap, which is also on the "physical" /dev/hda device, to not use my home/root on the /dev/hda1 device, and after booting, perform a fsck on the /dev/hda device.
You would boot the CD and then check the filesystem assuming it is ext3 e2fsck /dev/hda1 you do not mount the partitions and knoppix will not by default mount the partitions the /swap is irrevalent you should not need to check it.

Looking through the fsck man pages, I am getting lost. I know I want to use the fix option, but do I want it to have "unlimited" fixing, (it suggests this is a bad thing), do I mount the device previous, or do I let fsck do that part?

I am in fear that the longer I keep my system up, after knowing about the fsck problem, I am only damaging the file system further, am I right?

Someone, [?]
Cuddles
You can just answer the questions one by one which the command I gave does there will most likely be a lot of them and you are going to want to answer yes to fixing the errors so the -y in the command may be what you want.