X software not working.

[jane zhang]

Hi all,

I have a linux box with OS Red Hat Enterprise Linux WS.

I recently change it's NIS setting and rebooted it. The machines can not come up with (INIT X software resprawing too fast, wait for 5 minutes...).

I then commented out init X line and restarted, it asked to do manual fsck. Once this is done, the box came up but when I type "startx", it gave me this error messages:

xauth: error while loading shared libraries: libX11.so.6: cannot open shared object file: No such file or directory

My questions are:

1. How do I fsck the root disk?
2. where to get rpm package related to XFree86l-lib? I have CDs but can not find it.

Thanks,

Jane

[Ivan Ferreira]

To run a fsck of the root disk, you can boot in emergency mode. On GRUB, press "a" and type emergency, then ENTER and "b".

You can run fsck because the root filesystem is mounted as read only.

To find out the package that contains the libX11.so.6, you can use rpm -qif libX11.so.6

The libX11.so.6 argument must be the full path to the file.

[jane zhang]

Ivan,

Thanks for your response.

First I tried to install the Xfree86-lib from the installation cd. and It still give me IO errors, the rpm install failed.

I now boot it in emergency mode from mainitenance mode.


When I try
fsck -y /

it told me no, complaining /proc/partition is not mounted.

Could you let me know the fsck command?

Jane

[jane zhang]

OK,

I mount /proc/partition and then run

fsck -y /dev/hda5

It told me / /boot are clean.

Let me reboot and to see if startx works.

Jane

[jane zhang]

Hi,

After fsck -As in emergency, the box was rebooted and I tried to install XFree86-lib and I got IO error again and then:

hda: lost interrupted

....

express disk checked passed.

Any idea?

Jane

[Ivan Ferreira]

hda is your hard drive or your cdrom?

Maybe you have an I/O error on the CD media.

If hda is your hard drive, it may be bad.

First try replacing the power cable of the disk drive with another available.

Then try disabling DMA for the hard drive on the BIOS.

Then, try running the fsck with the -f and the -b options.

If this information is usefull, please assign some points ;).