How to avoid “Welcome to emergency mode!”
Just after power on I got to :
[[0;32m OK [0m] Started Login to default iSCSI targets.
[[0;32m OK [0m] Reached target Remote File Systems (Pre).
[[0;32m OK [0m] Reached target Remote File Systems.
Welcome to 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):
How to avoid this?
Who is getting in the way and showing this Welcome to emergency mode!?
May I disable any service so that in the next reboot it didn't happen?
This question is part of another one: Amazon AWS EC2 Volume issue prevents instance access via SSH
linux ubuntu debian amazon-web-services amazon-ec2
asked Jun 15 '17 at 19:17
KcFnMiKcFnMi
215212
add a comment |
Just after power on I got to :
[[0;32m OK [0m] Started Login to default iSCSI targets.
[[0;32m OK [0m] Reached target Remote File Systems (Pre).
[[0;32m OK [0m] Reached target Remote File Systems.
Welcome to 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):
How to avoid this?
Who is getting in the way and showing this Welcome to emergency mode!?
May I disable any service so that in the next reboot it didn't happen?
This question is part of another one: Amazon AWS EC2 Volume issue prevents instance access via SSH
linux ubuntu debian amazon-web-services amazon-ec2
asked Jun 15 '17 at 19:17
KcFnMiKcFnMi
215212
1
Did youtype "journalctl -xb" to view system logs?
– Kamil Maciorowski
Jun 15 '17 at 19:28
1
No, because I do not have access to the machine, it's on amazon aws.
– KcFnMi
Jun 15 '17 at 19:31
add a comment |
Just after power on I got to :
[[0;32m OK [0m] Started Login to default iSCSI targets.
[[0;32m OK [0m] Reached target Remote File Systems (Pre).
[[0;32m OK [0m] Reached target Remote File Systems.
Welcome to 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):
How to avoid this?
Who is getting in the way and showing this Welcome to emergency mode!?
May I disable any service so that in the next reboot it didn't happen?
This question is part of another one: Amazon AWS EC2 Volume issue prevents instance access via SSH
linux ubuntu debian amazon-web-services amazon-ec2
asked Jun 15 '17 at 19:17
KcFnMiKcFnMi
215212
Just after power on I got to :
[[0;32m OK [0m] Started Login to default iSCSI targets.
[[0;32m OK [0m] Reached target Remote File Systems (Pre).
[[0;32m OK [0m] Reached target Remote File Systems.
Welcome to 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):
How to avoid this?
Who is getting in the way and showing this Welcome to emergency mode!?
May I disable any service so that in the next reboot it didn't happen?
This question is part of another one: Amazon AWS EC2 Volume issue prevents instance access via SSH
linux ubuntu debian amazon-web-services amazon-ec2
linux ubuntu debian amazon-web-services amazon-ec2
asked Jun 15 '17 at 19:17
KcFnMiKcFnMi
215212
asked Jun 15 '17 at 19:17
KcFnMiKcFnMi
215212
asked Jun 15 '17 at 19:17
KcFnMiKcFnMi
215212
asked Jun 15 '17 at 19:17
KcFnMiKcFnMi
215212
asked Jun 15 '17 at 19:17
KcFnMiKcFnMi
215212
215212
1
Did youtype "journalctl -xb" to view system logs?
– Kamil Maciorowski
Jun 15 '17 at 19:28
1
No, because I do not have access to the machine, it's on amazon aws.
– KcFnMi
Jun 15 '17 at 19:31
add a comment |
1
Did youtype "journalctl -xb" to view system logs?
– Kamil Maciorowski
Jun 15 '17 at 19:28
1
No, because I do not have access to the machine, it's on amazon aws.
– KcFnMi
Jun 15 '17 at 19:31
1
1
Did you
type "journalctl -xb" to view system logs?– Kamil Maciorowski
Jun 15 '17 at 19:28
Did you
type "journalctl -xb" to view system logs?– Kamil Maciorowski
Jun 15 '17 at 19:28
1
1
No, because I do not have access to the machine, it's on amazon aws.
– KcFnMi
Jun 15 '17 at 19:31
No, because I do not have access to the machine, it's on amazon aws.
– KcFnMi
Jun 15 '17 at 19:31
add a comment |
1 Answer
1
active
oldest
votes
We ran into this problem, and I spent 3+ hours trying to fix it. Turns out, one of the EBS wasn't reattached after instance reboot, and since the mount was hardcoded in /etc/fstab, it failed during startup. Once we attached the EBS back to the instance, everything came back up.
Another thing to note: if you reattached the EBS without specifying which /dev/ it's mounted, the EBS will have a different /dev/ point; however, this won't cause an error, as fstab uses device ID and not device location.
answered Aug 1 '17 at 21:16
Tam N.Tam N.
120211
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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%2fsuperuser.com%2fquestions%2f1219695%2fhow-to-avoid-welcome-to-emergency-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
We ran into this problem, and I spent 3+ hours trying to fix it. Turns out, one of the EBS wasn't reattached after instance reboot, and since the mount was hardcoded in /etc/fstab, it failed during startup. Once we attached the EBS back to the instance, everything came back up.
Another thing to note: if you reattached the EBS without specifying which /dev/ it's mounted, the EBS will have a different /dev/ point; however, this won't cause an error, as fstab uses device ID and not device location.
answered Aug 1 '17 at 21:16
Tam N.Tam N.
120211
add a comment |
We ran into this problem, and I spent 3+ hours trying to fix it. Turns out, one of the EBS wasn't reattached after instance reboot, and since the mount was hardcoded in /etc/fstab, it failed during startup. Once we attached the EBS back to the instance, everything came back up.
Another thing to note: if you reattached the EBS without specifying which /dev/ it's mounted, the EBS will have a different /dev/ point; however, this won't cause an error, as fstab uses device ID and not device location.
answered Aug 1 '17 at 21:16
Tam N.Tam N.
120211
add a comment |
We ran into this problem, and I spent 3+ hours trying to fix it. Turns out, one of the EBS wasn't reattached after instance reboot, and since the mount was hardcoded in /etc/fstab, it failed during startup. Once we attached the EBS back to the instance, everything came back up.
Another thing to note: if you reattached the EBS without specifying which /dev/ it's mounted, the EBS will have a different /dev/ point; however, this won't cause an error, as fstab uses device ID and not device location.
answered Aug 1 '17 at 21:16
Tam N.Tam N.
120211
We ran into this problem, and I spent 3+ hours trying to fix it. Turns out, one of the EBS wasn't reattached after instance reboot, and since the mount was hardcoded in /etc/fstab, it failed during startup. Once we attached the EBS back to the instance, everything came back up.
Another thing to note: if you reattached the EBS without specifying which /dev/ it's mounted, the EBS will have a different /dev/ point; however, this won't cause an error, as fstab uses device ID and not device location.
answered Aug 1 '17 at 21:16
Tam N.Tam N.
120211
answered Aug 1 '17 at 21:16
Tam N.Tam N.
120211
answered Aug 1 '17 at 21:16
Tam N.Tam N.
120211
answered Aug 1 '17 at 21:16
Tam N.Tam N.
120211
120211
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1219695%2fhow-to-avoid-welcome-to-emergency-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
1
Did you
type "journalctl -xb" to view system logs?– Kamil Maciorowski
Jun 15 '17 at 19:28
1
No, because I do not have access to the machine, it's on amazon aws.
– KcFnMi
Jun 15 '17 at 19:31