Why does bionic now freeze during LUKS boot?
up vote
0
down vote
favorite
Recently I installed 18.04 on a clean M.2 form-factor SSD, in my Dell latitude E7470 laptop, enabling full-disk encryption.
For a week or two it worked fine, but since yesterday morning, I have not been able to boot normally:
If I let the system boot as usual, after I enter my LUKS passphrase, it seems to freeze for a while, then shows me some boot messages, including a failure: "Failed to start Create Static Device Nodes in /dev". It continues for a bit, then freezes, without my reaching the X login screen.
If I select the recovery option in the grub menu, after I enter my password the LUKS partition is available. If I choose to continue at the recovery menu, the system starts up, and I get an X prompt. However, certain hardware hasn't been initialised, so support for multiple monitors and wifi (among other things) appear not be working correctly.
I have tried booting from USB, and I can mount the LUKS partition fine, and then mount the LVM2 logical volume. fsck does not return any errors.
I do not see any evidence of disk corruption after logging in via the recovery menu. I have tried "update-initramfs", but that has not made a difference.
What can I try next? I will attach a couple of photos; I don't know how to capture the log messages properly since the system hangs during boot.
photo of boot message
boot 18.04 luks
asked Nov 21 at 23:29
Nick
1
New contributor
Nick is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
favorite
Recently I installed 18.04 on a clean M.2 form-factor SSD, in my Dell latitude E7470 laptop, enabling full-disk encryption.
For a week or two it worked fine, but since yesterday morning, I have not been able to boot normally:
If I let the system boot as usual, after I enter my LUKS passphrase, it seems to freeze for a while, then shows me some boot messages, including a failure: "Failed to start Create Static Device Nodes in /dev". It continues for a bit, then freezes, without my reaching the X login screen.
If I select the recovery option in the grub menu, after I enter my password the LUKS partition is available. If I choose to continue at the recovery menu, the system starts up, and I get an X prompt. However, certain hardware hasn't been initialised, so support for multiple monitors and wifi (among other things) appear not be working correctly.
I have tried booting from USB, and I can mount the LUKS partition fine, and then mount the LVM2 logical volume. fsck does not return any errors.
I do not see any evidence of disk corruption after logging in via the recovery menu. I have tried "update-initramfs", but that has not made a difference.
What can I try next? I will attach a couple of photos; I don't know how to capture the log messages properly since the system hangs during boot.
photo of boot message
boot 18.04 luks
asked Nov 21 at 23:29
Nick
1
New contributor
Nick is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
You can use journalctl -b to display the last boot log (journalctl -b > logfile.log should create a file).
– Skaparate
Nov 22 at 2:34
What does systemctl status systemd-tmpfiles-setup-dev show?
– Skaparate
Nov 22 at 2:40
1
Thanks for both of these suggestions. They were both helpful in pointing me in the right direction.
– Nick
Nov 23 at 20:58
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Recently I installed 18.04 on a clean M.2 form-factor SSD, in my Dell latitude E7470 laptop, enabling full-disk encryption.
For a week or two it worked fine, but since yesterday morning, I have not been able to boot normally:
If I let the system boot as usual, after I enter my LUKS passphrase, it seems to freeze for a while, then shows me some boot messages, including a failure: "Failed to start Create Static Device Nodes in /dev". It continues for a bit, then freezes, without my reaching the X login screen.
If I select the recovery option in the grub menu, after I enter my password the LUKS partition is available. If I choose to continue at the recovery menu, the system starts up, and I get an X prompt. However, certain hardware hasn't been initialised, so support for multiple monitors and wifi (among other things) appear not be working correctly.
I have tried booting from USB, and I can mount the LUKS partition fine, and then mount the LVM2 logical volume. fsck does not return any errors.
I do not see any evidence of disk corruption after logging in via the recovery menu. I have tried "update-initramfs", but that has not made a difference.
What can I try next? I will attach a couple of photos; I don't know how to capture the log messages properly since the system hangs during boot.
photo of boot message
boot 18.04 luks
asked Nov 21 at 23:29
Nick
1
New contributor
Nick is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Recently I installed 18.04 on a clean M.2 form-factor SSD, in my Dell latitude E7470 laptop, enabling full-disk encryption.
For a week or two it worked fine, but since yesterday morning, I have not been able to boot normally:
If I let the system boot as usual, after I enter my LUKS passphrase, it seems to freeze for a while, then shows me some boot messages, including a failure: "Failed to start Create Static Device Nodes in /dev". It continues for a bit, then freezes, without my reaching the X login screen.
If I select the recovery option in the grub menu, after I enter my password the LUKS partition is available. If I choose to continue at the recovery menu, the system starts up, and I get an X prompt. However, certain hardware hasn't been initialised, so support for multiple monitors and wifi (among other things) appear not be working correctly.
I have tried booting from USB, and I can mount the LUKS partition fine, and then mount the LVM2 logical volume. fsck does not return any errors.
I do not see any evidence of disk corruption after logging in via the recovery menu. I have tried "update-initramfs", but that has not made a difference.
What can I try next? I will attach a couple of photos; I don't know how to capture the log messages properly since the system hangs during boot.
photo of boot message
boot 18.04 luks
boot 18.04 luks
asked Nov 21 at 23:29
Nick
1
New contributor
Nick is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Nov 21 at 23:29
Nick
1
New contributor
Nick is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Nov 21 at 23:29
Nick
1
New contributor
Nick is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Nov 21 at 23:29
Nick
1
asked Nov 21 at 23:29
Nick
1
1
New contributor
Nick is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Nick is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Nick is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
You can use journalctl -b to display the last boot log (journalctl -b > logfile.log should create a file).
– Skaparate
Nov 22 at 2:34
What does systemctl status systemd-tmpfiles-setup-dev show?
– Skaparate
Nov 22 at 2:40
1
Thanks for both of these suggestions. They were both helpful in pointing me in the right direction.
– Nick
Nov 23 at 20:58
add a comment |
You can use journalctl -b to display the last boot log (journalctl -b > logfile.log should create a file).
– Skaparate
Nov 22 at 2:34
What does systemctl status systemd-tmpfiles-setup-dev show?
– Skaparate
Nov 22 at 2:40
1
Thanks for both of these suggestions. They were both helpful in pointing me in the right direction.
– Nick
Nov 23 at 20:58
You can use journalctl -b to display the last boot log (journalctl -b > logfile.log should create a file).
– Skaparate
Nov 22 at 2:34
You can use journalctl -b to display the last boot log (journalctl -b > logfile.log should create a file).
– Skaparate
Nov 22 at 2:34
What does systemctl status systemd-tmpfiles-setup-dev show?
– Skaparate
Nov 22 at 2:40
What does systemctl status systemd-tmpfiles-setup-dev show?
– Skaparate
Nov 22 at 2:40
1
1
Thanks for both of these suggestions. They were both helpful in pointing me in the right direction.
– Nick
Nov 23 at 20:58
Thanks for both of these suggestions. They were both helpful in pointing me in the right direction.
– Nick
Nov 23 at 20:58
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
The root cause of my problem was that somehow the root partition (/) was no longer owned by the root user, which led to various sanity checks failing during boot.
Using the suggestions in the comments above helped me see other error messages which were slightly more relevant , and which by googling showed me other people in a similar situation.
I am not sure how the root partition had its owner changed but the solution was simply:
$ chown root /
After booting into recovery mode and opening a console
answered Nov 23 at 21:02
Nick
1
New contributor
Nick is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
The root cause of my problem was that somehow the root partition (/) was no longer owned by the root user, which led to various sanity checks failing during boot.
Using the suggestions in the comments above helped me see other error messages which were slightly more relevant , and which by googling showed me other people in a similar situation.
I am not sure how the root partition had its owner changed but the solution was simply:
$ chown root /
After booting into recovery mode and opening a console
answered Nov 23 at 21:02
Nick
1
New contributor
Nick is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
The root cause of my problem was that somehow the root partition (/) was no longer owned by the root user, which led to various sanity checks failing during boot.
Using the suggestions in the comments above helped me see other error messages which were slightly more relevant , and which by googling showed me other people in a similar situation.
I am not sure how the root partition had its owner changed but the solution was simply:
$ chown root /
After booting into recovery mode and opening a console
answered Nov 23 at 21:02
Nick
1
New contributor
Nick is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
up vote
0
down vote
The root cause of my problem was that somehow the root partition (/) was no longer owned by the root user, which led to various sanity checks failing during boot.
Using the suggestions in the comments above helped me see other error messages which were slightly more relevant , and which by googling showed me other people in a similar situation.
I am not sure how the root partition had its owner changed but the solution was simply:
$ chown root /
After booting into recovery mode and opening a console
answered Nov 23 at 21:02
Nick
1
New contributor
Nick is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
The root cause of my problem was that somehow the root partition (/) was no longer owned by the root user, which led to various sanity checks failing during boot.
Using the suggestions in the comments above helped me see other error messages which were slightly more relevant , and which by googling showed me other people in a similar situation.
I am not sure how the root partition had its owner changed but the solution was simply:
$ chown root /
After booting into recovery mode and opening a console
answered Nov 23 at 21:02
Nick
1
New contributor
Nick is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Nov 23 at 21:02
Nick
1
New contributor
Nick is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Nov 23 at 21:02
Nick
1
answered Nov 23 at 21:02
Nick
1
1
New contributor
Nick is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Nick is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Nick is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Nick is a new contributor. Be nice, and check out our Code of Conduct.
Nick is a new contributor. Be nice, and check out our Code of Conduct.
Nick is a new contributor. Be nice, and check out our Code of Conduct.
Nick is a new contributor. Be nice, and check out our Code of Conduct.
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%2f1094971%2fwhy-does-bionic-now-freeze-during-luks-boot%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
You can use journalctl -b to display the last boot log (journalctl -b > logfile.log should create a file).
– Skaparate
Nov 22 at 2:34
What does systemctl status systemd-tmpfiles-setup-dev show?
– Skaparate
Nov 22 at 2:40
1
Thanks for both of these suggestions. They were both helpful in pointing me in the right direction.
– Nick
Nov 23 at 20:58