Broken filesystem
Something is wrong with the filesystem on my ubuntu installtion and i'm trying to fix it. I tired to use fsck but the problem is that i don't got access to sudo when I try to run sudo i get
-bash: /usr/bin/sudo: Input/output error
A lot of other program does work as well like df, same error.
What might be worth knowing is that i'm running the installation on raid 5 (setup from ubuntu, not hardware). It might be possible that one of the disk are broken. Again i need sudo to check the status of that. So how do fix the filesystem without sudo (or get it back)?
Also of note i updated over 100 packages yesterday but it seem unlikly that it caused this error, including it just in case.
16.04 server mount filesystem raid
add a comment |
Something is wrong with the filesystem on my ubuntu installtion and i'm trying to fix it. I tired to use fsck but the problem is that i don't got access to sudo when I try to run sudo i get
-bash: /usr/bin/sudo: Input/output error
A lot of other program does work as well like df, same error.
What might be worth knowing is that i'm running the installation on raid 5 (setup from ubuntu, not hardware). It might be possible that one of the disk are broken. Again i need sudo to check the status of that. So how do fix the filesystem without sudo (or get it back)?
Also of note i updated over 100 packages yesterday but it seem unlikly that it caused this error, including it just in case.
16.04 server mount filesystem raid
Restarted the system and got control back. It looks like only one disk had failed. Have orded an new on and shut the server off until then. Hopeful this will be solved.
– Frozendragon
Apr 17 '17 at 19:10
add a comment |
Something is wrong with the filesystem on my ubuntu installtion and i'm trying to fix it. I tired to use fsck but the problem is that i don't got access to sudo when I try to run sudo i get
-bash: /usr/bin/sudo: Input/output error
A lot of other program does work as well like df, same error.
What might be worth knowing is that i'm running the installation on raid 5 (setup from ubuntu, not hardware). It might be possible that one of the disk are broken. Again i need sudo to check the status of that. So how do fix the filesystem without sudo (or get it back)?
Also of note i updated over 100 packages yesterday but it seem unlikly that it caused this error, including it just in case.
16.04 server mount filesystem raid
Something is wrong with the filesystem on my ubuntu installtion and i'm trying to fix it. I tired to use fsck but the problem is that i don't got access to sudo when I try to run sudo i get
-bash: /usr/bin/sudo: Input/output error
A lot of other program does work as well like df, same error.
What might be worth knowing is that i'm running the installation on raid 5 (setup from ubuntu, not hardware). It might be possible that one of the disk are broken. Again i need sudo to check the status of that. So how do fix the filesystem without sudo (or get it back)?
Also of note i updated over 100 packages yesterday but it seem unlikly that it caused this error, including it just in case.
16.04 server mount filesystem raid
16.04 server mount filesystem raid
asked Apr 12 '17 at 21:39
FrozendragonFrozendragon
1133
1133
Restarted the system and got control back. It looks like only one disk had failed. Have orded an new on and shut the server off until then. Hopeful this will be solved.
– Frozendragon
Apr 17 '17 at 19:10
add a comment |
Restarted the system and got control back. It looks like only one disk had failed. Have orded an new on and shut the server off until then. Hopeful this will be solved.
– Frozendragon
Apr 17 '17 at 19:10
Restarted the system and got control back. It looks like only one disk had failed. Have orded an new on and shut the server off until then. Hopeful this will be solved.
– Frozendragon
Apr 17 '17 at 19:10
Restarted the system and got control back. It looks like only one disk had failed. Have orded an new on and shut the server off until then. Hopeful this will be solved.
– Frozendragon
Apr 17 '17 at 19:10
add a comment |
1 Answer
1
active
oldest
votes
"Input/output error" is bash telling you that it has been refused access to that utility by the kernel. The kernel has unfortunately been told by the hardware that it is unavailable (or it believes it is unavailable). Typically in a single disk environment, this error would signify that a disk has failed (or is failing), as it is refusing access to those sectors of the disk that hold that utility or application (in your case, sudo).
I would boot from an Ubuntu live CD (or USB) and see if you can diagnose the issue using the utilities in the live environment. If you can see your array and your disks, it may be that the kernel has had a moment and forgotten how to interact with them. If you can't see your disks, or a disk is missing, you may be looking at array issues, which is a whole different post I'm afraid.
In RAID5, if you lose two disks in the array you lose everything. It sounds like two disks may have died and the array has basically stalled, disallowing access to anything on it (sudo being the prime example).
Minor nitpick, I think you mean "In RAID5, if you lose two disks in the array you lose everything.".
– jrh
Oct 18 '18 at 20:00
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2faskubuntu.com%2fquestions%2f904121%2fbroken-filesystem%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
"Input/output error" is bash telling you that it has been refused access to that utility by the kernel. The kernel has unfortunately been told by the hardware that it is unavailable (or it believes it is unavailable). Typically in a single disk environment, this error would signify that a disk has failed (or is failing), as it is refusing access to those sectors of the disk that hold that utility or application (in your case, sudo).
I would boot from an Ubuntu live CD (or USB) and see if you can diagnose the issue using the utilities in the live environment. If you can see your array and your disks, it may be that the kernel has had a moment and forgotten how to interact with them. If you can't see your disks, or a disk is missing, you may be looking at array issues, which is a whole different post I'm afraid.
In RAID5, if you lose two disks in the array you lose everything. It sounds like two disks may have died and the array has basically stalled, disallowing access to anything on it (sudo being the prime example).
Minor nitpick, I think you mean "In RAID5, if you lose two disks in the array you lose everything.".
– jrh
Oct 18 '18 at 20:00
add a comment |
"Input/output error" is bash telling you that it has been refused access to that utility by the kernel. The kernel has unfortunately been told by the hardware that it is unavailable (or it believes it is unavailable). Typically in a single disk environment, this error would signify that a disk has failed (or is failing), as it is refusing access to those sectors of the disk that hold that utility or application (in your case, sudo).
I would boot from an Ubuntu live CD (or USB) and see if you can diagnose the issue using the utilities in the live environment. If you can see your array and your disks, it may be that the kernel has had a moment and forgotten how to interact with them. If you can't see your disks, or a disk is missing, you may be looking at array issues, which is a whole different post I'm afraid.
In RAID5, if you lose two disks in the array you lose everything. It sounds like two disks may have died and the array has basically stalled, disallowing access to anything on it (sudo being the prime example).
Minor nitpick, I think you mean "In RAID5, if you lose two disks in the array you lose everything.".
– jrh
Oct 18 '18 at 20:00
add a comment |
"Input/output error" is bash telling you that it has been refused access to that utility by the kernel. The kernel has unfortunately been told by the hardware that it is unavailable (or it believes it is unavailable). Typically in a single disk environment, this error would signify that a disk has failed (or is failing), as it is refusing access to those sectors of the disk that hold that utility or application (in your case, sudo).
I would boot from an Ubuntu live CD (or USB) and see if you can diagnose the issue using the utilities in the live environment. If you can see your array and your disks, it may be that the kernel has had a moment and forgotten how to interact with them. If you can't see your disks, or a disk is missing, you may be looking at array issues, which is a whole different post I'm afraid.
In RAID5, if you lose two disks in the array you lose everything. It sounds like two disks may have died and the array has basically stalled, disallowing access to anything on it (sudo being the prime example).
"Input/output error" is bash telling you that it has been refused access to that utility by the kernel. The kernel has unfortunately been told by the hardware that it is unavailable (or it believes it is unavailable). Typically in a single disk environment, this error would signify that a disk has failed (or is failing), as it is refusing access to those sectors of the disk that hold that utility or application (in your case, sudo).
I would boot from an Ubuntu live CD (or USB) and see if you can diagnose the issue using the utilities in the live environment. If you can see your array and your disks, it may be that the kernel has had a moment and forgotten how to interact with them. If you can't see your disks, or a disk is missing, you may be looking at array issues, which is a whole different post I'm afraid.
In RAID5, if you lose two disks in the array you lose everything. It sounds like two disks may have died and the array has basically stalled, disallowing access to anything on it (sudo being the prime example).
edited 9 hours ago
wjandrea
8,49742259
8,49742259
answered Apr 12 '17 at 21:48
FoxieFoxie
396212
396212
Minor nitpick, I think you mean "In RAID5, if you lose two disks in the array you lose everything.".
– jrh
Oct 18 '18 at 20:00
add a comment |
Minor nitpick, I think you mean "In RAID5, if you lose two disks in the array you lose everything.".
– jrh
Oct 18 '18 at 20:00
Minor nitpick, I think you mean "In RAID5, if you lose two disks in the array you lose everything.".
– jrh
Oct 18 '18 at 20:00
Minor nitpick, I think you mean "In RAID5, if you lose two disks in the array you lose everything.".
– jrh
Oct 18 '18 at 20:00
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f904121%2fbroken-filesystem%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
Restarted the system and got control back. It looks like only one disk had failed. Have orded an new on and shut the server off until then. Hopeful this will be solved.
– Frozendragon
Apr 17 '17 at 19:10