Ubuntu 16.04: Can only boot in recovery mode
What happened:
1. Ubuntu 16.04 works fine
2. Emergency in our building => computer was forced to shut down immediately
3. Since then: Ubuntu doesn't boot properly
3.1 Screen stays gray not black before login screen appears
3.2 Recovery mode -> fsck -> resume boot -> Everything works fine
What I found in journalctl boot logs:
/dev/sda2 contains a file system with errors, check forced.
/dev/sda2: Resize inode not valid.
/dev/sda2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
I guess I need to run fsck -a /dev/sda2.
Can it harm my system in anyway?
Do I need to unmount sda2 first?
fdisk -l says:
/dev/sda1 2048 1126399 1124352 549M EFI System
/dev/sda2 1126400 3174399 2048000 1000M BIOS boot
/dev/sda3 3174400 35942399 32768000 15.6G Linux swap
/dev/sda4 35942400 7501475839 7465533440 3.5T Microsoft basic data
16.04 boot fsck
asked Jun 27 '18 at 6:55
ninjaninja
234
add a comment |
What happened:
1. Ubuntu 16.04 works fine
2. Emergency in our building => computer was forced to shut down immediately
3. Since then: Ubuntu doesn't boot properly
3.1 Screen stays gray not black before login screen appears
3.2 Recovery mode -> fsck -> resume boot -> Everything works fine
What I found in journalctl boot logs:
/dev/sda2 contains a file system with errors, check forced.
/dev/sda2: Resize inode not valid.
/dev/sda2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
I guess I need to run fsck -a /dev/sda2.
Can it harm my system in anyway?
Do I need to unmount sda2 first?
fdisk -l says:
/dev/sda1 2048 1126399 1124352 549M EFI System
/dev/sda2 1126400 3174399 2048000 1000M BIOS boot
/dev/sda3 3174400 35942399 32768000 15.6G Linux swap
/dev/sda4 35942400 7501475839 7465533440 3.5T Microsoft basic data
16.04 boot fsck
asked Jun 27 '18 at 6:55
ninjaninja
234
add a comment |
What happened:
1. Ubuntu 16.04 works fine
2. Emergency in our building => computer was forced to shut down immediately
3. Since then: Ubuntu doesn't boot properly
3.1 Screen stays gray not black before login screen appears
3.2 Recovery mode -> fsck -> resume boot -> Everything works fine
What I found in journalctl boot logs:
/dev/sda2 contains a file system with errors, check forced.
/dev/sda2: Resize inode not valid.
/dev/sda2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
I guess I need to run fsck -a /dev/sda2.
Can it harm my system in anyway?
Do I need to unmount sda2 first?
fdisk -l says:
/dev/sda1 2048 1126399 1124352 549M EFI System
/dev/sda2 1126400 3174399 2048000 1000M BIOS boot
/dev/sda3 3174400 35942399 32768000 15.6G Linux swap
/dev/sda4 35942400 7501475839 7465533440 3.5T Microsoft basic data
16.04 boot fsck
asked Jun 27 '18 at 6:55
ninjaninja
234
What happened:
1. Ubuntu 16.04 works fine
2. Emergency in our building => computer was forced to shut down immediately
3. Since then: Ubuntu doesn't boot properly
3.1 Screen stays gray not black before login screen appears
3.2 Recovery mode -> fsck -> resume boot -> Everything works fine
What I found in journalctl boot logs:
/dev/sda2 contains a file system with errors, check forced.
/dev/sda2: Resize inode not valid.
/dev/sda2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
I guess I need to run fsck -a /dev/sda2.
Can it harm my system in anyway?
Do I need to unmount sda2 first?
fdisk -l says:
/dev/sda1 2048 1126399 1124352 549M EFI System
/dev/sda2 1126400 3174399 2048000 1000M BIOS boot
/dev/sda3 3174400 35942399 32768000 15.6G Linux swap
/dev/sda4 35942400 7501475839 7465533440 3.5T Microsoft basic data
16.04 boot fsck
16.04 boot fsck
asked Jun 27 '18 at 6:55
ninjaninja
234
asked Jun 27 '18 at 6:55
ninjaninja
234
edited Jun 27 '18 at 8:28
ninja
asked Jun 27 '18 at 6:55
ninjaninja
234
asked Jun 27 '18 at 6:55
ninjaninja
234
asked Jun 27 '18 at 6:55
ninjaninja
234
234
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Your filesystem is inconsistent, so you need to run fsck as you write.
It's best to unmount /dev/sda2 if possible, or boot from a Live media, and then do fsck
Will it harm ? It will bring your filesystem back to a consistent state, clearing dangling inodes and block. You will probably not loose data, unless
your disk is severely crashed, but then data is probably lost anyway.
A good backup from yesterday is always a good asset to have.
edited 10 hours ago
Elder Geek
27.3k954127
answered Jun 27 '18 at 8:37
Soren ASoren A
3,4781924
Thanks for your answer. I am a little bit confused now. When I sayfsck -A /dev/sda2it says/dev/sda4 is mountedandWARNING!!! The filesystem is mounted. If you continue you ***WILL*** cause ***SEVERE*** filesystem damage. Do you want to continue?I don't want to damage /dev/sda4, I only want to repair /dev/sda2.
– ninja
Jun 27 '18 at 8:57
Sorry, I misunderstood. I thought that you where in GRUB shell. The best to unmount /dev/sda2 if possible, or boot from a Live media, and then do fsck. I don't think that you will damage the filesystem by doing it on the mounted device, if you reboot immediately after.
– Soren A
Jun 27 '18 at 11:09
It worked when I tried it in GRUB shell.
– ninja
Jun 27 '18 at 12:24
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%2f1050063%2fubuntu-16-04-can-only-boot-in-recovery-mode%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
Your filesystem is inconsistent, so you need to run fsck as you write.
It's best to unmount /dev/sda2 if possible, or boot from a Live media, and then do fsck
Will it harm ? It will bring your filesystem back to a consistent state, clearing dangling inodes and block. You will probably not loose data, unless
your disk is severely crashed, but then data is probably lost anyway.
A good backup from yesterday is always a good asset to have.
edited 10 hours ago
Elder Geek
27.3k954127
answered Jun 27 '18 at 8:37
Soren ASoren A
3,4781924
Thanks for your answer. I am a little bit confused now. When I sayfsck -A /dev/sda2it says/dev/sda4 is mountedandWARNING!!! The filesystem is mounted. If you continue you ***WILL*** cause ***SEVERE*** filesystem damage. Do you want to continue?I don't want to damage /dev/sda4, I only want to repair /dev/sda2.
– ninja
Jun 27 '18 at 8:57
Sorry, I misunderstood. I thought that you where in GRUB shell. The best to unmount /dev/sda2 if possible, or boot from a Live media, and then do fsck. I don't think that you will damage the filesystem by doing it on the mounted device, if you reboot immediately after.
– Soren A
Jun 27 '18 at 11:09
It worked when I tried it in GRUB shell.
– ninja
Jun 27 '18 at 12:24
add a comment |
Your filesystem is inconsistent, so you need to run fsck as you write.
It's best to unmount /dev/sda2 if possible, or boot from a Live media, and then do fsck
Will it harm ? It will bring your filesystem back to a consistent state, clearing dangling inodes and block. You will probably not loose data, unless
your disk is severely crashed, but then data is probably lost anyway.
A good backup from yesterday is always a good asset to have.
edited 10 hours ago
Elder Geek
27.3k954127
answered Jun 27 '18 at 8:37
Soren ASoren A
3,4781924
Thanks for your answer. I am a little bit confused now. When I sayfsck -A /dev/sda2it says/dev/sda4 is mountedandWARNING!!! The filesystem is mounted. If you continue you ***WILL*** cause ***SEVERE*** filesystem damage. Do you want to continue?I don't want to damage /dev/sda4, I only want to repair /dev/sda2.
– ninja
Jun 27 '18 at 8:57
Sorry, I misunderstood. I thought that you where in GRUB shell. The best to unmount /dev/sda2 if possible, or boot from a Live media, and then do fsck. I don't think that you will damage the filesystem by doing it on the mounted device, if you reboot immediately after.
– Soren A
Jun 27 '18 at 11:09
It worked when I tried it in GRUB shell.
– ninja
Jun 27 '18 at 12:24
add a comment |
Your filesystem is inconsistent, so you need to run fsck as you write.
It's best to unmount /dev/sda2 if possible, or boot from a Live media, and then do fsck
Will it harm ? It will bring your filesystem back to a consistent state, clearing dangling inodes and block. You will probably not loose data, unless
your disk is severely crashed, but then data is probably lost anyway.
A good backup from yesterday is always a good asset to have.
edited 10 hours ago
Elder Geek
27.3k954127
answered Jun 27 '18 at 8:37
Soren ASoren A
3,4781924
Your filesystem is inconsistent, so you need to run fsck as you write.
It's best to unmount /dev/sda2 if possible, or boot from a Live media, and then do fsck
Will it harm ? It will bring your filesystem back to a consistent state, clearing dangling inodes and block. You will probably not loose data, unless
your disk is severely crashed, but then data is probably lost anyway.
A good backup from yesterday is always a good asset to have.
edited 10 hours ago
Elder Geek
27.3k954127
answered Jun 27 '18 at 8:37
Soren ASoren A
3,4781924
edited 10 hours ago
Elder Geek
27.3k954127
edited 10 hours ago
Elder Geek
27.3k954127
edited 10 hours ago
Elder Geek
27.3k954127
27.3k954127
answered Jun 27 '18 at 8:37
Soren ASoren A
3,4781924
answered Jun 27 '18 at 8:37
Soren ASoren A
3,4781924
answered Jun 27 '18 at 8:37
Soren ASoren A
3,4781924
3,4781924
Thanks for your answer. I am a little bit confused now. When I sayfsck -A /dev/sda2it says/dev/sda4 is mountedandWARNING!!! The filesystem is mounted. If you continue you ***WILL*** cause ***SEVERE*** filesystem damage. Do you want to continue?I don't want to damage /dev/sda4, I only want to repair /dev/sda2.
– ninja
Jun 27 '18 at 8:57
Sorry, I misunderstood. I thought that you where in GRUB shell. The best to unmount /dev/sda2 if possible, or boot from a Live media, and then do fsck. I don't think that you will damage the filesystem by doing it on the mounted device, if you reboot immediately after.
– Soren A
Jun 27 '18 at 11:09
It worked when I tried it in GRUB shell.
– ninja
Jun 27 '18 at 12:24
add a comment |
Thanks for your answer. I am a little bit confused now. When I sayfsck -A /dev/sda2it says/dev/sda4 is mountedandWARNING!!! The filesystem is mounted. If you continue you ***WILL*** cause ***SEVERE*** filesystem damage. Do you want to continue?I don't want to damage /dev/sda4, I only want to repair /dev/sda2.
– ninja
Jun 27 '18 at 8:57
Sorry, I misunderstood. I thought that you where in GRUB shell. The best to unmount /dev/sda2 if possible, or boot from a Live media, and then do fsck. I don't think that you will damage the filesystem by doing it on the mounted device, if you reboot immediately after.
– Soren A
Jun 27 '18 at 11:09
It worked when I tried it in GRUB shell.
– ninja
Jun 27 '18 at 12:24
Thanks for your answer. I am a little bit confused now. When I say
fsck -A /dev/sda2 it says /dev/sda4 is mounted and WARNING!!! The filesystem is mounted. If you continue you ***WILL*** cause ***SEVERE*** filesystem damage. Do you want to continue? I don't want to damage /dev/sda4, I only want to repair /dev/sda2.– ninja
Jun 27 '18 at 8:57
Thanks for your answer. I am a little bit confused now. When I say
fsck -A /dev/sda2 it says /dev/sda4 is mounted and WARNING!!! The filesystem is mounted. If you continue you ***WILL*** cause ***SEVERE*** filesystem damage. Do you want to continue? I don't want to damage /dev/sda4, I only want to repair /dev/sda2.– ninja
Jun 27 '18 at 8:57
Sorry, I misunderstood. I thought that you where in GRUB shell. The best to unmount /dev/sda2 if possible, or boot from a Live media, and then do fsck. I don't think that you will damage the filesystem by doing it on the mounted device, if you reboot immediately after.
– Soren A
Jun 27 '18 at 11:09
Sorry, I misunderstood. I thought that you where in GRUB shell. The best to unmount /dev/sda2 if possible, or boot from a Live media, and then do fsck. I don't think that you will damage the filesystem by doing it on the mounted device, if you reboot immediately after.
– Soren A
Jun 27 '18 at 11:09
It worked when I tried it in GRUB shell.
– ninja
Jun 27 '18 at 12:24
It worked when I tried it in GRUB shell.
– ninja
Jun 27 '18 at 12:24
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%2f1050063%2fubuntu-16-04-can-only-boot-in-recovery-mode%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
