Error? Ext4-fs (sda6): couldn't mount as ext3 due to feature incompatibilities
In recent weeks, when the attempt system boot Ubuntu, the following information appears on the screen with black background:
Ext4-fs (sda6): couldn't mount as ext3 due to feature incompatibilities.
Ext4-fs (sda6): couldn't mount as ext2 due to feature incompatibilities.
Friends, can you tell me how to interpret these messages, and what could do about it?
Thanks
ext4
asked Mar 26 '16 at 20:58
Daniel GonzálezDaniel González
11113
add a comment |
In recent weeks, when the attempt system boot Ubuntu, the following information appears on the screen with black background:
Ext4-fs (sda6): couldn't mount as ext3 due to feature incompatibilities.
Ext4-fs (sda6): couldn't mount as ext2 due to feature incompatibilities.
Friends, can you tell me how to interpret these messages, and what could do about it?
Thanks
ext4
asked Mar 26 '16 at 20:58
Daniel GonzálezDaniel González
11113
add a comment |
In recent weeks, when the attempt system boot Ubuntu, the following information appears on the screen with black background:
Ext4-fs (sda6): couldn't mount as ext3 due to feature incompatibilities.
Ext4-fs (sda6): couldn't mount as ext2 due to feature incompatibilities.
Friends, can you tell me how to interpret these messages, and what could do about it?
Thanks
ext4
asked Mar 26 '16 at 20:58
Daniel GonzálezDaniel González
11113
In recent weeks, when the attempt system boot Ubuntu, the following information appears on the screen with black background:
Ext4-fs (sda6): couldn't mount as ext3 due to feature incompatibilities.
Ext4-fs (sda6): couldn't mount as ext2 due to feature incompatibilities.
Friends, can you tell me how to interpret these messages, and what could do about it?
Thanks
ext4
ext4
asked Mar 26 '16 at 20:58
Daniel GonzálezDaniel González
11113
asked Mar 26 '16 at 20:58
Daniel GonzálezDaniel González
11113
asked Mar 26 '16 at 20:58
Daniel GonzálezDaniel González
11113
asked Mar 26 '16 at 20:58
Daniel GonzálezDaniel González
11113
asked Mar 26 '16 at 20:58
Daniel GonzálezDaniel González
11113
11113
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
Apparently you marked the partition as ext3 in /etc/fstab, when in fact it is ext4 ( or you have since converted it with tune2fs ). Change the ext3 designation to ext4 in /etc/fstab.
answered Mar 27 '16 at 0:21
psusipsusi
31.2k15088
Thanks for your answer. But I found it easier to reinstall the operating system and putting on ubuntu Mate 15.10. Apparently, the new kernel updates were causing me the problem because since that I have not updated the problem didn't appear again.
– Daniel González
Apr 15 '16 at 16:10
add a comment |
I saw this bright red message in my dmesg output and got curious although I am not experiencing any problems. I checked the hint from psusi's answer but /etc/fstab is set to ext4 on my system. After some more research I found this post in the arch forum with an explanation that sounds resonable to me. The gist: The ext-fs driver supports multiple versions and checks which one works if none is specified at boot time. My kernel command line reads root=/dev/xvda ro console=xvc0 console=hvc0 so it looks like auto-detection is required.
answered Jan 25 at 19:05
wediwedi
1113
add a comment |
This just happened to me recently after a package upgrade leaving me with a low resolution login screen that wouldn't work. (Ubuntu 16.04)
- Type Ctrl+Alt+F1 to get a terminal and login via this terminal.
Run following commands:
sudo apt update
sudo apt upgrade
sudo reboot
Hope this helps ...
edited Feb 16 '17 at 12:16
d a i s y
3,34782444
answered Feb 16 '17 at 11:22
JohnJohn
11
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%2f750518%2ferror-ext4-fs-sda6-couldnt-mount-as-ext3-due-to-feature-incompatibilities%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Apparently you marked the partition as ext3 in /etc/fstab, when in fact it is ext4 ( or you have since converted it with tune2fs ). Change the ext3 designation to ext4 in /etc/fstab.
answered Mar 27 '16 at 0:21
psusipsusi
31.2k15088
Thanks for your answer. But I found it easier to reinstall the operating system and putting on ubuntu Mate 15.10. Apparently, the new kernel updates were causing me the problem because since that I have not updated the problem didn't appear again.
– Daniel González
Apr 15 '16 at 16:10
add a comment |
Apparently you marked the partition as ext3 in /etc/fstab, when in fact it is ext4 ( or you have since converted it with tune2fs ). Change the ext3 designation to ext4 in /etc/fstab.
answered Mar 27 '16 at 0:21
psusipsusi
31.2k15088
Thanks for your answer. But I found it easier to reinstall the operating system and putting on ubuntu Mate 15.10. Apparently, the new kernel updates were causing me the problem because since that I have not updated the problem didn't appear again.
– Daniel González
Apr 15 '16 at 16:10
add a comment |
Apparently you marked the partition as ext3 in /etc/fstab, when in fact it is ext4 ( or you have since converted it with tune2fs ). Change the ext3 designation to ext4 in /etc/fstab.
answered Mar 27 '16 at 0:21
psusipsusi
31.2k15088
Apparently you marked the partition as ext3 in /etc/fstab, when in fact it is ext4 ( or you have since converted it with tune2fs ). Change the ext3 designation to ext4 in /etc/fstab.
answered Mar 27 '16 at 0:21
psusipsusi
31.2k15088
answered Mar 27 '16 at 0:21
psusipsusi
31.2k15088
answered Mar 27 '16 at 0:21
psusipsusi
31.2k15088
answered Mar 27 '16 at 0:21
psusipsusi
31.2k15088
31.2k15088
Thanks for your answer. But I found it easier to reinstall the operating system and putting on ubuntu Mate 15.10. Apparently, the new kernel updates were causing me the problem because since that I have not updated the problem didn't appear again.
– Daniel González
Apr 15 '16 at 16:10
add a comment |
Thanks for your answer. But I found it easier to reinstall the operating system and putting on ubuntu Mate 15.10. Apparently, the new kernel updates were causing me the problem because since that I have not updated the problem didn't appear again.
– Daniel González
Apr 15 '16 at 16:10
Thanks for your answer. But I found it easier to reinstall the operating system and putting on ubuntu Mate 15.10. Apparently, the new kernel updates were causing me the problem because since that I have not updated the problem didn't appear again.
– Daniel González
Apr 15 '16 at 16:10
Thanks for your answer. But I found it easier to reinstall the operating system and putting on ubuntu Mate 15.10. Apparently, the new kernel updates were causing me the problem because since that I have not updated the problem didn't appear again.
– Daniel González
Apr 15 '16 at 16:10
add a comment |
I saw this bright red message in my dmesg output and got curious although I am not experiencing any problems. I checked the hint from psusi's answer but /etc/fstab is set to ext4 on my system. After some more research I found this post in the arch forum with an explanation that sounds resonable to me. The gist: The ext-fs driver supports multiple versions and checks which one works if none is specified at boot time. My kernel command line reads root=/dev/xvda ro console=xvc0 console=hvc0 so it looks like auto-detection is required.
answered Jan 25 at 19:05
wediwedi
1113
add a comment |
I saw this bright red message in my dmesg output and got curious although I am not experiencing any problems. I checked the hint from psusi's answer but /etc/fstab is set to ext4 on my system. After some more research I found this post in the arch forum with an explanation that sounds resonable to me. The gist: The ext-fs driver supports multiple versions and checks which one works if none is specified at boot time. My kernel command line reads root=/dev/xvda ro console=xvc0 console=hvc0 so it looks like auto-detection is required.
answered Jan 25 at 19:05
wediwedi
1113
add a comment |
I saw this bright red message in my dmesg output and got curious although I am not experiencing any problems. I checked the hint from psusi's answer but /etc/fstab is set to ext4 on my system. After some more research I found this post in the arch forum with an explanation that sounds resonable to me. The gist: The ext-fs driver supports multiple versions and checks which one works if none is specified at boot time. My kernel command line reads root=/dev/xvda ro console=xvc0 console=hvc0 so it looks like auto-detection is required.
answered Jan 25 at 19:05
wediwedi
1113
I saw this bright red message in my dmesg output and got curious although I am not experiencing any problems. I checked the hint from psusi's answer but /etc/fstab is set to ext4 on my system. After some more research I found this post in the arch forum with an explanation that sounds resonable to me. The gist: The ext-fs driver supports multiple versions and checks which one works if none is specified at boot time. My kernel command line reads root=/dev/xvda ro console=xvc0 console=hvc0 so it looks like auto-detection is required.
answered Jan 25 at 19:05
wediwedi
1113
answered Jan 25 at 19:05
wediwedi
1113
answered Jan 25 at 19:05
wediwedi
1113
answered Jan 25 at 19:05
wediwedi
1113
1113
add a comment |
add a comment |
This just happened to me recently after a package upgrade leaving me with a low resolution login screen that wouldn't work. (Ubuntu 16.04)
- Type Ctrl+Alt+F1 to get a terminal and login via this terminal.
Run following commands:
sudo apt update
sudo apt upgrade
sudo reboot
Hope this helps ...
edited Feb 16 '17 at 12:16
d a i s y
3,34782444
answered Feb 16 '17 at 11:22
JohnJohn
11
add a comment |
This just happened to me recently after a package upgrade leaving me with a low resolution login screen that wouldn't work. (Ubuntu 16.04)
- Type Ctrl+Alt+F1 to get a terminal and login via this terminal.
Run following commands:
sudo apt update
sudo apt upgrade
sudo reboot
Hope this helps ...
edited Feb 16 '17 at 12:16
d a i s y
3,34782444
answered Feb 16 '17 at 11:22
JohnJohn
11
add a comment |
This just happened to me recently after a package upgrade leaving me with a low resolution login screen that wouldn't work. (Ubuntu 16.04)
- Type Ctrl+Alt+F1 to get a terminal and login via this terminal.
Run following commands:
sudo apt update
sudo apt upgrade
sudo reboot
Hope this helps ...
edited Feb 16 '17 at 12:16
d a i s y
3,34782444
answered Feb 16 '17 at 11:22
JohnJohn
11
This just happened to me recently after a package upgrade leaving me with a low resolution login screen that wouldn't work. (Ubuntu 16.04)
- Type Ctrl+Alt+F1 to get a terminal and login via this terminal.
Run following commands:
sudo apt update
sudo apt upgrade
sudo reboot
Hope this helps ...
edited Feb 16 '17 at 12:16
d a i s y
3,34782444
answered Feb 16 '17 at 11:22
JohnJohn
11
edited Feb 16 '17 at 12:16
d a i s y
3,34782444
edited Feb 16 '17 at 12:16
d a i s y
3,34782444
edited Feb 16 '17 at 12:16
d a i s y
3,34782444
3,34782444
answered Feb 16 '17 at 11:22
JohnJohn
11
answered Feb 16 '17 at 11:22
JohnJohn
11
answered Feb 16 '17 at 11:22
JohnJohn
11
11
add a comment |
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%2f750518%2ferror-ext4-fs-sda6-couldnt-mount-as-ext3-due-to-feature-incompatibilities%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
