Please Help
 

Hi All,
After disabling Selinux, I cant boot my centos normally.
Here is the message:
" 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 fix this?
Please help.

it is written: After logging in, type "journalctl -xb" to view system logs.

Dear Pan64,

yeah i tried command journalctl -xb and then i m getting many logs. kindly tell me the solution as i want to boot normally please.

what do you think how can we help you? Please post the log you got and/or give more information.
http://www.catb.org/~esr/faqs/smart-...html#beprecise

Did you try to re-enable SElinux?

Dear PAN64,

Yes i already enable the status from "sudo nano /etc/selinux/config" it is showing enable when i type command "sestatus".

and?

Dear PAN64,

and then i rebooted my machine and again i stuck on emergency mode.

Dear PAN64,

these are the screenshots when i get output from journalctl -xb.

I think this should be something else, not related to selinux. What you posted is not enough to diagnose it.
http://www.catb.org/~esr/faqs/smart-...html#beprecise
Please post at least the OS, version, the hardware and what was modified/installed, what else happened?

Without telling us anything about your system, there's nothing we can even BEGIN to guess at. And what you posted in your first post is NOT the entire message...how about posting that?

We need version/distro of Linux, type of hardware and machine, and COMPLETE messages. If I had to take a wild guess, the beginning of that message said something about fsck, right???

> After disabling Selinux

why did you do it in the first place?

Dear Tbone,

i m attaching some screen shots in which every thing is mentioned. i created a Vm.

Dear FlinchX,

It was my mistake.

No, that's NOT everything; a good deal comes before that, and again you were asked does it mention fsck???

If you just created this VM, then why bother fixing it? Delete it and start over. As pan64 said, selinux most probably has nothing to do with this.