After doing the following a lot went wrong on my COS box:

# yum remove python3-pip

# yum install python3-pip

# reboot

# yum install conda

I was suddenly unable to access my box from a client and also the web interface stopped working.
After a reboot I tried to do a restore, but it got stuck and I lost control of my box again ... no Internet on my LAN.
I rebooted while the restore process was stuck and then I had Internet again, but the restore process gave a re-ocurring serious error:

Command execution failed - rhel-autorelabel-mark

Restarting service: rhel-autorelabel

After this point I lost Internet from my LAN, WinSCP stopped working and everything crashed again.
The red login box on my COS box was replaced by the emergency mode, so I had no other option then to reboot again.
After this I was able to access the web interface again, so I am able to boot up, but I am unable to restore my COS box to it's last functioning state.
I also tried to restore a backup from yesterday, but that gave the same problems.

Please advice.

Ps.
This all started after attempting to follow this.
At the moment "SELINUX=disabled" in /etc/selinux/config ... should that not be "SELINUX=permissive" ... ?!?

EDIT:
"journalctl -xb" resulted in the following errors:

Nov 17 16:09:14 clearos.lan systemd-udevd[289]: inotify_add_watch(6. /dev/sdb1, 10) failed: No such file or directory
Nov 17 16:09:14 clearos.lan systemd-udevd[289]: inotify_add_watch(6. /dev/sdb2, 10) failed: No such file or directory
Nov 17 16:09:14 clearos.lan systemd-udevd[289]: inotify_add_watch(6. /dev/sda2, 10) failed: No such file or directory
Nov 17 16:09:14 clearos.lan systemd-udevd[289]: inotify_add_watch(6. /dev/sda1, 10) failed: No such file or directory

Booted with the rescue kernel and successfully restored a backup, with the following error messages (no Internet):

Command execution failed - Firewall

Command execution failed - NFS-server

Command execution failed - NFS

Firewall & NFS are operational when booting normally.

Still unable to restore when booting normally.