input/output error /tmp : No X startup

[Michiel]

Ran into weird but serious trouble. My Pardus system froze suddenly and upon rebooting it now hangs at the point where it tries to clean up /tmp and then comes up with an error message which I cannot reproduce literally (mudur is named and that one should contact Pardus team), but it states an input/output error of /tmp, I can also not access /tmp anymore.
I can only login in CLI, and do things like ls and so on. I can cd to all dirs except tmp which is not accessible and causes X not to start up.

Any hints how to get out without losing my data?

Can it be a memory problem in /tmp?

At linuxquestions.org I found this suggestion which I will give a try:

Code:

mkdir /deltmp
mount -t /dev/sda1 /deltmp
rm /deltmp/tmp* -R

[PhiX]

Is your root partition full ?

Code:

df /

As root, you can try to delete the X lock file

Code:

su
rm /tmp/.X0-lock

Then, Ctrl-D to go back to your user account and

Code:

startx

[Michiel]

Thanks, but the problem is I can do anything with all dirs except /tmp.

Any action regarding /tmp (whether cd or rm or whatever) ends up in the same input/ouput error
The partition is NOT full.

Is trying to umount /tmp an option you think?

Luckily I have managed to backup my home/username folder data, so I am almost at the point of aonther re-install (third already for 2009), perhaps my laptop hardware is just getting too old, that might also be the ase.

[PhiX]

You can't unmount /tmp, unless it is on a separate partition.

What is th exact error message in /var/log/Xorg.0.log ?

[Michiel]

Well, just leave this, I reinstalled. The problem was somehow a completely locked /tmp dir, I do not think the xorg files itself were corrupt. Just a single bit having fallen the wrong way I guess, just unlucky.
I tried all sorts of options (inclouding accessing from a LIVE CD) to restore things, but did not succeed. Also upon Googling around I did not find a right away solution.

Luckily I was able to backup my home/username data, and reinstalling takes about 30 minutes.

I am not such a fanatic that I defintely want to solve ALL my encountered bugs befroe proceeding. Most of the time I wait one-and-a-half day to find a soultion together with the community, but when it takes longer I take the short bend and do a reinstall to get things up-and-running again.

Theoretically you miss potential solutions for problems that other people als might encounter I know, but as said I am not that fanatic although I am always willing to help finding solutions for each other.

So I guess I can close this for now.

Thanks for thinking along with me and providing some suggestions PhiX