Solutions:

1. When rebooting the system, select the kernel you want to enter from the following page, and press E, grub to edit the page.
https://img-my.csdn.net/uploads/201709/03/1504438099_7830.png
2. Find linux16 that line in LANG = zh_CN. Utf-8 Spaces with selinux = 0 or enforcing = 0 (I was the first to solve the problem)
3. After that, Ctrl+ X will launch, and you will see the familiar page in a moment. On the other hand, you might be stuck on the page below for a while, but you’ll be fine later
https://img-my.csdn.net/uploads/201709/03/1504438100_7681.png
4. After entering the system, remember to modify the configuration correctly.
5. Modify the “SELinux” parameter in /etc/selinux/config file
# SELINUX = enforcing the original configuration
SELINUX = disabled correctly
   
But I was looking at the wrong modification; Modified the selinuxType parameter by treating “selinuxType =target” as “SELINUX”

# selinuxType =targeted The original configuration is unchanged
SELINUXTYPE = disabled errors

The reason for the error
Configuration closed SELinux, as a result, wrong operation, should be modified in the configuration file/etc/SELinux/config “SELinux” the value of the parameter, SELinux = enforcing original configuration SELinux = disabled right
but mistakenly “SELINUXTYPE” as “SELinux”, set up SELINUXTYPE parameters:
# SELINUXTYPE = targeted the original configuration This don’t need to modify.
SELINUXTYPE = disabled errors
Error
Failed to load SELinux policy. Freezing error caused the machine to never start
Solutions:

When rebooting, on the boot page, select the kernel you want to boot and press E to enter the GRUB editing page. Find the linux16 one line, behind the language Is LANG = zh_CN. Utf-8, the blank space with selinux = 0 or enforcing = 0 (note: I am join selinux = 0 effect.) Then Ctrl + X launches, and you see the familiar login screen. Modify the SELinux configuration file to properly close SELinux ~! 4. Modify SELinux configuration file to properly close SELinux ~!

vim /etc/selinux/config
#This file controls the state of SELinux on the system.
#SELINUX= can take one of these three values:
#enforcing – SELinux security policy is enforced.
#permissive – SELinux prints warnings instead of enforcing.
#disabled – No SELinux policy is loaded.
SELINUX=disabled
#SELINUXTYPE= can take one of three two values:
#targeted – Targeted processes are protected,
#minimum – Modification of targeted policy. Only selected processes are protected.
#mls – Multi Level Security protection.
SELINUXTYPE=targeted

After the modification is complete, restart. Check to see if an error is reported. Over.

I could not find a similar reason on the Internet. I considered that there might be a problem with a previous operation, so I entered Rescue mode
How (centos into rescue mode: https://www.youtube.com/watch?v=e-NauoY3m50& Feature = youtu. Be)

I previously put the /usr/lib64 folder below
/usr/lib64/libstdc++
/ home/zhexin/Software/GCC/GCC – 5.4.0 – build/x86_64 – unknown – – the gnu/Linux libstdc++ – v3/SRC/libs/libstdc++. So. 6.0.21,
In rescue mode, I copy libstdc++.so.6.0.21 to /usr/lib64/libstdc++.so.6 to libstdc++.
Be careful not to link files under root such as /usr/lib64 to a user directory.