Answer the question
In order to leave comments, you need to log in
[[+content_image]]
Could it be a problem with the physical drive?
[[email protected] ~]# uptime
20:36:47 up 111 days, 5:09, 1 user, load average: 2.19, 1.51, 0.98
[[email protected] ~]# yum update
-bash: /usr/bin/yum: /usr/bin/python: bad interpreter: Input/output error
[[email protected] ~]# uname -r
2.6.32-696.28.1.el6.x86_64
Answer the question
In order to leave comments, you need to log in
The error message only shows that the python was threaded somewhere.
Theoretically, this may be due to a file system problem, and it can also be related to a physical disk problem. The dmesg command and the logs will be able to clear things up.
But if the matter is not in the disk, then you can restore the work of yum.
First you need to look for a snake =) :
If not found, download and unpack somewhere.
Well, link it (the first part is the path of the python found or installed manually):
And then reinstall it correctly, after "fixing" yum.
Not only can there be a problem - there is a problem in it. If there is valuable data - urgently back up.
Then:
1. Remove smart and analyze it. If smart shows that a fur-bearing animal is sneaking up to the disk, put money into the budget to buy a new one.
2. (if smart is nothing) The disk to be checked by Victoria or MHDD - sometimes with their help you can reallocate or clean broken sectors and it seems that work is being restored. But for responsible data, I would not use it anymore.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question