Unable to mount LV: “mount(2) system call failed: Structure needs cleaning,” but e2fsck says clean
Clash Royale CLAN TAG#URR8PPP
I was trying to install an old optical drive into my system, which turned out to be having problems, so I pulled it out again, but upon rebooting back into Ubuntu 18.04, I'm unable to mount my 3-drive (16TB) linear lvm volume. I keep getting the message:
mount: /home/kp/bigdrive: mount(2) system call failed: Structure needs cleaning.
I ran sudo e2fsck /dev/bigVG/bigvol and it comes back clean (without errors) every time. Also, the volume mounts just fine using the Ubuntu 18.04 live CD. No problems whatsoever. I'm really baffled here. Is there some kind of cached file I need to clear or something?
mount lvm storage administration
asked Jan 29 at 23:26
kegepetkegepet
133
add a comment |
I was trying to install an old optical drive into my system, which turned out to be having problems, so I pulled it out again, but upon rebooting back into Ubuntu 18.04, I'm unable to mount my 3-drive (16TB) linear lvm volume. I keep getting the message:
mount: /home/kp/bigdrive: mount(2) system call failed: Structure needs cleaning.
I ran sudo e2fsck /dev/bigVG/bigvol and it comes back clean (without errors) every time. Also, the volume mounts just fine using the Ubuntu 18.04 live CD. No problems whatsoever. I'm really baffled here. Is there some kind of cached file I need to clear or something?
mount lvm storage administration
asked Jan 29 at 23:26
kegepetkegepet
133
Thefsck /dev/bigVG/bigvolwon't check the volume if it thinks it's already clean. (Typically it's considered clean if the lastumountwas successful.) You need the-fflag to force the check.
– roaima
Feb 1 at 7:32
add a comment |
I was trying to install an old optical drive into my system, which turned out to be having problems, so I pulled it out again, but upon rebooting back into Ubuntu 18.04, I'm unable to mount my 3-drive (16TB) linear lvm volume. I keep getting the message:
mount: /home/kp/bigdrive: mount(2) system call failed: Structure needs cleaning.
I ran sudo e2fsck /dev/bigVG/bigvol and it comes back clean (without errors) every time. Also, the volume mounts just fine using the Ubuntu 18.04 live CD. No problems whatsoever. I'm really baffled here. Is there some kind of cached file I need to clear or something?
mount lvm storage administration
asked Jan 29 at 23:26
kegepetkegepet
133
I was trying to install an old optical drive into my system, which turned out to be having problems, so I pulled it out again, but upon rebooting back into Ubuntu 18.04, I'm unable to mount my 3-drive (16TB) linear lvm volume. I keep getting the message:
mount: /home/kp/bigdrive: mount(2) system call failed: Structure needs cleaning.
I ran sudo e2fsck /dev/bigVG/bigvol and it comes back clean (without errors) every time. Also, the volume mounts just fine using the Ubuntu 18.04 live CD. No problems whatsoever. I'm really baffled here. Is there some kind of cached file I need to clear or something?
mount lvm storage administration
mount lvm storage administration
asked Jan 29 at 23:26
kegepetkegepet
133
asked Jan 29 at 23:26
kegepetkegepet
133
edited Jan 30 at 1:38
kegepet
asked Jan 29 at 23:26
kegepetkegepet
133
asked Jan 29 at 23:26
kegepetkegepet
133
asked Jan 29 at 23:26
kegepetkegepet
133
133
Thefsck /dev/bigVG/bigvolwon't check the volume if it thinks it's already clean. (Typically it's considered clean if the lastumountwas successful.) You need the-fflag to force the check.
– roaima
Feb 1 at 7:32
add a comment |
Thefsck /dev/bigVG/bigvolwon't check the volume if it thinks it's already clean. (Typically it's considered clean if the lastumountwas successful.) You need the-fflag to force the check.
– roaima
Feb 1 at 7:32
The
fsck /dev/bigVG/bigvol won't check the volume if it thinks it's already clean. (Typically it's considered clean if the last umount was successful.) You need the -f flag to force the check.– roaima
Feb 1 at 7:32
The
fsck /dev/bigVG/bigvol won't check the volume if it thinks it's already clean. (Typically it's considered clean if the last umount was successful.) You need the -f flag to force the check.– roaima
Feb 1 at 7:32
add a comment |
2 Answers
2
active
oldest
votes
As I just posted in the other thread, the kernel package linux-image-4.15.0-43-generic works for me, while linux-image-4.15.0-44-generic has the "Structure needs cleaning" bug described above. Hope this helps!
answered Jan 31 at 0:12
Frank HorowitzFrank Horowitz
261
Wish I had seen this sooner, but I needed to get the file server up and running. Anyway, now I know. Thanks for the info.
– kegepet
Jan 31 at 1:08
add a comment |
OK, I noticed another post in the SuperUser forum from yesterday and the problem described is identical to my own. As I mentioned in my initial post, the 18.04 live cd mounts the volume fine. Today, I tried the 18.10 live cd and that too mounted the volume without issue. I first reinstalled 18.04 from scratch (along with all available updates), but the problem persisted. Finally, I installed 18.10 and the volume mounts perfectly. So, I'm guessing something broke
with some recent update for 18.04. Any info would still be appreciated.
answered Jan 30 at 19:56
kegepetkegepet
133
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%2f497577%2funable-to-mount-lv-mount2-system-call-failed-structure-needs-cleaning-but%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 I just posted in the other thread, the kernel package linux-image-4.15.0-43-generic works for me, while linux-image-4.15.0-44-generic has the "Structure needs cleaning" bug described above. Hope this helps!
answered Jan 31 at 0:12
Frank HorowitzFrank Horowitz
261
Wish I had seen this sooner, but I needed to get the file server up and running. Anyway, now I know. Thanks for the info.
– kegepet
Jan 31 at 1:08
add a comment |
As I just posted in the other thread, the kernel package linux-image-4.15.0-43-generic works for me, while linux-image-4.15.0-44-generic has the "Structure needs cleaning" bug described above. Hope this helps!
answered Jan 31 at 0:12
Frank HorowitzFrank Horowitz
261
Wish I had seen this sooner, but I needed to get the file server up and running. Anyway, now I know. Thanks for the info.
– kegepet
Jan 31 at 1:08
add a comment |
As I just posted in the other thread, the kernel package linux-image-4.15.0-43-generic works for me, while linux-image-4.15.0-44-generic has the "Structure needs cleaning" bug described above. Hope this helps!
answered Jan 31 at 0:12
Frank HorowitzFrank Horowitz
261
As I just posted in the other thread, the kernel package linux-image-4.15.0-43-generic works for me, while linux-image-4.15.0-44-generic has the "Structure needs cleaning" bug described above. Hope this helps!
answered Jan 31 at 0:12
Frank HorowitzFrank Horowitz
261
answered Jan 31 at 0:12
Frank HorowitzFrank Horowitz
261
answered Jan 31 at 0:12
Frank HorowitzFrank Horowitz
261
answered Jan 31 at 0:12
Frank HorowitzFrank Horowitz
261
261
Wish I had seen this sooner, but I needed to get the file server up and running. Anyway, now I know. Thanks for the info.
– kegepet
Jan 31 at 1:08
add a comment |
Wish I had seen this sooner, but I needed to get the file server up and running. Anyway, now I know. Thanks for the info.
– kegepet
Jan 31 at 1:08
Wish I had seen this sooner, but I needed to get the file server up and running. Anyway, now I know. Thanks for the info.
– kegepet
Jan 31 at 1:08
Wish I had seen this sooner, but I needed to get the file server up and running. Anyway, now I know. Thanks for the info.
– kegepet
Jan 31 at 1:08
add a comment |
OK, I noticed another post in the SuperUser forum from yesterday and the problem described is identical to my own. As I mentioned in my initial post, the 18.04 live cd mounts the volume fine. Today, I tried the 18.10 live cd and that too mounted the volume without issue. I first reinstalled 18.04 from scratch (along with all available updates), but the problem persisted. Finally, I installed 18.10 and the volume mounts perfectly. So, I'm guessing something broke
with some recent update for 18.04. Any info would still be appreciated.
answered Jan 30 at 19:56
kegepetkegepet
133
add a comment |
OK, I noticed another post in the SuperUser forum from yesterday and the problem described is identical to my own. As I mentioned in my initial post, the 18.04 live cd mounts the volume fine. Today, I tried the 18.10 live cd and that too mounted the volume without issue. I first reinstalled 18.04 from scratch (along with all available updates), but the problem persisted. Finally, I installed 18.10 and the volume mounts perfectly. So, I'm guessing something broke
with some recent update for 18.04. Any info would still be appreciated.
answered Jan 30 at 19:56
kegepetkegepet
133
add a comment |
OK, I noticed another post in the SuperUser forum from yesterday and the problem described is identical to my own. As I mentioned in my initial post, the 18.04 live cd mounts the volume fine. Today, I tried the 18.10 live cd and that too mounted the volume without issue. I first reinstalled 18.04 from scratch (along with all available updates), but the problem persisted. Finally, I installed 18.10 and the volume mounts perfectly. So, I'm guessing something broke
with some recent update for 18.04. Any info would still be appreciated.
answered Jan 30 at 19:56
kegepetkegepet
133
OK, I noticed another post in the SuperUser forum from yesterday and the problem described is identical to my own. As I mentioned in my initial post, the 18.04 live cd mounts the volume fine. Today, I tried the 18.10 live cd and that too mounted the volume without issue. I first reinstalled 18.04 from scratch (along with all available updates), but the problem persisted. Finally, I installed 18.10 and the volume mounts perfectly. So, I'm guessing something broke
with some recent update for 18.04. Any info would still be appreciated.
answered Jan 30 at 19:56
kegepetkegepet
133
answered Jan 30 at 19:56
kegepetkegepet
133
answered Jan 30 at 19:56
kegepetkegepet
133
answered Jan 30 at 19:56
kegepetkegepet
133
133
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%2f497577%2funable-to-mount-lv-mount2-system-call-failed-structure-needs-cleaning-but%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
The
fsck /dev/bigVG/bigvolwon't check the volume if it thinks it's already clean. (Typically it's considered clean if the lastumountwas successful.) You need the-fflag to force the check.– roaima
Feb 1 at 7:32