Boot problem - libreadline.so.5

English Install/Boot/Login
#1

Hi,

I am running OpenSUSE 10.3. I have had no troubles with it until now:

Now I can no longer boot to Linux. Right at the beginning of the boot sequence, I get:

/bin/bash: error while loading shared libraries: libreadline.so.5 cannot open shared object file or directory

This is followed by a Kernel panic and then the system locks up. This happens in Fail Safe mode as well.

I do not understand what happened because I did not use root account and did no installation by myself since the last successful boot. Could the problem be caused by an automatic update?

I checked libreadline.so.5 and it IS in /lib/ directory.

Does anybody know what is the problem and how can I fix it?
Thanks!

martin

#2

This is a typical ‘this should not happen error’ problem. If a kernel panic occurs, you should also get a more desciptive error message. Which did you receive? Hardware releated disk-errors can also be the cause of your problem…

#3

I could access data by booting Knoppix from CD. Now I am backuping all my data with Knoppix. I will provide the complete error message afterwards.

#4

Meanwhile, I listed libreadline.so.5 in /lib/ directory and got Input/output error message:
$ ls /lib/libreadline.so.5*
ls: libreadline.so.5: Input/output error
ls: libreadline.so.5.2: Input/output error

#5

So the error message is as follows:

/bin/sh: error while loading shared libraries: libreadline.so.5: cannot open shared object file: Input/output error

(this message is iterated many times)

INIT: Id “1” respawning too fast: disabled for 5 minutes

(followed by 4 messages of /bin/sh: error while loading shared libraries: libreadline.so.5: cannot open shared object file: Input/output error)

INIT: Id “2” respawning too fast: disabled for 5 minutes

(followed by 4 messages of /bin/sh: error while loading shared libraries: libreadline.so.5: cannot open shared object file: Input/output error)

INIT: Id “3” etc…

INIT: No more processes left in this runlevel

#6

Can you run the following command:

dmesg

I suspect your partition or drive is going south. I/O errors are very nasty and may be hardware related.