After resizing partition Ubuntu boots in emergency mode

-1

After resizing /home directory on my Ubuntu 18.04 (used Gparted while booting from LinuxMint-LiveCD my Ubuntu boots exclusively in emergency mode. What can I do to fix it?

I ran lsblk in emergency mode, and saw that:

my /dev/sda3 (/home) partition was unmounted (its size was changed)

unallocated space presumably still is considered as part of sda device (because sda size is shown as before 931Gb), but not recognized as /dev/sda4 or anyhow.

After mounting /dev/sda3 to the system I am able to start a normal session, but after reboot it happens again.

What can I do to make my Ubuntu boot normally again?

Content of /etc/fstab:

# <file system> <mount point>   <type>  <options>       <dump>  <pass>

# / was on /dev/sda2 during installation

UUID=d5eb2396-e9df-4a63-84da-d628c915d809 /               ext4    errors=remount-ro 0       1

# /boot/efi was on /dev/sda1 during installation

UUID=3E0D-5C34  /boot/efi       vfat    utf8,umask=007,gid=46 0       1

# /home was on /dev/sda3 during installation

UUID=f79558ec-8e55-4fa5-81ed-b6c77c87a43b /home           ext4    defaults        0       2

/swapfile                                 none            swap    sw              0       0

edited Mar 21 at 8:51

asked Mar 19 at 10:32

Ivan K.

524

It will help if you add the contents of /etc/fstab and the output of the command blkid to your question

– Charles Green
Mar 19 at 13:09

1

Welcome to AskUbuntu! Unfortunately you've added your blkid output twice and your fstab content not at all. Please copy and paste text rather than posting images of console output. Thank you for helping us help you

– Elder Geek
Mar 19 at 18:28

3

Welcome to Ask Ubuntu! What are the error messages from the failed boot? Also please do not post screenshots of the terminal. Paste the text directly to your question and apply code formatting.

– Melebius
Mar 20 at 10:11

Re. "P.S. I'm sorry for posting images instead of pasting text, I just find it yet confusing to deal with local markup rules. If I'd just pasted output here it would look unreadable, images do the job much better", Please read points 1-5 in this question.

– DK Bose
Mar 21 at 2:25

1

I'd upvote question if you fixed images of code, that really grinds my gears. Paste code from terminal.

– FreeSoftwareServers
Mar 21 at 4:08

|
show 1 more comment

-1

After resizing /home directory on my Ubuntu 18.04 (used Gparted while booting from LinuxMint-LiveCD my Ubuntu boots exclusively in emergency mode. What can I do to fix it?

I ran lsblk in emergency mode, and saw that:

my /dev/sda3 (/home) partition was unmounted (its size was changed)

unallocated space presumably still is considered as part of sda device (because sda size is shown as before 931Gb), but not recognized as /dev/sda4 or anyhow.

After mounting /dev/sda3 to the system I am able to start a normal session, but after reboot it happens again.

What can I do to make my Ubuntu boot normally again?

Content of /etc/fstab:

# <file system> <mount point>   <type>  <options>       <dump>  <pass>

# / was on /dev/sda2 during installation

UUID=d5eb2396-e9df-4a63-84da-d628c915d809 /               ext4    errors=remount-ro 0       1

# /boot/efi was on /dev/sda1 during installation

UUID=3E0D-5C34  /boot/efi       vfat    utf8,umask=007,gid=46 0       1

# /home was on /dev/sda3 during installation

UUID=f79558ec-8e55-4fa5-81ed-b6c77c87a43b /home           ext4    defaults        0       2

/swapfile                                 none            swap    sw              0       0

edited Mar 21 at 8:51

asked Mar 19 at 10:32

Ivan K.

524

It will help if you add the contents of /etc/fstab and the output of the command blkid to your question

– Charles Green
Mar 19 at 13:09

1

Welcome to AskUbuntu! Unfortunately you've added your blkid output twice and your fstab content not at all. Please copy and paste text rather than posting images of console output. Thank you for helping us help you

– Elder Geek
Mar 19 at 18:28

3

Welcome to Ask Ubuntu! What are the error messages from the failed boot? Also please do not post screenshots of the terminal. Paste the text directly to your question and apply code formatting.

– Melebius
Mar 20 at 10:11

Re. "P.S. I'm sorry for posting images instead of pasting text, I just find it yet confusing to deal with local markup rules. If I'd just pasted output here it would look unreadable, images do the job much better", Please read points 1-5 in this question.

– DK Bose
Mar 21 at 2:25

1

I'd upvote question if you fixed images of code, that really grinds my gears. Paste code from terminal.

– FreeSoftwareServers
Mar 21 at 4:08

|
show 1 more comment

-1

After resizing /home directory on my Ubuntu 18.04 (used Gparted while booting from LinuxMint-LiveCD my Ubuntu boots exclusively in emergency mode. What can I do to fix it?

I ran lsblk in emergency mode, and saw that:

my /dev/sda3 (/home) partition was unmounted (its size was changed)

unallocated space presumably still is considered as part of sda device (because sda size is shown as before 931Gb), but not recognized as /dev/sda4 or anyhow.

After mounting /dev/sda3 to the system I am able to start a normal session, but after reboot it happens again.

What can I do to make my Ubuntu boot normally again?

Content of /etc/fstab:

# <file system> <mount point>   <type>  <options>       <dump>  <pass>

# / was on /dev/sda2 during installation

UUID=d5eb2396-e9df-4a63-84da-d628c915d809 /               ext4    errors=remount-ro 0       1

# /boot/efi was on /dev/sda1 during installation

UUID=3E0D-5C34  /boot/efi       vfat    utf8,umask=007,gid=46 0       1

# /home was on /dev/sda3 during installation

UUID=f79558ec-8e55-4fa5-81ed-b6c77c87a43b /home           ext4    defaults        0       2

/swapfile                                 none            swap    sw              0       0

edited Mar 21 at 8:51

asked Mar 19 at 10:32

Ivan K.

524

After resizing /home directory on my Ubuntu 18.04 (used Gparted while booting from LinuxMint-LiveCD my Ubuntu boots exclusively in emergency mode. What can I do to fix it?

I ran lsblk in emergency mode, and saw that:

my /dev/sda3 (/home) partition was unmounted (its size was changed)

unallocated space presumably still is considered as part of sda device (because sda size is shown as before 931Gb), but not recognized as /dev/sda4 or anyhow.

After mounting /dev/sda3 to the system I am able to start a normal session, but after reboot it happens again.

What can I do to make my Ubuntu boot normally again?

Content of /etc/fstab:

# <file system> <mount point>   <type>  <options>       <dump>  <pass>

# / was on /dev/sda2 during installation

UUID=d5eb2396-e9df-4a63-84da-d628c915d809 /               ext4    errors=remount-ro 0       1

# /boot/efi was on /dev/sda1 during installation

UUID=3E0D-5C34  /boot/efi       vfat    utf8,umask=007,gid=46 0       1

# /home was on /dev/sda3 during installation

UUID=f79558ec-8e55-4fa5-81ed-b6c77c87a43b /home           ext4    defaults        0       2

/swapfile                                 none            swap    sw              0       0

boot partitioning gparted mint

edited Mar 21 at 8:51

asked Mar 19 at 10:32

Ivan K.

524

edited Mar 21 at 8:51

asked Mar 19 at 10:32

Ivan K.

524

edited Mar 21 at 8:51

asked Mar 19 at 10:32

Ivan K.

524

asked Mar 19 at 10:32

Ivan K.

524

asked Mar 19 at 10:32

Ivan K.

524

It will help if you add the contents of /etc/fstab and the output of the command blkid to your question

– Charles Green
Mar 19 at 13:09

1

Welcome to AskUbuntu! Unfortunately you've added your blkid output twice and your fstab content not at all. Please copy and paste text rather than posting images of console output. Thank you for helping us help you

– Elder Geek
Mar 19 at 18:28

3

Welcome to Ask Ubuntu! What are the error messages from the failed boot? Also please do not post screenshots of the terminal. Paste the text directly to your question and apply code formatting.

– Melebius
Mar 20 at 10:11

Re. "P.S. I'm sorry for posting images instead of pasting text, I just find it yet confusing to deal with local markup rules. If I'd just pasted output here it would look unreadable, images do the job much better", Please read points 1-5 in this question.

– DK Bose
Mar 21 at 2:25

1

I'd upvote question if you fixed images of code, that really grinds my gears. Paste code from terminal.

– FreeSoftwareServers
Mar 21 at 4:08

|
show 1 more comment

It will help if you add the contents of /etc/fstab and the output of the command blkid to your question

– Charles Green
Mar 19 at 13:09

1

Welcome to AskUbuntu! Unfortunately you've added your blkid output twice and your fstab content not at all. Please copy and paste text rather than posting images of console output. Thank you for helping us help you

– Elder Geek
Mar 19 at 18:28

3

Welcome to Ask Ubuntu! What are the error messages from the failed boot? Also please do not post screenshots of the terminal. Paste the text directly to your question and apply code formatting.

– Melebius
Mar 20 at 10:11

Re. "P.S. I'm sorry for posting images instead of pasting text, I just find it yet confusing to deal with local markup rules. If I'd just pasted output here it would look unreadable, images do the job much better", Please read points 1-5 in this question.

– DK Bose
Mar 21 at 2:25

1

I'd upvote question if you fixed images of code, that really grinds my gears. Paste code from terminal.

– FreeSoftwareServers
Mar 21 at 4:08

It will help if you add the contents of /etc/fstab and the output of the command blkid to your question

– Charles Green
Mar 19 at 13:09

Welcome to AskUbuntu! Unfortunately you've added your blkid output twice and your fstab content not at all. Please copy and paste text rather than posting images of console output. Thank you for helping us help you

– Elder Geek
Mar 19 at 18:28

Welcome to Ask Ubuntu! What are the error messages from the failed boot? Also please do not post screenshots of the terminal. Paste the text directly to your question and apply code formatting.

– Melebius
Mar 20 at 10:11

Re. "P.S. I'm sorry for posting images instead of pasting text, I just find it yet confusing to deal with local markup rules. If I'd just pasted output here it would look unreadable, images do the job much better", Please read points 1-5 in this question.

– DK Bose
Mar 21 at 2:25

I'd upvote question if you fixed images of code, that really grinds my gears. Paste code from terminal.

– FreeSoftwareServers
Mar 21 at 4:08

|
show 1 more comment

1 Answer
1

active

oldest

votes

I solved the problem in the following manner:

In the emergency mode, I ran journalctl -xb | less and searched for errors.

It appeared that /dev/sda3 couldn't pass control sum check and therefore was refused to be mounted. Fortunately right there was a proposition to run manually fsck /dev/sda3 to fix it.

I ran fsck /dev/sda3 and, in a while, it fixed the problem.

Since then I didn't have problems booting into Ubuntu.

edited Mar 21 at 7:04

Melebius

5,09552040

answered Mar 20 at 15:27

Ivan K.

524

Less of a good idea, but another thing that may pass for a possible solution, in a similar case, is to change the value of <pass> parameter from 2 to 0 in /etc/fstab file for the corresponding partition. Then it won't be checked at all by fsck wiki. Probably, maybe handy if certain properties of a partition change very often

– Ivan K.
Mar 21 at 9:08

While I understand what you would be doing if you changed the value of <pass> I would not encourage you to do this. Failing the boot fsck indicates that there is a problem with the file system structure, and proceeding further could place the data stored on your disc in danger.

– Charles Green
Mar 22 at 14:01

add a comment |

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
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1126900%2fafter-resizing-partition-ubuntu-boots-in-emergency-mode%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

I solved the problem in the following manner:

In the emergency mode, I ran journalctl -xb | less and searched for errors.

It appeared that /dev/sda3 couldn't pass control sum check and therefore was refused to be mounted. Fortunately right there was a proposition to run manually fsck /dev/sda3 to fix it.

I ran fsck /dev/sda3 and, in a while, it fixed the problem.

Since then I didn't have problems booting into Ubuntu.

edited Mar 21 at 7:04

Melebius

5,09552040

answered Mar 20 at 15:27

Ivan K.

524

Less of a good idea, but another thing that may pass for a possible solution, in a similar case, is to change the value of <pass> parameter from 2 to 0 in /etc/fstab file for the corresponding partition. Then it won't be checked at all by fsck wiki. Probably, maybe handy if certain properties of a partition change very often

– Ivan K.
Mar 21 at 9:08

While I understand what you would be doing if you changed the value of <pass> I would not encourage you to do this. Failing the boot fsck indicates that there is a problem with the file system structure, and proceeding further could place the data stored on your disc in danger.

– Charles Green
Mar 22 at 14:01

add a comment |

I solved the problem in the following manner:

In the emergency mode, I ran journalctl -xb | less and searched for errors.

It appeared that /dev/sda3 couldn't pass control sum check and therefore was refused to be mounted. Fortunately right there was a proposition to run manually fsck /dev/sda3 to fix it.

I ran fsck /dev/sda3 and, in a while, it fixed the problem.

Since then I didn't have problems booting into Ubuntu.

edited Mar 21 at 7:04

Melebius

5,09552040

answered Mar 20 at 15:27

Ivan K.

524

Less of a good idea, but another thing that may pass for a possible solution, in a similar case, is to change the value of <pass> parameter from 2 to 0 in /etc/fstab file for the corresponding partition. Then it won't be checked at all by fsck wiki. Probably, maybe handy if certain properties of a partition change very often

– Ivan K.
Mar 21 at 9:08

While I understand what you would be doing if you changed the value of <pass> I would not encourage you to do this. Failing the boot fsck indicates that there is a problem with the file system structure, and proceeding further could place the data stored on your disc in danger.

– Charles Green
Mar 22 at 14:01

add a comment |

I solved the problem in the following manner:

In the emergency mode, I ran journalctl -xb | less and searched for errors.

It appeared that /dev/sda3 couldn't pass control sum check and therefore was refused to be mounted. Fortunately right there was a proposition to run manually fsck /dev/sda3 to fix it.

I ran fsck /dev/sda3 and, in a while, it fixed the problem.

Since then I didn't have problems booting into Ubuntu.

edited Mar 21 at 7:04

Melebius

5,09552040

answered Mar 20 at 15:27

Ivan K.

524

I solved the problem in the following manner:

In the emergency mode, I ran journalctl -xb | less and searched for errors.

It appeared that /dev/sda3 couldn't pass control sum check and therefore was refused to be mounted. Fortunately right there was a proposition to run manually fsck /dev/sda3 to fix it.

I ran fsck /dev/sda3 and, in a while, it fixed the problem.

Since then I didn't have problems booting into Ubuntu.

edited Mar 21 at 7:04

Melebius

5,09552040

answered Mar 20 at 15:27

Ivan K.

524

edited Mar 21 at 7:04

Melebius

5,09552040

edited Mar 21 at 7:04

Melebius

5,09552040

edited Mar 21 at 7:04

Melebius

5,09552040

answered Mar 20 at 15:27

Ivan K.

524

answered Mar 20 at 15:27

Ivan K.

524

answered Mar 20 at 15:27

Ivan K.

524

Less of a good idea, but another thing that may pass for a possible solution, in a similar case, is to change the value of <pass> parameter from 2 to 0 in /etc/fstab file for the corresponding partition. Then it won't be checked at all by fsck wiki. Probably, maybe handy if certain properties of a partition change very often

– Ivan K.
Mar 21 at 9:08

While I understand what you would be doing if you changed the value of <pass> I would not encourage you to do this. Failing the boot fsck indicates that there is a problem with the file system structure, and proceeding further could place the data stored on your disc in danger.

– Charles Green
Mar 22 at 14:01

add a comment |

Less of a good idea, but another thing that may pass for a possible solution, in a similar case, is to change the value of <pass> parameter from 2 to 0 in /etc/fstab file for the corresponding partition. Then it won't be checked at all by fsck wiki. Probably, maybe handy if certain properties of a partition change very often

– Ivan K.
Mar 21 at 9:08

While I understand what you would be doing if you changed the value of <pass> I would not encourage you to do this. Failing the boot fsck indicates that there is a problem with the file system structure, and proceeding further could place the data stored on your disc in danger.

– Charles Green
Mar 22 at 14:01

Less of a good idea, but another thing that may pass for a possible solution, in a similar case, is to change the value of <pass> parameter from 2 to 0 in /etc/fstab file for the corresponding partition. Then it won't be checked at all by fsck wiki. Probably, maybe handy if certain properties of a partition change very often

– Ivan K.
Mar 21 at 9:08

While I understand what you would be doing if you changed the value of <pass> I would not encourage you to do this. Failing the boot fsck indicates that there is a problem with the file system structure, and proceeding further could place the data stored on your disc in danger.

– Charles Green
Mar 22 at 14:01

add a comment |

draft saved

draft discarded

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.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Cfxtrjtrk