Why did my virtual machine go into emergency mode after reboot?












0














root@mini2-game1-30001:~# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 9.6 (stretch)
Release: 9.6
Codename: stretch
root@mini2-game1-30001:~# reboot
[ OK ] Started File System Check on /dev/disk/by-label/x2fhome.
Checking in progress on 0 disks (100.0% complete)
[FAILED] Failed to start File System Check o81a1-979f-47db-a743-7dbdbc79e30a.
See 'systemctl status "systemd-fsck@devx2d7dbdbc79e30a.service"' for details.
[DEPEND] Dependency failed for /boot.
[DEPEND] Dependency failed for Local File Systems.
[511687.524606] XFS (vdc1): Mounting V5 Filesystem
Starting Set console font and keymap...
[ OK ] Reached target Timers.
You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to
try again to boot into default mode.
Give root password for maintenance
(or press Control-D to continue): [164252.510128] random: crng init done
[164252.511122] random: 7 urandom warning(s) missed due to ratelimiting

Login incorrect

Give root password for maintenance
(or press Control-D to continue):









share|improve this question






















  • See 'systemctl status "systemd-fsck@devx2d7dbdbc79e30a.service"' for details. What are the details?
    – Mark Plotnick
    Dec 17 at 5:17










  • ice"@mini2-game1-30001:~# systemctl status "systemd-fsck@devx2d7dbdbc79e30a.servi ● systemd-fsck@devx2d7dbdbc79e30a.service - File System Check on /devx2d7dbdbc79 Loaded: loaded (/lib/systemd/system/systemd-fsck@.service; static; vendor pre Active: inactive (dead) Docs: man:systemd-fsck@.servi
    – 朱培棋
    Dec 18 at 8:25
















0














root@mini2-game1-30001:~# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 9.6 (stretch)
Release: 9.6
Codename: stretch
root@mini2-game1-30001:~# reboot
[ OK ] Started File System Check on /dev/disk/by-label/x2fhome.
Checking in progress on 0 disks (100.0% complete)
[FAILED] Failed to start File System Check o81a1-979f-47db-a743-7dbdbc79e30a.
See 'systemctl status "systemd-fsck@devx2d7dbdbc79e30a.service"' for details.
[DEPEND] Dependency failed for /boot.
[DEPEND] Dependency failed for Local File Systems.
[511687.524606] XFS (vdc1): Mounting V5 Filesystem
Starting Set console font and keymap...
[ OK ] Reached target Timers.
You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to
try again to boot into default mode.
Give root password for maintenance
(or press Control-D to continue): [164252.510128] random: crng init done
[164252.511122] random: 7 urandom warning(s) missed due to ratelimiting

Login incorrect

Give root password for maintenance
(or press Control-D to continue):









share|improve this question






















  • See 'systemctl status "systemd-fsck@devx2d7dbdbc79e30a.service"' for details. What are the details?
    – Mark Plotnick
    Dec 17 at 5:17










  • ice"@mini2-game1-30001:~# systemctl status "systemd-fsck@devx2d7dbdbc79e30a.servi ● systemd-fsck@devx2d7dbdbc79e30a.service - File System Check on /devx2d7dbdbc79 Loaded: loaded (/lib/systemd/system/systemd-fsck@.service; static; vendor pre Active: inactive (dead) Docs: man:systemd-fsck@.servi
    – 朱培棋
    Dec 18 at 8:25














0












0








0







root@mini2-game1-30001:~# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 9.6 (stretch)
Release: 9.6
Codename: stretch
root@mini2-game1-30001:~# reboot
[ OK ] Started File System Check on /dev/disk/by-label/x2fhome.
Checking in progress on 0 disks (100.0% complete)
[FAILED] Failed to start File System Check o81a1-979f-47db-a743-7dbdbc79e30a.
See 'systemctl status "systemd-fsck@devx2d7dbdbc79e30a.service"' for details.
[DEPEND] Dependency failed for /boot.
[DEPEND] Dependency failed for Local File Systems.
[511687.524606] XFS (vdc1): Mounting V5 Filesystem
Starting Set console font and keymap...
[ OK ] Reached target Timers.
You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to
try again to boot into default mode.
Give root password for maintenance
(or press Control-D to continue): [164252.510128] random: crng init done
[164252.511122] random: 7 urandom warning(s) missed due to ratelimiting

Login incorrect

Give root password for maintenance
(or press Control-D to continue):









share|improve this question













root@mini2-game1-30001:~# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 9.6 (stretch)
Release: 9.6
Codename: stretch
root@mini2-game1-30001:~# reboot
[ OK ] Started File System Check on /dev/disk/by-label/x2fhome.
Checking in progress on 0 disks (100.0% complete)
[FAILED] Failed to start File System Check o81a1-979f-47db-a743-7dbdbc79e30a.
See 'systemctl status "systemd-fsck@devx2d7dbdbc79e30a.service"' for details.
[DEPEND] Dependency failed for /boot.
[DEPEND] Dependency failed for Local File Systems.
[511687.524606] XFS (vdc1): Mounting V5 Filesystem
Starting Set console font and keymap...
[ OK ] Reached target Timers.
You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to
try again to boot into default mode.
Give root password for maintenance
(or press Control-D to continue): [164252.510128] random: crng init done
[164252.511122] random: 7 urandom warning(s) missed due to ratelimiting

Login incorrect

Give root password for maintenance
(or press Control-D to continue):






debian reboot






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Dec 17 at 3:31









朱培棋

6




6












  • See 'systemctl status "systemd-fsck@devx2d7dbdbc79e30a.service"' for details. What are the details?
    – Mark Plotnick
    Dec 17 at 5:17










  • ice"@mini2-game1-30001:~# systemctl status "systemd-fsck@devx2d7dbdbc79e30a.servi ● systemd-fsck@devx2d7dbdbc79e30a.service - File System Check on /devx2d7dbdbc79 Loaded: loaded (/lib/systemd/system/systemd-fsck@.service; static; vendor pre Active: inactive (dead) Docs: man:systemd-fsck@.servi
    – 朱培棋
    Dec 18 at 8:25


















  • See 'systemctl status "systemd-fsck@devx2d7dbdbc79e30a.service"' for details. What are the details?
    – Mark Plotnick
    Dec 17 at 5:17










  • ice"@mini2-game1-30001:~# systemctl status "systemd-fsck@devx2d7dbdbc79e30a.servi ● systemd-fsck@devx2d7dbdbc79e30a.service - File System Check on /devx2d7dbdbc79 Loaded: loaded (/lib/systemd/system/systemd-fsck@.service; static; vendor pre Active: inactive (dead) Docs: man:systemd-fsck@.servi
    – 朱培棋
    Dec 18 at 8:25
















See 'systemctl status "systemd-fsck@devx2d7dbdbc79e30a.service"' for details. What are the details?
– Mark Plotnick
Dec 17 at 5:17




See 'systemctl status "systemd-fsck@devx2d7dbdbc79e30a.service"' for details. What are the details?
– Mark Plotnick
Dec 17 at 5:17












ice"@mini2-game1-30001:~# systemctl status "systemd-fsck@devx2d7dbdbc79e30a.servi ● systemd-fsck@devx2d7dbdbc79e30a.service - File System Check on /devx2d7dbdbc79 Loaded: loaded (/lib/systemd/system/systemd-fsck@.service; static; vendor pre Active: inactive (dead) Docs: man:systemd-fsck@.servi
– 朱培棋
Dec 18 at 8:25




ice"@mini2-game1-30001:~# systemctl status "systemd-fsck@devx2d7dbdbc79e30a.servi ● systemd-fsck@devx2d7dbdbc79e30a.service - File System Check on /devx2d7dbdbc79 Loaded: loaded (/lib/systemd/system/systemd-fsck@.service; static; vendor pre Active: inactive (dead) Docs: man:systemd-fsck@.servi
– 朱培棋
Dec 18 at 8:25















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


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f489401%2fwhy-did-my-virtual-machine-go-into-emergency-mode-after-reboot%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































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.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • 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














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f489401%2fwhy-did-my-virtual-machine-go-into-emergency-mode-after-reboot%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

Morgemoulin

Scott Moir

Souastre