Welcome to emergency mode!

[rhus]

Hello!

I have this problem in openSUSE Leap 42.2.

After the boot, I receive this:
“Welcome to emergency mode! After logging in, type “Journalctl -xd” to view system logs, “systemctl reboot” to reboot,
“systemctl default” or ^D try again to boot into default mode.
Give root password for maintenance (or press Control-D to continue):”

How do I resolve this issue??

Thank you very much!

[arvidjaar]

Some filesystem defined in /etc/fstab failed to mount. You should get list of failed units with “systemctl --failed -l”. Post this list here.

[rhus]

@arvidjaar

Some filesystem defined in /etc/fstab failed to mount. You should get list of failed units with “systemctl --failed -l”. Post this list here.

systemctl --failed -l

UNIT -------------------------- LOAD ----- ACTIVE ----- SUB — Description.
auditd.service ------------- Loaded ---- failed ------- failed - Security Auditing Service.
plymouth-start.service - Loaded ---- failed ------- failed - Show Plymouth Boot Screen.

[rhus]

Anyone have any idea?

[dcurtisfra]

@rhus

“Welcome to emergency mode! After logging in, type “Journalctl -xd” to view system logs, “systemctl reboot” to reboot,
“systemctl default” or ^D try again to boot into default mode.
Give root password for maintenance (or press Control-D to continue):”

How do I resolve this issue??

Please type in the “root” user’s password – at this level there’s no echo – you’ll have to type the password “blind”.

Once you have a “root” prompt, you can begin to inspect the system:

• Check what’s mounted: simply type “mount”.

You’re on Leap 42.2 and therefore there should be a number of Btrfs mount points visible, beginning with the “/” mount point.

• Assuming that the “/” partition is on a Btrfs file system, it may be that, there’s a Btrfs issue here.

Try the suggestions made in this openSUSE post:
<https://lists.opensuse.org/opensuse/2017-02/msg00930.html&gt;

[arvidjaar]

@rhus

systemctl --failed -l

UNIT -------------------------- LOAD ----- ACTIVE ----- SUB — Description.
auditd.service ------------- Loaded ---- failed ------- failed - Security Auditing Service.
plymouth-start.service - Loaded ---- failed ------- failed - Show Plymouth Boot Screen.

Could you upload full output of “journalctl -b” in emergency boot to http://susepaste.org/?

[rhus]

@dcurtisfra

Please type in the “root” user’s password – at this level there’s no echo – you’ll have to type the password “blind”.

Once you have a “root” prompt, you can begin to inspect the system:

• Check what’s mounted: simply type “mount”.

You’re on Leap 42.2 and therefore there should be a number of Btrfs mount points visible, beginning with the “/” mount point.

• Assuming that the “/” partition is on a Btrfs file system, it may be that, there’s a Btrfs issue here.

Try the suggestions made in this openSUSE post:
<https://lists.opensuse.org/opensuse/2017-02/msg00930.html&gt;

This command line “btrfs check --repair /dev/sda6” solved the problem.
I found it in the post suggested by you.

Thank you very much!

[noehlmann]

@rhus

This command line “btrfs check --repair /dev/sda6” solved the problem.
I found it in the post suggested by you.

Thank you very much!

Dear Fellow Users,

I also got into this problem by simply updating the Windows side on my dual boot machine Windows10/Opensuse43.2:
During Update of Windows the friends from Microsoft have changed my power management settings from Shutdown to Hibernate>:(!
As an effect Windows did not shutdown properly and the partition could not be mounted in the Linux directory tree, which resulted in a “Welcome to emergency mode”.

With “systemctl --failed -l” I could easily identify the problem and with the partitioner stop the partition from mounting. That solved the problem.
Thanks to rhusrotfl!

[noehlmann]

Sorry, it was arvidjaar.](https://forums.opensuse.org/member.php/69818-arvidjaar)
But thanks to all of you!rotfl!