Eliminate emergency mode.

At each boot-up my Fedora goes to the emergency mode. Black screen with the following message:

Welcome to emergency mode! After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" to try again
to boot into default mode.
Give root password for maintenance
(or type Control-D to continue):

However , after I type Ctrl+D the boot up is success.

1. Why this message occurs?
2. How to eliminate that?

Thanks.
Nusrat NuriyevAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ThomasMcA2Commented:
Look for errors in the system log (/var/log/messages, I think). Sometimes a system boots into emergency mode when either the disk or the memory are generating errors. I suggest running memtest, fsck, and smartctl to test your system.
0
Gerwin Jansen, EE MVETopic Advisor Commented:
What is the output of:

journalctl -xb

or did you not yet run that command?
0
Nusrat NuriyevAuthor Commented:
Some of red messages of journalctl -xb

Sep 08 10:49:48 localhost.localdomain systemd-udevd[138]: unknown key '\nSYMLINK' in /etc/udev/rules.d/99-resume.rules:1
Sep 08 10:49:48 localhost.localdomain systemd-udevd[138]: invalid rule '/etc/udev/rules.d/99-resume.rules:1'

Sep 08 10:50:00 localhost.localdomain systemd-fsck[269]: fsck failed with error code 4.

Sep 08 10:50:00 localhost.localdomain systemd[1]: Failed to start File System Check on Root Device.

Sep 08 10:50:01 localhost.localdomain systemd-tmpfiles[457]: chmod(/var/log/journal/009896b432ed435bb5d6c0bcb8848f55/system@000500fafc
Sep 08 10:50:01 localhost.localdomain systemd-tmpfiles[457]: chmod(/var/log/journal/009896b432ed435bb5d6c0bcb8848f55/system@00050196c7
Sep 08 10:50:01 localhost.localdomain systemd-tmpfiles[457]: chmod(/var/log/journal/009896b432ed435bb5d6c0bcb8848f55/system@000501afe2
Sep 08 10:50:01 localhost.localdomain systemd-tmpfiles[457]: chmod(/var/log/journal/009896b432ed435bb5d6c0bcb8848f55/system@0005005b49
Sep 08 10:50:01 localhost.localdomain systemd-tmpfiles[457]: chmod(/var/log/journal/009896b432ed435bb5d6c0bcb8848f55/system@00050125f4
Sep 08 10:50:01 localhost.localdomain systemd-tmpfiles[457]: chmod(/var/log/journal/009896b432ed435bb5d6c0bcb8848f55/system@0005025179
Sep 08 10:50:01 localhost.localdomain systemd-tmpfiles[457]: chmod(/var/log/journal/009896b432ed435bb5d6c0bcb8848f55/system.journal) f
Sep 08 10:50:01 localhost.localdomain systemd-tmpfiles[457]: chmod(/var/log/journal/009896b432ed435bb5d6c0bcb8848f55/system@0005025522
Sep 08 10:50:01 localhost.localdomain systemd-tmpfiles[457]: chmod(/var/log/journal/009896b432ed435bb5d6c0bcb8848f55/system@0005025251
Sep 08 10:50:01 localhost.localdomain systemd-tmpfiles[457]: chmod(/var/log/journal/009896b432ed435bb5d6c0bcb8848f55/system@0005006930
Sep 08 10:50:01 localhost.localdomain systemd-tmpfiles[457]: chmod(/var/log/journal/009896b432ed435bb5d6c0bcb8848f55/user-1000@0005022
Sep 08 10:50:01 localhost.localdomain systemd-tmpfiles[457]: chmod(/var/log/journal/009896b432ed435bb5d6c0bcb8848f55/system@000502549c
Sep 08 10:50:01 localhost.localdomain systemd-tmpfiles[457]: chmod(/var/log/journal/009896b432ed435bb5d6c0bcb8848f55/system@00050002e6
Sep 08 10:50:01 localhost.localdomain systemd-tmpfiles[457]: chmod(/var/log/journal/009896b432ed435bb5d6c0bcb8848f55/system@00050278e8
Sep 08 10:50:01 localhost.localdomain systemd-tmpfiles[457]: chmod(/var/log/journal/009896b432ed435bb5d6c0bcb8848f55/user-1000.journal
Sep 08 10:50:01 localhost.localdomain systemd-tmpfiles[457]: chmod(/var/log/journal/009896b432ed435bb5d6c0bcb8848f55/system@0005022528
Sep 08 10:50:01 localhost.localdomain systemd-tmpfiles[457]: chmod(/var/log/journal/009896b432ed435bb5d6c0bcb8848f55/user-1000@0005000



Sep 08 10:50:10 localhost.localdomain systemd[1]: bus_connection_get_unix_fd failed Bad file descriptor
Sep 08 10:50:10 localhost.localdomain systemd[1]: Failed to get caller's security context on: Bad file descriptor


Sep 08 10:50:14 localhost.localdomain smartd[519]: Device: /dev/sda [SAT], 3 Currently unreadable (pending) sectors

Sep 08 10:50:53 localhost.localdomain systemd-logind[538]: Assertion 's->user->slice' failed at ../src/login/logind-session.c:531, fun...


Sep 08 10:50:53 localhost.localdomain kdm[697]: :0[697]: pam_systemd(kdm:session): Failed to create session: Message did not receive a...



Sep 08 10:50:53 localhost.localdomain systemd[1]: SELinux policy denies access.
Sep 08 10:50:53 localhost.localdomain systemd-logind[1275]: Failed to start unit user-1000.slice: Access denied
Sep 08 10:50:53 localhost.localdomain systemd-logind[1275]: Failed to start user slice: Access denied



Sep 08 10:52:41 localhost.localdomain su[1867]: (to root) nn on pts/2
Sep 08 10:52:41 localhost.localdomain systemd[1]: SELinux policy denies access.
Sep 08 10:52:41 localhost.localdomain systemd-logind[1275]: Failed to start unit user-0.slice: Access denied
Sep 08 10:52:41 localhost.localdomain systemd-logind[1275]: Failed to start user slice: Access denied
0
Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

Gerwin Jansen, EE MVETopic Advisor Commented:
>>Sep 08 10:50:14 localhost.localdomain smartd[519]: Device: /dev/sda [SAT], 3 Currently unreadable (pending) sectors


You may have a disk that is defective. What kind of system is this? Is this a new system or did you build something on your own?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Nusrat NuriyevAuthor Commented:
How to check whether it's defective or not? Loading from liveCd and fsck?
0
Nusrat NuriyevAuthor Commented:
Well that's fedora, maybe with recompiled kernel  i don't remember.
what does mean "build on my own"?
0
Gerwin Jansen, EE MVETopic Advisor Commented:
"build on my own" means: did you put the machine together yourself from parts? Did you determine if your disc is defective or not? You can use UBCD (Ultimate Boot CD) for that.

Would you explain why you gave a C-grade? Thanks.

http://support.experts-exchange.com/customer/portal/articles/481419-what-grade-should-i-award-
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux Distributions

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.