Why am I being thrown into an emergency shell when booting?
I have set up Arch Linux with full-disk encryption and partitioned my system disk using LVM. I just changed the motherboard, CPU and RAM of my machine, and after enabling legacy boot and disabling secure boot it booted fine at least once — I was asked for the LUKS passphrase, the GRUB menu showed up, lightdm and Awesome WM started fine, and I used the system for some hours. Next time I booted the LUKS prompt showed up, and I got the GRUB menu, but shortly afterwards my screen looked like this:
Starting version 241.7-2-arch
ERROR: device '/dev/mapper/vg-root' not found. Skipping fsck.
mount: /new_root: no filesystem type specified.
You are now being dropped into an emergency shell.
sh: can't access tty: job control turned off
[rootfs ]#
The really weird thing is that /dev/mapper/vg-root clearly does exist: I was able to mount it, mount my home directory within it, chroot to it and see all my files, and finally when I ran reboot
outside the chroot it took me straight to the lightdm login screen. Why reboot
would continue the boot rather than restart the machine is beyond me, but might just be a red herring.
What is going on here? Is there some known issue with this version of systemd?
arch-linux systemd boot lvm
add a comment |
I have set up Arch Linux with full-disk encryption and partitioned my system disk using LVM. I just changed the motherboard, CPU and RAM of my machine, and after enabling legacy boot and disabling secure boot it booted fine at least once — I was asked for the LUKS passphrase, the GRUB menu showed up, lightdm and Awesome WM started fine, and I used the system for some hours. Next time I booted the LUKS prompt showed up, and I got the GRUB menu, but shortly afterwards my screen looked like this:
Starting version 241.7-2-arch
ERROR: device '/dev/mapper/vg-root' not found. Skipping fsck.
mount: /new_root: no filesystem type specified.
You are now being dropped into an emergency shell.
sh: can't access tty: job control turned off
[rootfs ]#
The really weird thing is that /dev/mapper/vg-root clearly does exist: I was able to mount it, mount my home directory within it, chroot to it and see all my files, and finally when I ran reboot
outside the chroot it took me straight to the lightdm login screen. Why reboot
would continue the boot rather than restart the machine is beyond me, but might just be a red herring.
What is going on here? Is there some known issue with this version of systemd?
arch-linux systemd boot lvm
add a comment |
I have set up Arch Linux with full-disk encryption and partitioned my system disk using LVM. I just changed the motherboard, CPU and RAM of my machine, and after enabling legacy boot and disabling secure boot it booted fine at least once — I was asked for the LUKS passphrase, the GRUB menu showed up, lightdm and Awesome WM started fine, and I used the system for some hours. Next time I booted the LUKS prompt showed up, and I got the GRUB menu, but shortly afterwards my screen looked like this:
Starting version 241.7-2-arch
ERROR: device '/dev/mapper/vg-root' not found. Skipping fsck.
mount: /new_root: no filesystem type specified.
You are now being dropped into an emergency shell.
sh: can't access tty: job control turned off
[rootfs ]#
The really weird thing is that /dev/mapper/vg-root clearly does exist: I was able to mount it, mount my home directory within it, chroot to it and see all my files, and finally when I ran reboot
outside the chroot it took me straight to the lightdm login screen. Why reboot
would continue the boot rather than restart the machine is beyond me, but might just be a red herring.
What is going on here? Is there some known issue with this version of systemd?
arch-linux systemd boot lvm
I have set up Arch Linux with full-disk encryption and partitioned my system disk using LVM. I just changed the motherboard, CPU and RAM of my machine, and after enabling legacy boot and disabling secure boot it booted fine at least once — I was asked for the LUKS passphrase, the GRUB menu showed up, lightdm and Awesome WM started fine, and I used the system for some hours. Next time I booted the LUKS prompt showed up, and I got the GRUB menu, but shortly afterwards my screen looked like this:
Starting version 241.7-2-arch
ERROR: device '/dev/mapper/vg-root' not found. Skipping fsck.
mount: /new_root: no filesystem type specified.
You are now being dropped into an emergency shell.
sh: can't access tty: job control turned off
[rootfs ]#
The really weird thing is that /dev/mapper/vg-root clearly does exist: I was able to mount it, mount my home directory within it, chroot to it and see all my files, and finally when I ran reboot
outside the chroot it took me straight to the lightdm login screen. Why reboot
would continue the boot rather than restart the machine is beyond me, but might just be a red herring.
What is going on here? Is there some known issue with this version of systemd?
arch-linux systemd boot lvm
arch-linux systemd boot lvm
asked 2 mins ago
l0b0l0b0
28.5k19121248
28.5k19121248
add a comment |
add a comment |
0
active
oldest
votes
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%2f507097%2fwhy-am-i-being-thrown-into-an-emergency-shell-when-booting%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f507097%2fwhy-am-i-being-thrown-into-an-emergency-shell-when-booting%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