Errno 5 Input/output error when running yum check-update
Clash Royale CLAN TAG#URR8PPP
I tried to update a server over SSH, but when I ran yum check-update I got an error:
[error 5] Input/output error
I think this means the RPM libraries may be damaged or corrupt, but I'm not sure how to resolve this.
linux centos
edited Feb 2 '16 at 18:13
Michael Mrozek♦
61.6k29192211
asked Feb 2 '16 at 18:03
user2513528user2513528
117
add a comment |
I tried to update a server over SSH, but when I ran yum check-update I got an error:
[error 5] Input/output error
I think this means the RPM libraries may be damaged or corrupt, but I'm not sure how to resolve this.
linux centos
edited Feb 2 '16 at 18:13
Michael Mrozek♦
61.6k29192211
asked Feb 2 '16 at 18:03
user2513528user2513528
117
This means (as its name implies) you have an error with your disk. There is an I/O error.
– Valentin Bajrami
Feb 2 '16 at 18:19
It also may mean that the yum cache location is not writable. Have you done any chmod's to /var recently?
– Tim S.
Feb 2 '16 at 18:22
add a comment |
I tried to update a server over SSH, but when I ran yum check-update I got an error:
[error 5] Input/output error
I think this means the RPM libraries may be damaged or corrupt, but I'm not sure how to resolve this.
linux centos
edited Feb 2 '16 at 18:13
Michael Mrozek♦
61.6k29192211
asked Feb 2 '16 at 18:03
user2513528user2513528
117
I tried to update a server over SSH, but when I ran yum check-update I got an error:
[error 5] Input/output error
I think this means the RPM libraries may be damaged or corrupt, but I'm not sure how to resolve this.
linux centos
linux centos
edited Feb 2 '16 at 18:13
Michael Mrozek♦
61.6k29192211
asked Feb 2 '16 at 18:03
user2513528user2513528
117
edited Feb 2 '16 at 18:13
Michael Mrozek♦
61.6k29192211
asked Feb 2 '16 at 18:03
user2513528user2513528
117
edited Feb 2 '16 at 18:13
Michael Mrozek♦
61.6k29192211
edited Feb 2 '16 at 18:13
Michael Mrozek♦
61.6k29192211
edited Feb 2 '16 at 18:13
Michael Mrozek♦
61.6k29192211
61.6k29192211
asked Feb 2 '16 at 18:03
user2513528user2513528
117
asked Feb 2 '16 at 18:03
user2513528user2513528
117
asked Feb 2 '16 at 18:03
user2513528user2513528
117
117
This means (as its name implies) you have an error with your disk. There is an I/O error.
– Valentin Bajrami
Feb 2 '16 at 18:19
It also may mean that the yum cache location is not writable. Have you done any chmod's to /var recently?
– Tim S.
Feb 2 '16 at 18:22
add a comment |
This means (as its name implies) you have an error with your disk. There is an I/O error.
– Valentin Bajrami
Feb 2 '16 at 18:19
It also may mean that the yum cache location is not writable. Have you done any chmod's to /var recently?
– Tim S.
Feb 2 '16 at 18:22
This means (as its name implies) you have an error with your disk. There is an I/O error.
– Valentin Bajrami
Feb 2 '16 at 18:19
This means (as its name implies) you have an error with your disk. There is an I/O error.
– Valentin Bajrami
Feb 2 '16 at 18:19
It also may mean that the yum cache location is not writable. Have you done any chmod's to /var recently?
– Tim S.
Feb 2 '16 at 18:22
It also may mean that the yum cache location is not writable. Have you done any chmod's to /var recently?
– Tim S.
Feb 2 '16 at 18:22
add a comment |
2 Answers
2
active
oldest
votes
As the comments mentioned its probably that there is something wrong with your disk. My first thought would be to check disk space. Double check file system too (btrfs snaps for example).
df -h
Then going into File permissions (chmod etc), and actual disk failures. Try to write or touch files in other directories/partitions
touch ~/yayfile.txt
touch /yayfile.txt
answered Feb 2 '16 at 20:09
DishcandantyDishcandanty
165
hi, thank you everyone for you help, i am still learning linux, so i really appreciate the assistance
– user2513528
Feb 6 '16 at 3:34
Aren't we all :). Mark answered or comment ( if still need help ).
– Dishcandanty
Feb 13 '16 at 20:39
add a comment |
I ran into this same issue across a number of VMs. The fix that worked for me was to clean up yum tmp files.
yum clean all
answered Jun 21 '18 at 17:22
Matthew MattoxMatthew Mattox
1
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f259387%2ferrno-5-input-output-error-when-running-yum-check-update%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
As the comments mentioned its probably that there is something wrong with your disk. My first thought would be to check disk space. Double check file system too (btrfs snaps for example).
df -h
Then going into File permissions (chmod etc), and actual disk failures. Try to write or touch files in other directories/partitions
touch ~/yayfile.txt
touch /yayfile.txt
answered Feb 2 '16 at 20:09
DishcandantyDishcandanty
165
hi, thank you everyone for you help, i am still learning linux, so i really appreciate the assistance
– user2513528
Feb 6 '16 at 3:34
Aren't we all :). Mark answered or comment ( if still need help ).
– Dishcandanty
Feb 13 '16 at 20:39
add a comment |
As the comments mentioned its probably that there is something wrong with your disk. My first thought would be to check disk space. Double check file system too (btrfs snaps for example).
df -h
Then going into File permissions (chmod etc), and actual disk failures. Try to write or touch files in other directories/partitions
touch ~/yayfile.txt
touch /yayfile.txt
answered Feb 2 '16 at 20:09
DishcandantyDishcandanty
165
hi, thank you everyone for you help, i am still learning linux, so i really appreciate the assistance
– user2513528
Feb 6 '16 at 3:34
Aren't we all :). Mark answered or comment ( if still need help ).
– Dishcandanty
Feb 13 '16 at 20:39
add a comment |
As the comments mentioned its probably that there is something wrong with your disk. My first thought would be to check disk space. Double check file system too (btrfs snaps for example).
df -h
Then going into File permissions (chmod etc), and actual disk failures. Try to write or touch files in other directories/partitions
touch ~/yayfile.txt
touch /yayfile.txt
answered Feb 2 '16 at 20:09
DishcandantyDishcandanty
165
As the comments mentioned its probably that there is something wrong with your disk. My first thought would be to check disk space. Double check file system too (btrfs snaps for example).
df -h
Then going into File permissions (chmod etc), and actual disk failures. Try to write or touch files in other directories/partitions
touch ~/yayfile.txt
touch /yayfile.txt
answered Feb 2 '16 at 20:09
DishcandantyDishcandanty
165
answered Feb 2 '16 at 20:09
DishcandantyDishcandanty
165
answered Feb 2 '16 at 20:09
DishcandantyDishcandanty
165
answered Feb 2 '16 at 20:09
DishcandantyDishcandanty
165
165
hi, thank you everyone for you help, i am still learning linux, so i really appreciate the assistance
– user2513528
Feb 6 '16 at 3:34
Aren't we all :). Mark answered or comment ( if still need help ).
– Dishcandanty
Feb 13 '16 at 20:39
add a comment |
hi, thank you everyone for you help, i am still learning linux, so i really appreciate the assistance
– user2513528
Feb 6 '16 at 3:34
Aren't we all :). Mark answered or comment ( if still need help ).
– Dishcandanty
Feb 13 '16 at 20:39
hi, thank you everyone for you help, i am still learning linux, so i really appreciate the assistance
– user2513528
Feb 6 '16 at 3:34
hi, thank you everyone for you help, i am still learning linux, so i really appreciate the assistance
– user2513528
Feb 6 '16 at 3:34
Aren't we all :). Mark answered or comment ( if still need help ).
– Dishcandanty
Feb 13 '16 at 20:39
Aren't we all :). Mark answered or comment ( if still need help ).
– Dishcandanty
Feb 13 '16 at 20:39
add a comment |
I ran into this same issue across a number of VMs. The fix that worked for me was to clean up yum tmp files.
yum clean all
answered Jun 21 '18 at 17:22
Matthew MattoxMatthew Mattox
1
add a comment |
I ran into this same issue across a number of VMs. The fix that worked for me was to clean up yum tmp files.
yum clean all
answered Jun 21 '18 at 17:22
Matthew MattoxMatthew Mattox
1
add a comment |
I ran into this same issue across a number of VMs. The fix that worked for me was to clean up yum tmp files.
yum clean all
answered Jun 21 '18 at 17:22
Matthew MattoxMatthew Mattox
1
I ran into this same issue across a number of VMs. The fix that worked for me was to clean up yum tmp files.
yum clean all
answered Jun 21 '18 at 17:22
Matthew MattoxMatthew Mattox
1
answered Jun 21 '18 at 17:22
Matthew MattoxMatthew Mattox
1
answered Jun 21 '18 at 17:22
Matthew MattoxMatthew Mattox
1
answered Jun 21 '18 at 17:22
Matthew MattoxMatthew Mattox
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f259387%2ferrno-5-input-output-error-when-running-yum-check-update%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
This means (as its name implies) you have an error with your disk. There is an I/O error.
– Valentin Bajrami
Feb 2 '16 at 18:19
It also may mean that the yum cache location is not writable. Have you done any chmod's to /var recently?
– Tim S.
Feb 2 '16 at 18:22